What books and training in IT have you taken on this sort of work? Sometimes I find fledgling IT staffers without the training and they get really upset over this. That is, they think the answer fits in one paragraph.
OK, well I have 4 different locations that I want to WAN into one network. I have at the central location 2 Servers one is W2003SP2SMB the other is W2008R2 Enterprise. Both are setup to accept RAS connections. I have user accounts shared via Active directory. Now all users at the central location Have not issues accessing their shares or new users being able to log into any computer. ( we have roaming profiles) BUT at the other locations unless I create an account by having the user login or using soem select run commands logged in under me, the remote users can't login and they get "The domain X is not available. please see you system administrator" Ofcourse I renamed my domain in the error message, its not actually called X but go with me on it here.
So I got to thinking, It must be a WAN issue. When I setup a manual VPN connection to either server users can operate fine, but its the whole login issue I'm having. I want my users to be able to access their Outlook and be able to login without me first having to create an account. I want them to be able to roam from PC to PC no matter the location their at.
What I've setup is a Netgear Prosafe VPN firewall FV318. This then goes to a 24 port network switch at each location. Each location does not have their own evers but have a static IP with a ADSL connection. The modem is routed into the network switch, that then all the LAN connections from each location is connected.
Ideas why my WAN doesn't Detect the domain or Whats wrong with the WAN?