Windows 98 getting stuck logging into a W2K3 domain.

[Bloke at the pennine puddle (Replace n.a.v.d with]

The good news is that the symptoms are all the same. As a temporary
workaround I've turned off Windows 98's ability in Client for MS
networks to validate usernames and passwords.

The problem is that at random times Windows 98 pops up a message on
login stating that the domain can not be found, or wrong password.
Sometimes the account gets locked out on the server. Yes, directory
services client for 9x is installed.

Now, turning off the login to domain option on Client for MS networks
allows the workstation to login, but here lies a problem with
remembered driver letter mappings, because login scripts only run when
Client for MS networks does the password validation.

What happens is that the dialogue (`Quick login` used) shosing the
drive letter is being mapped shows and, just hangs.

I can get past this by clicking on cancel, then `Start` and then `Log
off`. At this poing I'm returned to the Windows login dialogue and
possibly an imcomplete dialogue behind that which tries to tell me
that the next drive letter in line can't be mapped.

Logging into Windows a second time works perfectly.

Client and server communications signing is disabled on the Windows
2003 server within group policies.

Windows 95 seems to not to suffer from this problem. Windows 2000
Professional works perfectly.

BEcause of a legacy application, I don't have a choice and the
machines running Windows 95 and WIndows 98 have got to stay. The
legacy application will be redesigned, but this will not be for a
number of months.

Can anyone help me with this annoyiong problem? I would really like
Win9x to validate the login to the domain and also have the facility
of using login scripts as they are supposed to be used.

In a nut shell, I'm stumped. I've never need this sort of behaviour
before.

HELP!!!!!

 

[Pegasus \(MVP\)]

"Bloke at the pennine puddle (Replace n.a.v.d with vodafone.net.)"

The good news is that the symptoms are all the same. As a temporary
workaround I've turned off Windows 98's ability in Client for MS
networks to validate usernames and passwords.

The problem is that at random times Windows 98 pops up a message on
login stating that the domain can not be found, or wrong password.
Sometimes the account gets locked out on the server. Yes, directory
services client for 9x is installed.

Now, turning off the login to domain option on Client for MS networks
allows the workstation to login, but here lies a problem with
remembered driver letter mappings, because login scripts only run when
Client for MS networks does the password validation.

What happens is that the dialogue (`Quick login` used) shosing the
drive letter is being mapped shows and, just hangs.

I can get past this by clicking on cancel, then `Start` and then `Log
off`. At this poing I'm returned to the Windows login dialogue and
possibly an imcomplete dialogue behind that which tries to tell me
that the next drive letter in line can't be mapped.

Logging into Windows a second time works perfectly.

Client and server communications signing is disabled on the Windows
2003 server within group policies.

Windows 95 seems to not to suffer from this problem. Windows 2000
Professional works perfectly.

BEcause of a legacy application, I don't have a choice and the
machines running Windows 95 and WIndows 98 have got to stay. The
legacy application will be redesigned, but this will not be for a
number of months.

Can anyone help me with this annoyiong problem? I would really like
Win9x to validate the login to the domain and also have the facility
of using login scripts as they are supposed to be used.

In a nut shell, I'm stumped. I've never need this sort of behaviour
before.

HELP!!!!!

I have seen a few Win98 machines before that would intermittently
fail to get domain validation. Rather than trying to solve the problem,
I walked around it, by telling the machine NOT to get domain validation,
and by placing this batch file into the Startup folder:

@echo off
\\YourPDC\Netlogon\YourNetlogon.bat

This will get you the usual drives mapped. The only thing you will
miss is central password administration: If the password changes
then you will have to change it manually on the domain controller
and on the Win98 machine.

 

[Bloke at the pennine puddle (Replace n.a.v.d with]

I have seen a few Win98 machines before that would intermittently
fail to get domain validation. Rather than trying to solve the problem,
I walked around it, by telling the machine NOT to get domain validation,
and by placing this batch file into the Startup folder:

@echo off
\\YourPDC\Netlogon\YourNetlogon.bat

This will get you the usual drives mapped. The only thing you will
miss is central password administration: If the password changes
then you will have to change it manually on the domain controller
and on the Win98 machine.

I'm glad I'm not the only one suffering from this problem.

The other issue that remains is sometimes the drives don't want to
map! Logging off and back on again makes it work, but it's not ideal.

I'll give you idea a try I've already got something similar configured
on each computer that I can modify to pick up the official login
script(s).

 

[Pegasus \(MVP\)]

"Bloke at the pennine puddle (Replace n.a.v.d with vodafone.net.)"

I'm glad I'm not the only one suffering from this problem.

The other issue that remains is sometimes the drives don't want to
map! Logging off and back on again makes it work, but it's not ideal.

I'll give you idea a try I've already got something similar configured
on each computer that I can modify to pick up the official login
script(s).

If your drives will not map some of the time then you
should capture the error message and post them here.

 

[Bloke at the pennine puddle (Replace n.a.v.d with]

I have seen a few Win98 machines before that would intermittently
fail to get domain validation. Rather than trying to solve the problem,
I walked around it, by telling the machine NOT to get domain validation,
and by placing this batch file into the Startup folder:

@echo off
\\YourPDC\Netlogon\YourNetlogon.bat

This will get you the usual drives mapped. The only thing you will
miss is central password administration: If the password changes
then you will have to change it manually on the domain controller
and on the Win98 machine.

Following on the post of Windows 2003 servers not logging in, could it
also be that there was a Licencing problem? A week or three before
the server went live, Active Directory screwed up so I demoted the
server to a stand-alone server, re-propoted the server and again
imported all the user accounts from the Novell server.

I've just had a look and noticed that the licence logging server was
disabled. I enabled that then managed to find out that the 19 client
licences were not recorded.

Thing is, not every computer this Saturday gone was loggin in. Maybe
at most three at a time. So, I've re-added the 19 client licences to
the server and, maybe, that will cure the problem? Yeh, but then I
should be so lucky.

Do you (or anyone else) know how many users over the 19 W2K3 server
will allow before denying file and print services? I discovered this
while I'm logged onto the server console as well as two others, and
the server did not deny access.

 

[Bloke at the pennine puddle (Replace n.a.v.d with]

"Bloke at the pennine puddle (Replace n.a.v.d with vodafone.net.)"


If your drives will not map some of the time then you
should capture the error message and post them here.

This is thge point. There is no capture error. It just "stops".

Now, it could have been a licencing problem, but reading through some
text, it was only the licence logging service that was, for some
reason, disabled. I sure didn't disable this service. Also the 19
client cicences I registered were no longer then to I've re-keyd the
magic number 19 in the relevant box.

I manually mapped the drives within the GUI and selected the option to
remember the drive mapping.

Oh, I dunno... I just want it to work.