Don, The user's profile (which points to the profile directory on their H: drive) is 2.12 MB). Our pipe is a T-1. According to our LAN admin, it takes approximately 15 minutes to load - and even then, it is not complete (e.g., the network and local NTUSER.DAT file sizes do not match up).
-----Original Message----- From: Don Ely [mailto:[EMAIL PROTECTED]] Sent: Friday, October 05, 2001 9:33 AM To: NT 2000 Discussions Subject: RE: Cross-Wan Authentication How big is the profile you're pulling across? How big is the pipe for your WAN? It would appear that authentication takes so long due to authenticating across the WAN and downloading the profile. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Hoxie, Glenn Sent: Friday, October 05, 2001 5:58 AM To: NT 2000 Discussions Subject: RE: Cross-Wan Authentication Don, we use Cisco equipment across the board. AT&T supports our WAN infrastructure. The problem exists in all offices (specifically, the same scenario would exist if the user logged in from our other non-Washington offices). Users in LA authenticate to their local server (additionally, their profiles reside on a local server). In this case, though, it is a Washington user (sitting in an LA office) who is pulling his profile directory from Washington. -----Original Message----- From: Don Ely [mailto:[EMAIL PROTECTED]] Sent: Thursday, October 04, 2001 5:34 PM To: NT 2000 Discussions Subject: RE: Cross-Wan Authentication So the only problem office is the LA office correct? What kind of Switches, Hubs, etc. have you got? Are these users in LA logging into their local server or are they authenticating across the WAN? -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Hoxie, Glenn Sent: Thursday, October 04, 2001 12: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] ------ 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] ------ You are subscribed as [email protected] Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe send a blank email to [EMAIL PROTECTED]
