Discussion Locked

Windows XP VPN Mapped Drive Issues

0 helpful
11 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have a client who's main servers (DC and terminal server, win2k3) are in London. They have an office in Newcastle, and this office connects via a VPN into the head office, picking up the domain, exchange, and network shares. To do this newcastle has a Draytek router with a VPN LAN to LAN profile to a netscreen in London.
All was working perfectly when they had Windows 2000 workstations, but recently I travelled up to newcastle and replaced the PC's with Dell WinXP workstations.
Now I'm getting a really nagging problem. Logging on is ok, picking up emails is ok, but the network shares isn't.
Basically the client PC's see the the domain controller ok but not the terminal server (where the shares are located).
The first sign is that the mapped drives don't appear. They should be mapped via a logon script, but when the script runs it shows a system error 53 network path could not be found. In the event logs I'm getting an event ID 1054, saying basically the DC cannot be contacted and the group policy cannot be updated. I can ping the terminal server via IP address and can readd the mapped drive using the IP address, but not with the DNS name. Very annoying!
I have tried lots of things, there are no firewalls running on the client including the SP2 firewall. I have tried updating the GPO Computer\Administrative Templates\System\Logon\[Always wait for the network at computer startup and logon] but to no avail. Its so strange because DNS appears to be ok since I can see the DC\Exchange server, but not the terminal server.
Any help would be greatly appreciated

11 replies

by urbndk

I think it is your login script more then likely your shares might have changed paths during the upgrade and they didn?t change it in your script.

by tim.goodall

Its not the logon script. It can't see the terminal server using DNS names full stop, please read the question as I stated I cannot ping the server using the DNS name. No changes were made to network shares either

by blackcurrant

Hi

Have you tried to use the server's netbios name to map the drive (\\servername\sharename) in your script?

Good luck

by tim.goodall

Poster rated this answer.
Hiya,
Yes I have, the script is the same as its always been. It worked with Win2k workstations but not WinXP. This is happening on two machines no not just on PC specific.
Its completely script unrelated because PING to the DNS name doesn't work either

by shelli_2005

You said you cant ping the server name.
Can you ping the server by fqdn? How about nslookup?
Can you nslookup servername and server fqdn?
Tracert give any hints?

by joanne lowery

Have a look at the hosts file on the old Win2K machine. Also check LMHosts. You may find that either the TS server is specified in the hosts file, or that a domain and location is specified in the LMHosts file. You could either copy off these two or edit the XP files.
By setting hard values in the lm/hosts file the DNS service is not required for name resolution.

by tomaaa1

Hi,
I had a similar problem and used the rather "messy" route of adding the server to the PCs' HOSTS and LMHOSTS files.
Anyone have a neater solution?

by arnold.r.massey

This appears to be a Directory Services security issue with Windows 2K3 server. Information is available on TechNet at http://www.microsoft.com/technet/community/columns/profwin/pw0503.mspx . Also, are you are trying to access VPN from the desktop after a local login?. If so, try "Logon using dial-up networking" from the initial Windows Login prompt (CTL-ALT-DEL). This is a more direct path to the resources that has no "hooks" to local network credentials.

by yinbig

Step 1: Use the IP address in the logon scripts as a counter measure. At least it will work for now.

Step 2: The issue lies with DNS resolution. Perhaps the DNS records are corrupt?
Is thhis record resolved through forwarding to the master server(s)?

Perhaps a function on XP that is not on 2000 has been enabled?

Are the GPO's at the XP sp2 level or are they the old 2000 ones (GPO templates)?

by rubenszhang

Please pay atention to the following:
Since you can't ping the NetBIOS name, make sure PTR records in DNS are created; also in Win2k NETBEUI is installed in most cases, but in WInXP it's not installed by default. Install NETBEUI in the PCs, see if it makes any differences; MS says NETBEUI will slow down XP PCs and/or network performance, I'll say not much; the other try, you can put static DNS IP address in the XP PCs, it will improve login and solve lots of DNS issues. Good luck! Ruben

This discussion is closed to new replies.