We have this system that has worked for years. It is 2 Windows XP Pro SP2, talking up a VPN (over ADSL Modem) to a remote server. The destination ip of the two xp boxes was 10.10.10.11 or so. The VPN box failed, and was replaced. After the VPN was replaced, the destination ip is now something like 167.75.43.20, having been changed by the techies at the server site. Long story short, I am trying to map a drive to a folder on that remote, and keep getting error 53 "Network path not found" even though we have triple checked the syntax of the cammand, the destination ip, and manually verified that the volume exists. I can ping the server address and get a good reply. What am I missing? I'm a control-side programmer with limited network knowledge. Thanks.
2007-03-07 08:04:53 · 2 answers · asked by steve.c_50 6 in Computers & Internet ➔ Computer Networking
The techies at the other end haven't finished setting up how the LAN is accessed through the VPN, they need to get into the VPN Router and do some more configuration. The destination addresses of the 10 dot series is still what you want to connect to, but they haven't setup LAN access to get thru to them, so you're being stopped at the Router's IP Address.
2007-03-07 08:22:45 · answer #1 · answered by John N 2 · 0⤊ 0⤋
Okay, so to drive map, first you take the mohawk off your head and divide it into seperate pieces, then you connect the dots with each hair, and there you go bingo! You have your drive mapped!
2007-03-07 16:09:08 · answer #2 · answered by The Answer 2 · 0⤊ 1⤋