Win98 clients have problems logging into Windows 2000 Server domain 1

[tcflick]

I have a mixed Win98/Win2000 network accessing a Win2000 server acting as the PDC. Win98 clients are having problems logging into the domain and have name resolution issues. The Win2000 clients are having no problems. In most cases the Win98 user enters the correct password but after a long delay receives the message of incorrect password. Ctrl-Alt-Del will display the message "mprexe (not responding)". I have tried a number of the fixes suggested for mprexe problems and none of them work, or at least not for long. An interseting work around is that if the user enters an incorrect password when they first attempt to logon, the second logon attempt works fine. This was not a problem before Thanksgiving, but has been ever since.

 

[InfrArch]

Hello,

Did you installed an AD Client for W98?

Victor K
psas@canada.com
MCSE+I;MCSA;MCSE(w2k);CNE(5.1);MCNE(6);CIWSP;CIWSA.

 

[tcflick]

Victor K,

I do not have the AD client installed on all of the Win98 clients. Prior to this being a problem it was not installed on any clients and from a suggestion in another forum I installed the AD client on two machines and it does not appear ot have solved the problem, both machines still have login difficulties.

Thanx,

tcflick

 

[CharlieJax]

Your windows 98 clients are trying to connect via NetBIOS, you need to make sure your Windows 2000 machines are taking NetBIOS as well.

You could try adding your domain information to your LMHOST file on the Win 98 PCs or check and make sure your server is using NetBIOS over TCP/IP (and check that on the 98 machines as well) CJ
Don't listen to me, I wanted to be a forest ranger.

 

[InfrArch]

Hello, again

Please, check the following:
1. is there any AD replication problems in your network. It can be the reason of your problem.
2. do w98 PC ALWAYS correctly see w2k DC? Try to implement a WINS service. or just update a HOSTS file on w98 pc's with the pointer to w2k DC.

Please, write your results.

Good luck.

Victor K
psas@canada.com
MCSE+I;MCSA;MCSE(w2k);CNE(5.1);MCNE(6);CIWSP;CIWSA.

 

[GlenJohnson]

This was not a problem before Thanksgiving, but has been ever since. Has anything changed on your network that you know of, upgrade sp's on the server, etc? Have you seen

http://support.microsoft.com/default.aspx?scid=KB;en-us;q178084

Glen A. Johnson
Johnson Computer Consulting
MCP W2K
glen@johnsoncomputers.us



"There is only one good: knowledge; and only one evil: ignorance."
Socrates (470- 399 BC); Greek philosopher.

 

[tcflick]

CharlieJax - I am pretty sure all of the Win2K machines and the Win2K server are using netbios, but I did add the LMHOSTS file to a few clients and it appears to be working, but I am not to optimistic yet because the other fixes also worked but only temporarily.

GlenJohnson - That's the rub. I did not make any changes between when it was working and when the problems started. This system had been in place for over a year before any problems arose.

 

[Gifted1]

Are you using Wins on the Win2k Server. If not you will want to run it and also make sure it is authorized. If so try putting the wins address on the 98 machines istead of letting them get the info from DHCP.

 

[havanajoe]

If you are using WINS on your 2K server then it could possibly be that the WINS database is corrupt. I have seen this in the past with 98 clients not being able to contact a 2K sever for authentication, the problem was in deed a corrupt WINS database. I hope that this helps.

 

[CharlieJax]

The LMHost file will work forever, unless you change the address of the domain controler.

Since the LMHost file is working, then your problem is netbios. You can try setting up WINS on your W2K server, or if you already have it running it maybe that it has failed or is not starting correctly.

This would explain why the machines have all of a sudden stopped being able to get to the server.

I'd place money on it being a NETBios issue. CJ
Don't listen to me, I wanted to be a forest ranger.

 

[GlenJohnson]

Check any and all servers for nics going bad sending out bad broadcasts which will confuse pre-w2k machines first. Voice of experience here. Put a new server on-line. People started having problems autheticating after a couple of months. Finally, no 98 machines could get on domain. Set up a monitor for outgoing and incoming bad broadcasts. The brand new server had a nic sending out bad broadcasts. Changed it, things went fine. It's not always software causing problems. Glen A. Johnson
Johnson Computer Consulting
MCP W2K
glen@johnsoncomputers.us



"There is only one good: knowledge; and only one evil: ignorance."
Socrates (470- 399 BC); Greek philosopher.

 

[GlenJohnson]

Yes, the nic problem would explain why w2k and xp works. Are you using wins? It's used for pre w2k machines, so if your'e not using it, machines would have problems. I know the wins database corruption whas mentioned by CharlieJax, but you didn't say if your'e using it. Good luck.

Glen A. Johnson
Johnson Computer Consulting
MCP W2K



Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884
"Study not to know more, but better."
Lucius Annaeus Seneca (2 BC-65AD); Roman philosopher.

 

[Redfox1]

I'm having similar issues. NIC card is fine on the server, W2K, XP and NT 4.0 clients all login fine. I just posted a different issue I came across: when I dial into my DC (running DHCP, DNS, WINS + RAS) the DC registers in DNS with the RAS client's IP as ANOTHER DC!!!



I'm curious as to what a dcdiag, ipconfig and a netdiag indicate on your systems. (You may have to install the Support tools from the W2K Server CD)
Run a "dcdiag /v > c:\yourdomain.txt" and a "netdiag /v /debug >> C:\yourdomain.txt" and an "ipconfig /all >> c:\yourdomain.txt"
Look for anything that fails. Chances are that you might come upon the problem. Windows 98 client are VERY prone to WINS issues...

DO you have a WINS server? If so, I would recommend getting "Ethereal for Win32" -GNU free- and place it between the DC and one such PC that's having a problem. Look at the trace... see what the downlevel client are trying to do...

Redfox

 

[GlenJohnson]

I just posted a different issue I came across: when I dial into my DC (running DHCP, DNS, WINS + RAS) the DC registers in DNS with the RAS client's IP as ANOTHER DC!!!

Rouge DHCP server? Just wondering.



Glen A. Johnson
Johnson Computer Consulting
MCP W2K



Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884
"Study not to know more, but better."
Lucius Annaeus Seneca (2 BC-65AD); Roman philosopher.

 

[BWilson77080]

sounds like a WINS issue to me too, unless there's a router between the clients and the WINS server, then you could maybe check to be sure NBNS broadcasts are being passed through it.

try removing and reinstalling WINS over the weekend, the corrupted database does sound like the issue

 

[iseult]

Assuming you are using DHCP on the Server, enable DHCP on the 98 box. Disable DNS, WINS, and Gateway on the 98 box. LMHosts, Hosts, and ADClient are not needed on the 98 box. The most important thing on the 98 box is this: make sure the workgroup name in network properties is your domain name (e.g., if hq.mp.local is your domain name, put "hq" as the workgroup name). Finally, be sure the same domain name is entered under "client for microsoft networks" at "windows NT domain." If your Server is set up correctly, this should work. Regards.