Error 53 network path not found

When I attempt to map a drive to windows 2003 server sp2 from ouside the firewall I get the error message "error 53 network path not found" The server is located on our internal network and I'm a member of local admin group on the server. I can access it via thermal services and pcAnywhere, however I can not mapp a drive to it.
cheyligerAsked:
Who is Participating?
 
ChiefITConnect With a Mentor Commented:
There it is. This is the article I was looking for:
http://news.zdnet.co.uk/hardware/0,1000000091,2110398,00.htm

This should help you tune up WINS and DNS over your VPN connection. With WINS in place, you should also be able to use the Browser service. However, I noticed on your DCdiag report that your node type is set to broadcast mode. That means that you may need to change it to Hybrid mode to communicate. Broadcast sends out netbios broadcast. Hybrid sends out broadcasts and WINS netbios translation.

0
 
top_rungCommented:
You need to setup a VPN and authenticate properly  Then you should be able to Map the drive.  
0
 
cheyligerAuthor Commented:
Top rung, of course I've authenicated properly and VPN into our network and could access the server via thermal services and pcAnywhere but I still could not map a drive to it.
0
Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

 
top_rungCommented:
Sorry, but you didn't mention that and I wouldn't want to assume anything.  You do mean TERMINAL services and not thermal correct?

if you are establishing a VPN connection, try going to a command prompt and type..

net use <sharename>


Another thing piece of info you can provide is your network structure.  Are you trying to access a share that is located on the same segment as the one you are VPNing to?
0
 
cheyligerAuthor Commented:
Top_rung, I meant terminal services.... When I attempted to map a drive to it I used the comamnd line which include net use comamnds. I was able to successfully map drives to my other servers using that approach.
0
 
top_rungCommented:
We know that your fiewall is not the prob as you are successfully connecting  to other shares.

So is this particular share on the same network segment as the other shares?
0
 
cheyligerAuthor Commented:
Top rung, yes it is on the same network segment as the other shares.
0
 
ChiefITCommented:
try mapping the share by IP. Example: map a drive to \\5.5.5.5\shared_folder
It sounds like DNS is not negotiating through the VPN tunnel. Maybe the remote client has another DNS server listed as its primary DNS server.

0
 
cheyligerAuthor Commented:
ChiefIT, I've also tried using the ip address of the machine as you've suggested above but, I still get same error 53 meassge "network path not found"
0
 
ChiefITCommented:
So, the scope of this problem goes beyond DNS. If you can't map by IP, You shouldn't be able to ping that computer by IP address. Can you try that. Ping the computer by IP.
0
 
cheyligerAuthor Commented:
ChiefIT, I can ping the machine by its name or ip.
0
 
ChiefITCommented:
The problem with Mapping drives over a VPN is mapping drives uses DNS. DNS uses Netbios. Netbios has difficulty propogating over NAT, (Network address Translation).

The browser service also uses a form of Netbios translation on UDP port 137. So, you will probably have difficulty seeing those same computers you are trying to map to in My network places, UNLESS you are using WINS.

Top Rung: do you have a way to extend DNS beyond the local domain by using a VPN connection?
0
 
ChiefITCommented:
Here is an article that covers some troubleshooting of Netbios over a VPN connection:
http://www.chicagotech.net/vpnbrowsingissues.htm
0
 
Computer101Commented:
Forced accept.

Computer101
EE Admin
0
All Courses

From novice to tech pro — start learning today.