See my other question for the response, which basically is sites were set up at the beginning of the migration.
Although, I will check the DHCP setting to ensure each site is looing at its own DNS server.
Thanks
Main Topics
Browse All TopicsFYI - Same setup as a previous question, but a different problem.
We just completed a migration to a single Windows 2003 Active Directory. The migration consolidated 11 Windows 2000 forests into 1 Windows 2003 forest. We went from having 1 site per forest to having 9 sites in our new Active Directory. Per the event logs and experience, AD & NFS replication is happening in a timely manner and without error. Each site has their own domain controller, except for one site, which has two domain controllers. Each site also has a global catalog. The Windows 2003 Active Directory is in 2003 native mode.
We are still learning about the nuances of having a single domain and 9 geographically dispersed sites. 8 of the sites are connected by a T1 WAN link. The 9th site is linked via a DSL line with a VPN tunnel connecting it into the WAN. It is this 9th site we are having some challenges. This 9th site has two Windows 2003 domain controllers. One domain controller is a Global Catalog server, and the other domain controller holds the Infrastructure Master FSMO role.
Situation 2
When the DSL link goes down all of the workstations in Site 9 cannot authenticate locally. What is most strange is that the GUI logon screen does not present itself. There is no opportunity to enter <Ctrl><Alt><Delete> to at least logon locally to the workstation. These workstations appear to hang at some point in their startup. Both Windows NT 4 workstations and Windows XP pro workstations are effected by this situation. As soon as the DSL link is reestablished these workstations behave normally. This situation has happened several times.
If by chance a station was left logged on and the DSLlink goes down the station cannot access any resources from a local server, such as shared folders. If the user logges off the station while the DSL link is down, then the user will not be able get back in again because the logon prompt is not being presented.
What would prevent these workstations from presenting the logon screen?
What does down DSL line (Site 9’s link to our WAN) do to this network?
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Business Accounts
Answer for Membership
by: Netman66Posted on 2006-07-29 at 19:07:30ID: 17209493
See my post in the other question.
Once Sites are created and configured properly and the servers are moved to their correct site (within AD Sites and Services) then this issue should go away.
If you unplug the network cable on these PCs, the logon prompt should come up.