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