My two cents Delete the profile on the PRo box so it is NOT their anymore. Make sure that when the users roaming profile comes down it has (rather the user has) permissions to copy it into the profile directory on the workstation (where ever that is) If all else fails put the user in the local admin group and turn on ALL auditing to make sure it is not a permission issue. Try copying the users roaming profile to another location and change his account so it knows where to get it from. Can the user type \\server\profilelocation and see his profile? and copy files to it?
-----Original Message----- From: Hoxie, Glenn [mailto:[EMAIL PROTECTED]] Sent: Thursday, October 04, 2001 3:25 PM To: NT 2000 Discussions Cc: Lin, Michael Subject: Cross-Wan Authentication Environment: We have a Windows 2000 environment (native) (SP1 on servers; SP2 on workstations). We have four offices across the U.S. (one in England). A T-1 line exists between both the DC and Los Angeles offices. In this particular case, our DC-based user logs in normally. Specifically, all network profile information cleanly uploads to his local profile. The user's profile is stored on a DC-based server. Situation: When the user logs in as himself into a Windows 2000 Pro box in Los Angeles two issues arise. One, the time it takes to load the desktop is extremely slow - verging on 15 minutes. Two, it appears that the network profile is not coming down. The reason I believe this is the case is because the user's NTUSER.DAT file on their network location is 608KB. The size under their local profile (post login) is 200KB. Any ideas or recommendations would be sincerely appreciated. Thanks in advance. Glenn Hoxie Steptoe & Johnson LLP ------ You are subscribed as [EMAIL PROTECTED] Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe send a blank email to [EMAIL PROTECTED] ------ You are subscribed as [email protected] Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe send a blank email to [EMAIL PROTECTED]
