| Basic help with VPN Remote server is running XP Pro SP3, has a static IP (192.168.0.x) and is connected to Internet using a Netgear DG834G v3. I can Remote Desktop into this machine without problems.
Using the basic Microsoft VPN software in XP, I can log in ok, but cannot map a drive. I have tried using both the sharename and the IP address, but all I get is "The network path could not be found".
Any help would be appreciated... |
|
 SoonerAlOld enough to know betterPremium,MVM
join:2002-07-23
Norman, OK
kudos:5 | said by Spartan :Remote server is running XP Pro SP3, has a static IP (192.168.0.x) and is connected to Internet using a Netgear DG834G v3. I can Remote Desktop into this machine without problems.
Using the basic Microsoft VPN software in XP, I can log in ok, but cannot map a drive. I have tried using both the sharename and the IP address, but all I get is "The network path could not be found".
Any help would be appreciated...
Any chance the remote network the VPN client computer is on is also using the 192.168.0.X subnet? If so that is most likely the problem. The client does not know how to resolve the addresses since both ends of the VPN link are using the same address range. The solution is to change one end, either the server or the client, to a different subnet, ie. 192.168.2.X for example.
Our colleague mudtoe has some good advice about that in this post.
»Re: OpenVPN Errors -- MULTI: bad source address from client
Once you get this sorted out you might consider using a lmhosts or hosts file on the VPN client. Here is an example lmhosts syntax and file...
»support.microsoft.com/kb/314884/en-us
»theillustratednetwork.mvps.org/V···osts.txt
...based on this example network...
»theillustratednetwork.mvps.org/V···work.pdf
--
"When all else fails read the instructions..."
MS-MVP Windows Expert - Consumer |
|
| Thank you for your quick response...
No, on different subnets. Server is 192.168.0.x and client 192.168.1.x
Tried adding the IP address of the server to the LMHOST file on the client, but it made no difference. Still get the same error message.
I have also tried this:
net use Z: \\192.168.0.x\abc
Get same answer with 'System error 53'. If I then try the following it goes on to ask for username and password, but the box shows it's trying to log onto the client machine, not the server! It of course fails.
net use Z: \\Actualmachinename\abc
The Server is on a very simple workgroup network with only two other machines. As I said previously, Remote Desktop works fine, if that's of any consequence. |
|
1 edit | reply to Spartan
What’s not clear here is whether you can connect to the share even if you were physically located on the remote network as a local user. Yeah, you've shown you can remote desktop to the remote machine, but that's not evidence you have access to file sharing on that machine. Perhaps the remote machine has a local firewall blocking access, perhaps it’s just dropping the request so its appears to be not found. I suppose another possibility is that network file and printer sharing isn't bound to the VPN (check your VPN properties, it's normally enabled by default, but who knows, maybe something changed it). |
|
SoonerAlOld enough to know betterPremium,MVM
join:2002-07-23
Norman, OK
kudos:5 | reply to Spartan
In addition to eibrad's comments you also might look at this. I don't think its directly involved but check anyway.
»support.microsoft.com/kb/315236
--
"When all else fails read the instructions..."
MS-MVP Windows Expert - Consumer |
|
|
|
| Well here's what's happened since I last posted...
I had previously made sure the server and the ADSL router were rebooted prior to renewed attempts at getting the VPN to work, but no joy.
During the night there was a mains power outage to the whole building. Machines and router restarted some hours later, and when I checked the VPN, IT WORKED! I cannot offer any explanation as to why it worked, as no further changes were made to any setup.
Thank you for your thoughts on the problem. |
|
