Mapping Drives in Windows
-
I recently replaced a Sonic Wall TZ500 with a Netgate PFsense 4100. I'm using the same LAN IP, but after installation I found that all of my mapped drives were no longer connected (including my Synology NAS).
After some tinkering, I found that I could connect to the NAS using the UNC path method, but I still cannot connect with the IP Address and I also cannot access the NAS GUI. I can't map to Win 7 computers at all.
Does Netgate block SMBv1? Any help is appreciated.
-
@acannon said in Mapping Drives in Windows:
Does Netgate block SMBv1? Any help is appreciated.
Traffic between devices on the same network do not go through your router - what pfsense blocks or doesn't block leaving a network/vlan has nothing to do with devices talking to each other on the same network.
Your problem is most likely due to your devices getting different IP address then they had before.. if the unc path works, ie name but not IP your just using the wrong IP..
-
@johnpoz : I understand your point, but the NAS address is static and I can ping it; it just won't map. Am I missing something?
-
Sorry wrong thread.
Traffic from client 192.168.1.x or whatever network your on talking to 192.168.1.y has zero to do with pfsense - traffic between devices on the same network don't talk to the router. The router doesn't even know about this traffic, and could not mess with it even if it wanted too?
if you can ping the nas, and you can not map a drive - then its something on the nas, maybe the nas firewall and have not adjusted it for the new network your on?
Maybe you have duplicated IP? and your not actually talking to the nas when you ping it, etc.
-
@johnpoz : OK well I’ll figure it out. All I know is that when I take the LAN switch (that includes the NAS) and put it back on the old sonicwall everything comes back including the mapping of the IP address 10.108.x. If I move it back to the Netgate, 10.108.1.x, it all goes away. It looks like I’ve got more to do.
-
@acannon Are you bridging interface on the pfsense, where device X is on different side of bridge than device Y?
You said you set static, did you mess up the mask?
Here is what happens when 10.108.1.x/24 wants to talk to an IP.. Lets say it wants to talk to 10.108.1.y -- says oh that is on my network - let me arp for it, .y answer and says yup that is my IP here is my mac address. Then .x sends the traffic to .y mac - the router, pfsense has zero to do with that traffic - zero!
Now if lets say that IP address was 10.108.2.A, or lets say 8.8.8.8 - the devices says oh that IP is not on my network - lets send it to my default gateway since I don't have any other routes to get to that network the IP is on. It would then arp for the gateway mac and send the traffic to that mac.
Whatever issue your having it has zero to do with the router/pfsense - a router is only involved in routing traffic off a network to another network. So maybe you have a duplicate IP if your setting them static on the devices, or maybe you messed up a mask?
Here is one scenario I could think of that could cause a problem when the router/gateway changes - say with windows firewalls. When the gateway mac changes - windows thinks hey this is a different network, so going to use my public profile and firewall rules would be different than private network profile, etc.
-
@johnpoz : I was originally using it as a bridge server, but the second side of that bridge server is not connected anymore and everything is on one side now.
I think my best bet at this point is to take a separate computer and a separate switch and connect those to a separate NIC on the Sinology NAS so that I can access the GUI. From there maybe I can rework the network and get it put back together.
To recap, when I installed the Netgate, I basically matched all of the networking. I wanted it all to be the same as it was in the sonic wall. Same, WAN, same, LAN, same port forwards.
Basically, everything worked out except for the NAS.
I crack into it more after the holiday.
Thanks for your response.