Can't map network drives on Windows 7 machine with SBS 2003

I am unable to map network drives on a windows 7 machine located on site connecting to SBS 2003.  We currently have a site to site VPN from this remote site to our Headquarters office and I am able to map the drives on a windows 7 machine located here across the VPN.  I can ping the server from the workstation in which I am trying to map the drives and also can do an nslookup and get the correct address and hostname.
Free3454Asked:
Who is Participating?
 
Free3454Connect With a Mentor Author Commented:
I found that windows 7 is not compatible with SBS 2003 so once I upgraded to server 2008 everything worked fine.
0
 
Gabriel CliftonNet AdminCommented:
Is the SBS that you are unable to map to local? What happens when you try to map the drive manually, through command prompt?
0
 
Free3454Author Commented:
Yes it is local to where the workstation is, I have not tried to map through the command line, will try that and see.
0
Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
Free3454Author Commented:
I have just tried through the command line and get system error 53, the network path was not found?
0
 
Gabriel CliftonNet AdminCommented:
Are you able to browse to the share \\server\share$ check the permissions of the shared folder to make sure the users have access to it.
0
 
Free3454Author Commented:
I am not able to browse, I am able to map the drive with the users credentials on a machine at our headquarters which has a site to site VPN.  I setup the workstation here and was able to map the drives but when I shipped it there they were disconnected and I am not able to reconnect them.
0
 
Gabriel CliftonNet AdminCommented:
Possibilities:
When you mapped the drive through VPN, it mapped through the VPN, meaning that when the user got it, it was trying to use vpn to get to the share.

DNS settings are holding strong for your location and when the computer is being used at the remote location it does not know where to go. But you can ping the server and perform nslookup.

Could be routing issue, DHCP, or just network cache from HQ. Check computers logs.

Are you able to RDP into the computer and test it.
I am not guessing on fixes, just trying to get the full picture of the issue.
0
 
Free3454Author Commented:
Yes, I can RDP to it and I also have VNC on the machine as well.  I can ping the server by hostname and IP, can do nslookup and get correct response.  I can remote into that workstation, then logon to the VPN client which connects here at Headquarters then I can map the drives fine, but I cannot map them there locally.  I can't add the machine to the domain either, XP works fine.
0
 
Gabriel CliftonNet AdminCommented:
Ok, are you able to map the drive using FQDN , \\server.domain.local\share$. If you can then the local PC is trying to use the VPN credentials to access the local resources, which you could then use "cmdkey.exe /delete /ras" to clear RAS credentials cache.
0
 
Free3454Author Commented:
Unfortunately no, I can't map using the FQDN or the IP address of the server.
0
 
Gabriel CliftonNet AdminCommented:
Remove VPN settings, clear RAS cache then try to start over from there.

Open network and sharing center. On left side click on Change adpater settings. You will get all created VPN connections and you can delete what you don't need.
0
 
Free3454Author Commented:
I found this out on my own after much research and realised the only option was to upgrade the current system.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.