Cannot Use a Windows XP Network Share if You Are a Member of More Than 180 Groups (321180)
The information in this article applies to:
- Microsoft Windows XP Home Edition
- Microsoft Windows XP Professional
This article was previously published under Q321180 SYMPTOMS
Under the following conditions, you may receive one of two different error messages:
- You try to use a share on a Windows XP-based computer from another client computer.
- Your domain account is a member of more than 180 groups.
- You try to connect to the share by using a universal naming convention (UNC) name such as \\computer name\share name.
Under these conditions, you may receive either of the following error messages:
Windows cannot find \\computer name computer name is not accessible [...] you might not have permissions to access computer name. More data is available.
CAUSE
The redirector requires that tokens that are used for authentication cannot be larger than four kilobytes (KB). Membership in a large number of groups can result in a token that is more than four KB, and this may cause the remote connection to fail.
RESOLUTIONTo resolve this problem, obtain the latest service pack for Windows XP. For additional information, click the following article number to view the article in the
Microsoft Knowledge Base:
322389 How to Obtain the Latest Windows XP Service Pack
The English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Date Time Version Size File name
----------------------------------------------------
16-May-2002 11:24 5.1.2600.45 653,824 Lsasrv.dll
WORKAROUND
To work around this problem, use the \\IP address\share name UNC style, or be a member of less than 180 groups.
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows XP Service Pack 1.
Modification Type: | Minor | Last Reviewed: | 9/30/2005 |
---|
Keywords: | kbHotfixServer kbQFE kbbug kbenv kberrmsg kbfix kbOSWin2000fix kbWinXPsp1fix KB321180 |
---|
|