Re: Can't Map Drive over VPN to Win2K Server but can to desktops
From: Martini Murphy (Simon.Murphy_at_London.com)
Date: 12/03/04
- Next message: Terry: "Re: WINS server"
- Previous message: steŠ: "Wired v Wireless"
- In reply to: Lanwench [MVP - Exchange]: "Re: Can't Map Drive over VPN to Win2K Server but can to desktops"
- Messages sorted by: [ date ] [ thread ]
Date: 3 Dec 2004 02:39:15 -0800
Hi Lanwench, thanks for the reply:
Just a few comments:
- VPN Clients are using a different address scheme
- I think WINS is ok. As a test, I set up a static address in WINS as
an alias for the server and, from the VPN client, I can 'ping' with
the new name and it resolves the IP address of the server. When I do
a 'net view' of this alias I still get the same error 53 (network path
was not found).
- I added the WINS details to the DHCP scope. Not sure why though.
The internal LAN was working fine anyway without WINS and the VPN
clients don't get their details from DHCP. The server already points
to itself (proper IP address, not the loopback address) in WINS. I
aslo have DNS to forward unresolved names to WINS.
I've tried mapping drives from Explorer and from the command line,
both with host name & IP address.
In summary, I can map drives with no problem from the VPN client onto
shares on XP Pro & Win2k Workstation desktops but not the Win2K server
(which is the PDC). I can only guess that this points to a
configuration problem with the server maybe at an IP traffic level or
a security level as everything else works.
- Next message: Terry: "Re: WINS server"
- Previous message: steŠ: "Wired v Wireless"
- In reply to: Lanwench [MVP - Exchange]: "Re: Can't Map Drive over VPN to Win2K Server but can to desktops"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
