Question Locked

Windows XP workstations accessing a Win2003 server across hardware VPN

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

Hi folks.
My company has two new remote sites and a head office. The new remote sites have recently had the networks connected to the head office's network via VPN setup by the telecoms provider. They have provisioned private DSL links in each remote office that connect into the same provider of the head office's 6MB fibre link. They have set it up with Cisco 878 ADSL routers at the remote ends and a Cisco 871 Ethernet router at the head ofice all connected via IPSEC VPN.

So, my issue and question is that I have a Windows 2003 server (domain controller) at the head office and XP pro domain workstations at the remote offices. These workstations used to be connected to the domain at the head office LAN but since they were relocated to the remote office LAN they can no longer see the server automatically. I can ping the server across the links, manually set things like DNS work fine, and everything seems to be connected correcty, but I don't know how to make the workstations automatically 'see' the server for authentication and fileserver shares etc. Is there a setting I need to change for them to see the server? ... or is the VPN blocking some of the protocols necessary for the windows domain to work normally?

Sorry for the long-winded explanation, it's just that I barely understand the problem myself. Thanks in advance for any assistance.

Aaron in Australia.

3 replies

by scott_heath

When you say that the servers can't be "seen" what does that mean specifically? If you are logging into the workstations with a domain account, then they are authenticating. If you are logged in to a workstation as a domain admin and type \\servername\c$ what happens?

Regards,
Scott

http://scottisageek.spaces.live.com

by churdoo

As Scott suggested there could be several answers here. The most common missing piece about VPN-connected sites is name resolution at the remote sites.

I'm assuming you'll not be bringing up a DC at the remote sites, or at least not for the sake of this discussion. If the workstations at the remote sites are set to look to your AD-DNS resolver, i.e. your DC at the HQ site, then all should be well. Assuming you're using DHCP at your remote sites, probably handed out by the Cisco gear, you can do this by setting the DNS settings manually on the workstation to override the DHCP-provided DNS settings, but of course it would be better to configure the DHCP scope options on your remote site DHCP server to hand out your HQ DC private IP addy as the first DNS resolver and the ISP provided DNS as second, third etc. The reason for the ISP provided DNS is if your VPN link is down or if your DC at HQ is down for whatever reason, your remote site clients can at least browse the internet and carry on locally.

Hope this helps.
--C

This discussion is closed to new replies.