Discussion Locked

Logon problem when the WAN goes down

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

Our Win2K WAN is nationwide and the office I serve as an administrator is in Denver.We run roaming profiles and some of our policies are fairly strong.I do not work in the main office, but a branch, so I am a little outside the loop unless I ask a lot of questions of my colleagues at the main office.Most of our network people in the main office are very good, and very qualified, and they are scratching their heads a bit on this one.A few of the administrators feel we may have found a bug in Windows 2000 networking that needs a patch.Microsoft has looked at our setup and can find nothing wrong. I feel that they and we may have missed something obvious.
When the WAN connection goes down (between our office and the home office) the users inour office cannot logon, or logoff their workstations. It hangs at copying user settings. When the OS cannot find the roaming profile, it should give that error, but continue to log-on after clicking through the error. But it absolutely will not. However, If I physically remove the connection from the NIC, the workstation will logon (giving the roaming profile error.) If I plug back in the connection after it gives the roaming profile error, the users can work within our local network.Our QuestT1 has gone down twice in the last month for a half day at a time. Going to a hundred and fifty workstations and unplugging/plugging back in the network line is just not acceptable.I am sure you may give some that we have tried, and you may have some question about our setup. We are currently going over our DFS setup in the entire forest to make sure the correct servers are listed. It appears as though the workstations are looking to the DC in our main office for some information, instead of using the replicated information in the local office.
Robert (Bob) Ball MCP

5 replies

by tony.colgrove

First an assumption: Since you say Win2K WAN, I will assume you are using Windows2000 Active Directory, and Windows2000 Professional. If that is not true then these question might not fully apply:
1- Is your branch office configured as a seperate site in AD?
2- Is the local Win2K domian controller (you should have a local one) also a Global Catalog Server?
3- Are your GPO's configured at the site, domain, or OU level?

One thought is that your systems are trying to contact the PDC Emulator for the group policies. I believe DFS access can also be affected by site configuration.

by bobball

Size restrictions prevented me from fully explaining our setup to you.
We are fully Win2K Server/Pro AD
Our branch office is a separate site in AD
GPO's are configured at the domain level.
Our local DC is set up as a Global Catalog Server (I am double checking this though)

Good answer; I am running it by one of our engineers at the main office for confirmation of my answers and your suggestion.

by bobball

The problem was solved.
A file folder that DFS uses on each Domain controller.Until last week the only two root replicas for \\xxx.firmwide.com were \\firmwidedomaincontroller and \\itsbackupDC and no other domain controllers on the network which is what we believe was causing the problem with login on in local offices when the WAN link was not available. I believe those folders exist only because they are defined by DFS under the root.
Once this was changed, and the other DC's were listed,the result was that we could log on locally.

This discussion is closed to new replies.