Re: Failed network login!
- From: "Steven L Umbach" <n9rou@xxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 19 Jan 2006 18:31:07 -0600
Since it is a stand alone server that has the share you need to have the
same user account in it's local users that matches the logon/password that
the user is using to attempt to access the share. There could also be an
incompatibility in security settings if you can not resolve the problem and
the link below can help on that with the main possibilities being
incompatible settings for digitally sign communications and lan manager
authentication level. --- Steve
http://support.microsoft.com/default.aspx?scid=kb;en-us;823659
"msnews.microsoft.com" <beme@xxxxxxxxxxxxxxxx> wrote in message
news:eBmNObQHGHA.1452@xxxxxxxxxxxxxxxxxxxxxxx
> Hi All,
>
> I'm having the following problem when connecting via the network to a
> stand alone Win2K server. I make the connection (net use...) from a
> Winnt4.0 machine, using the credentials from a user on the Win2K server.
> The server says: "system error 1326 login denied: bad username or
> password." After a few tries, the account gets locked out.
>
> The thing is: I *can* log in locally on to the Win2k server, using the *
> same * credentials!
>
> For some reason log in via the network is denied. The username is
> recognized (the account gets locked out), the password hash is not.
>
> Any help would be appreciated!
>
> BeMe
>
.
- References:
- Failed network login!
- From: msnews.microsoft.com
- Failed network login!
- Prev by Date: Re: Find security group usage
- Next by Date: Re: logon locally user right needed for terminal server logon?
- Previous by thread: Failed network login!
- Next by thread: -- force clients to get time from the server --
- Index(es):
Relevant Pages
|
|
