We have been using Windows NT clients on a Windows NT domain for 5 years.
All users have been using roaming profiles with not glitches.
We are in the process of upgrading all of our workstations to Windows 2000.
All upgrades have been performed as a wipe and reload.
Now some of the users are experiencing trouble logging on with their roaming profile. They get a message stating that a file cannot be copied, and that they will be logged on with a temporary profile. It is not consistently the same file that fails.
Usually, if they log out and back in they get their roaming profile after 4-5 tries.
Each failure is accomponied by an event log entry on the client stating one of the following:
1: The specified network name is no longer available.
2: The network path was not found.
There are not corresponding entries in the server log regarding redirector timeouts.
Once the person is logged in, they never have any trouble opening any of their files, which are stored on the same server, across the network.
The user directories and profiles were originally stored in a Windows NT domain controller, but have been moved to a Windows 2000 member server with no improvement.
The profiles are limited to 40 MB, but most of the people having problems have profiles in the 3-10 MB range.
The problem is most prevalent on a segment of the network connected via a 10 Mb/Sec wireless bridge, but is also occurs on machines connected via CAT-5 through 100 MB/Sec switches.
I'll post a second question with another 500 points for whoever answers this.