Problems with Mapped drives

[erhardh]

Hello all,

Recently when we map drives and users access these drives via the VPN and sometimes on the LAN they see the mapped drive but when double clicking on it and going into the drive the users don't see the data in the drive. One way we kinda fixed it is to map the drive via the IP address of the server and not the UNC name. WINS was recently taken off this network and we are now exclusively DNS

any ideas as to why this might be happeneing?

 

[dTardis]

I have seen DNS not working through a VPN. For example the remote PC can not get a DNS resolution from the VPN connected network.

If you are having this problem when connected to the LAN (not the VPN) then I would open the RUN command and try the UNC (\\ServerName\FileShare) and see if that works.

 

[dberg35]

Also try flushing DNS to get it refreshed. (ipconfig /flushdns)

 

[w33mhz]

It would also help to verify that your VPN clients are recieving the correct DNS server addresses/VPN server has correct DNS configuration. If using DHCP through in the address of a WINS server that might help.

Also verify your firewall settings on the clients, turn the windows firewall off and check the the drive mappings, windows firewall is sometimes the cuplrate for many strange network issues.