Use opt interface as LAN port
-
It looks to me that rule1 is not needed on either interface but maybe you just have them there as placeholders and you'll tweak them when you get your current configuration working.
ping by IP address? ping by hostname? what does ping tell you? do you know the ping target actually has the address you think it should have?
There are a lot of things that could have gone wrong. It would be helpful to have a few more clues about what you have done and what you saw.
Did you remember to reset firewall states after changing the firewall rules?
Ok, Rule1 on both has been removed. I then reset the states (thanks for the reminder).
ASSUME: LAN has IP 192.168.0.1 and PC1 resides
ASSUME: OPT1 has IP 192.168.1.1 and PC2 residesFrom PC1 (and vice versa):
When I ping PC2's assigned IP address I receive a reply and vice versa. Good.
When I ping the computer name pc2 (i.e. ping pc2) from pc1 I receive "Pinging pc2.domain [oddball ext. ip] request timed out.
Now when I map, i.e. \pc2\c$ I got a time out however when I map to the IP, i.e. \192.168.1.x\c$ it works just fine.
A DNS issue???
-
A DNS issue???
Yes.
For PC1, who is its name server? Does it have a name - address mapping for PC2? (It will have to be a "local" system because a public name server won't know about names on your private network,) If pfSense is the name server how does it know the name - address mapping for PC2? Does DNS forwarder have a registration or (if you are using DHCP static assignments) do you have Register DHCP static mappings in DNS forwarder set?
-
For PC1, who is its name server? Does it have a name - address mapping for PC2? (It will have to be a "local" system because a public name server won't know about names on your private network,) If pfSense is the name server how does it know the name - address mapping for PC2? Does DNS forwarder have a registration or (if you are using DHCP static assignments) do you have Register DHCP static mappings in DNS forwarder set?
Lots of good questions. I use my ISP's Name Servers however pfsense assigns the dns and gateway it's own, i.e. 192.168.x.x. Under System –> General Setup --> Domain is domain.local however both LAN and OPT1 are on workgroup networks (not domain access). My systems were static however even checking the DHCP static mappings didn't work and so I set them to DHCP and same outcome.
I can ping pc2.domain (which shows an ext. IP) but no other combination works, i.e. pc2.domain.local , pc2.local , domain.local
-
If pc1 has domain domain.local and pc2 is known to the name server as host pc2 in domain domain.local then pc1 should be able to access pc2 as pc2 or pc2.domain.local.
What does pc1 think its name server is? (In windows open a command prompt and type command ipconfig. In Unix or Linux give the shell command dig or nslookup pc2 to see what is reported as the name server.) If you aren't sure how to interpret the output post the command and its output in a reply.
My systems were static however even checking the DHCP static mappings didn't work and so I set them to DHCP and same outcome.
I'm not sure what you mean by this. How are pc1 and pc2 getting their IP address? If its set as static IP address then you should also be setting the IP addresses of the default gateway and DNS. If pc1 and pc2 get their IP addresses from DHCP then they should also get default gateway and DNS from DHCP. If you switched pc1 and/or pc2 from static IP address to DHCP then you might need to disable then enable the corresponding interface (on pc1 or pc2) or even reboot to get them to issue the DHCP request.
-
If pc1 has domain domain.local and pc2 is known to the name server as host pc2 in domain domain.local then pc1 should be able to access pc2 as pc2 or pc2.domain.local.
What does pc1 think its name server is? (In windows open a command prompt and type command ipconfig. In Unix or Linux give the shell command dig or nslookup pc2 to see what is reported as the name server.) If you aren't sure how to interpret the output post the command and its output in a reply.
Finally…I swapped out my pfsense box for a different one and had probs with a different package and ended up redoing that one. Now I'm addicted to pfsense. Never meant to leave you hanging but since rebuilding I had to place this on hold.
From where I stand now, PC1 on LAN cannot ping PC2 on OPT1 by the command "ping PC2" as it just gets timed out. However, PC1 can ping the ip address of PC2 and receive a reply.
PC1 also cannot map to PC2 via \PC2\c$ however \192.168.x.x\c$ works. Is there some pfsense switch I'm missing that would allow mapping by the computer name PC2?
-
Its been a while since this was last discussed so lets verify the configuration you are currently using.
PC1 seems to be a windows system. In a command prompt window give the command ipconfig and verify that the pfSense box is the DHCP server and the DNS server. If thats not the case then the rest of this reply doesn't apply.
In pfSense Services -> DNS forwarder check the boxes Register DHCP leases in DNS forwarder and Register DHCP static mappings in DNS forwarder then click Save. This is probably not sufficient to get the DNS forwarder to notice the new settings so clear the Enable box then click Save and then tick the Enable box then click Save. Now try your access to PC2 by name.
If it didn't work, does PC2 have a DHCP lease from the pfSense box? If so, maybe DNS forwarder only notices "new" DHCP leases. So, restart PC2 so it gets a new DHCP lease. Then try the access by name from PC1. But did PC2 get its DHCP lease from pfSense?
On my home network al the systems get their IP address from DHCP. If that doesn't apply to your network a different solution will be required.
-
On my home network al the systems get their IP address from DHCP. If that doesn't apply to your network a different solution will be required.
Wow…them all being static is what it was. When I changed them to DHCP it worked like a charm. I then noticed the difference is that when static the ipconfig would not show the dns suffix and when I typed that in walla... Thank you!