Re: Problems logging on to Windows Based Server.

From: Karl Levinson [x y] mvp (levinson_k@excite.com)
Date: 10/30/02


From: "Karl Levinson [x y] mvp" <levinson_k@excite.com>
Date: Tue, 29 Oct 2002 21:17:54 -0500


I assume that you're sure that the caps lock is not on, a key on your
keyboard is not broken, and the password has not been changed by someone
else.

Here are the descriptions from the articles you referenced, they more or
less made sense to me anyways.... there were also a number of related linked
articles.

CAUSE

This problem occurs because the Windows 2000-based server rejects your logon
password when the client computer does not correctly de-allocate an internal
structure that is used to track the logon session. The client attempts to
reuse the expired encryption key that is passed to it by the server during
the original logon.

This problem does not occur in conjunction with Microsoft Windows NT-based
clients because the client does not attempt to use Distributed File System
(DFS) because the session that is reused is against a DFS referral from the
Windows 95-based or Windows 98-based client.

[possibly also related:]

The client computer sends invalid encrypted password information to the
server if the session that has been established between them is reset more
than once. A session on the server can automatically time out, as noted in
the Microsoft Knowledge Base article that is listed in the "Workaround"
section of this article. Additionally, a session on a Microsoft Windows
2000-based computer can be disconnected in the user interface by
right-clicking My Computer, clicking Manage, clicking Computer Management,
clicking Shared Folders, and then clicking Sessions.

You can see a session reset that is initiated by the server in network
traces as a TCP Reset packet on port 139 (NetBios Server service). During
reconnection, the client computer sends a C Session Setup And X server
message block (SMB) for the share. The server returns ACCESS_DENIED in an R
Session Setup SMB.

WORKAROUND

To work around this issue, use any of the following methods:
- Reboot?
- Click Start, click Run, type winipcfg, and then release and renew the DHCP
lease. This essentially resets the entire network stack.
- Open Network Neighborhood, and then double-click the affected server and
share.
- Type net use \\servername\sharename at a command prompt.
- Click Start, click Run, and then type \\servername.

You might also try making sure you have all the latest patches on the
workstations and also try the fix in the following article:
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q293793

For additional information about control of the LAN Autodisconnect feature
in Windows 2000, click the article number below to view the article in the
Microsoft Knowledge Base:
Q138365 How the Autodisconnect Works in Windows NT
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q138365

"Ken Homa" <KHOMA@NFSchools.net> wrote in message
news:0c7b01c27f74$de325690$3aef2ecf@TKMSFTNGXA09...
> This problem is posted in the Knowledge Base under
> Artical - Q272594.
>
> We (the 98 users) were able to sign on to the windows 2000
> server based domain. Just 3 days ago it issues the
> following message "The Domain password you supplied is not
> correct......." This is not true. The account is there
> and the password is correct.
>
> Is there a fix? And what is it?
>
>
> Thanks to all



Relevant Pages

  • RE: Printing from Win9x clients stops
    ... Open Server Management. ... then right-click the name of the computer running Windows Small Business ... >From the client computer: ... The Select Network Component Type ...
    (microsoft.public.windows.server.sbs)
  • RE: Printing from Win9x clients stops
    ... The printers with 9x drivers on the server appeared automatically in the ... > then right-click the name of the computer running Windows Small Business ... > From the client computer: ... The Select Network Component Type ...
    (microsoft.public.windows.server.sbs)
  • Re: random lockouts
    ... >> I've got a network with several Windows 2000 Servers and ... >> about 150 Windows 98 clients. ... >This problem occurs because the Windows 2000-based server ... >because the session that is reused is against a DFS ...
    (microsoft.public.win2000.security)
  • Re: after installing KB011829 OWA is not working anymore
    ... Based on my research, after you install hotfix KB911829, I suggest we ... Profile WMI Provider to each client computer that is running Windows Vista ... If you are running the Premium Edition of Windows Small Business Server ...
    (microsoft.public.exchange.connectivity)
  • Re: DHCP Issues. Very strange
    ... I understand the issue to be: some client computers ... can not obtain IP from SBS server. ... it is most possible a client side issue of Windows ... since you have join it to SBS domain and the Windows XP SP2 ...
    (microsoft.public.windows.server.sbs)