We have a Windows XP Professional desktop at a remote site connected to our SBS 2003 domain controller at the main office via VPN (LogMeIn Hamachi).
The XP desktop was joined to the domain across the VPN connection without any problems.
The issue is that domain users at the remote site see the following message when they try to log on:
This does not happen when the PC is taken to the main office and connected to the LAN, and subsequent attempts to log on remotely succeed after this is done (but only due to cached credentials- the underlying problem remains and new users will still not be able to log on at the remote site).
The other symptom is that domain users do not show up properly on the Local Users and Groups MMC snap-in (it shows only their SIDs, without the corresponding domain user names).
I've tried removing the PC from the domain and re-joining in case it was simple broken trust relationship problem (and even tried a different PC) but the issue is always the same.
Here are the results of pinging various combinations of hostnames and IP addresses for the domain controller from the XP system:
ping server = SUCCESS
ping server.domain.local = FAIL (however pinging the server's FQDN is successful when done to PCs at the main office)
ping 192.168.1.50 = FAIL (pinging DC by its private IP)
ping server's Hamachi VPN IP address = SUCCESS
There are no problems accessing shares on the server over the VPN link.
The (automatically-assigned) DNS for the XP system is the gateway router's IP: 192.168.1.1
Network shares on the server are working perfectly- it seems this issue only affects the ability to log on as domain users.
Any ideas what is going on and how I can fix this?