Microsoft KB Archive/263006

From BetaArchive Wiki
Knowledge Base


Logon Time Restrictions Prevent Users on Windows 95/98 or Windows NT 4.0 from Remotely Accessing Windows 2000 Resources

PSS ID Number: 263006

Article Last Modified on 12/4/2003



The information in this article applies to:

  • Microsoft Windows 2000 Server
  • Microsoft Windows 2000 Advanced Server
  • Microsoft Windows 2000 Professional
  • Microsoft Small Business Server 2000



This article was previously published under Q263006


SYMPTOMS

In an environment with a Microsoft Windows NT 4.0-based primary domain controller (PDC) and Microsoft Windows 2000-based computers, non-administrative users who are logged on to Windows NT 4.0-based computers may not be able to gain access to Windows 2000 resources remotely. Computers that are running Microsoft Windows NT 4.0 generate a "The server service is not running" error message when you try to log on or gain access to a network resource on the Windows 2000 computer. A network trace contains the error "(91) Invalid User Identifier"

Client computers that are running Microsoft Windows 95 or Microsoft Windows 98 generate a "This Device does not exist on the Network" error message when you try to log on or gain access to a network resource. This issue can also affect a domain with all Windows 2000-based domain controllers.

Specifically, this problem occurs if user accounts have restricted logon hours and a "Forcibly disconnect remote users from server when logon hours expire" account policy is enabled on the PDC. Users cannot gain access to a Windows 2000-based server remotely during a valid logon time.

Also, on a NT 4 machine, if you go to Start-->Run, type in \\server, you will get the error message:

Network name cannot be found

RESOLUTION

To resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

260910 How to Obtain the Latest Windows 2000 Service Pack


The English version of this fix should have the following file attributes or later:

   Date       Time     Version        Size     File name
   -----------------------------------------------------
   5/18/2000  03:00pm  5.0.2195.2096  234,320  Srv.sys  
                



STATUS

Microsoft 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 2000 Service Pack 2.

MORE INFORMATION

NOTE: The preceding problem can also occur with Windows 2000 domains as well.

For additional information about how to install Windows 2000 and Windows 2000 hotfixes at the same time, click the article number below to view the article in the Microsoft Knowledge Base:

249149 Installing Microsoft Windows 2000 and Windows 2000 Hotfixes



Additional query words: event ID 3172

Keywords: kbbug kbfix kbWin2000PreSP2Fix KB263006
Technology: kbSBServ2000 kbSBServSearch kbwin2000AdvServ kbwin2000AdvServSearch kbwin2000Pro kbwin2000ProSearch kbwin2000Search kbwin2000Serv kbwin2000ServSearch kbWinAdvServSearch kbZNotKeyword3