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
