Win98 clients login to 2000 server

[Portfox]

I wrote a message about 3 days ago on this and thanks to all who replied.
I still having the same issue when 98 clients trying to login to a 2000 server they are issued with a message ' the domain password you suppied is not correct or access to your logon server has been denied'.
If you 'esc' pass the login screen network access to proxy servers exchange servers are still possible, but network shares arent of course.
I have 1. Restarted the 2k server
2. removed tcp/ip from the clients and reinstalled it
3. gave the client a static IP address
4. reset passwords
5. tried different user name
6. checked dns wins and dhcp settings (all OK)
7. my 2000/NT4 machines have no problem
8. checked group policies
9. installed dsclient for 98
None of the above have rectified it
I have one dns box on my LAn/Wan 2000 and NT4 clients are unaffected.
Any one have any other suggestions

 

[DirtDawg]

Just a quick question. If you go to the 98 machine and try to ping the logon server name, what ip address do you receive? It sounds like you are trying to logon to the wrong server.

 

[Portfox]

If i ping the logon server it replies with the ip of that server.

 

[DirtDawg]

You have said that you have re-installed the TCP/IP protocol. Are the 98 machines a part of the domain or still workgroup? You may need to play with your networking options to find the right setting. I am using 98 and can get all of the shared drives on the LAN.

 

[Portfox]

the 98 machines are part of the domain, i have spent hours and hours tweaking the networking settings, this is a problem with a hand full of 98 machines not just one that attach to the 2000 network. A couple of other machines that have not been rolled out of the NT4 domain are OK and not experiencing the problem. It happened over a weekend which is very strange, no admins have touched any settings on the 2k dc which makes it more of a pain.
The only thought i had was to upgrade the PC's to 2k pro and wash my hands of it, but if i do that i know that it will eat at me because i didnt resolve the issue.

 

[DirtDawg]

Can you create a new test account. Give it the same permissions and try to log on to the 98 machine? Check the 98 machine how many .pwl files exist? Maybe there is something in the local user profile on the 98 machine that is cached? The login work fine on a NT or 2000 machine correct? There is nothing in the servers eventviewer?

 

[Portfox]

Servers event viewer shows nothing, .pwl have been deleted because i thought that was the problem.
I've tried about 10 user accounts but none work on th98 machine. All those accounts work on NT/2000 though.

Are you starting to scratch your head yet?

 

[Niavlys]

Do you have more than one network adapter in your server?

 

[1sexypapi]

have you tried installing the dfs client software on the 98 machines?? for 98 clients to access 2K resources DFS needs to be setup

 

[PhillipFoster]

When you created the computer in Active Directory->Users & Computers, did you tick the "Allow pre-Windows 2000 computers to use this account"?

If you can't remember, you'll have to delete the computer from AD and re-add it, as (AFAICS) there's no way to change this.

 

[zoeythecat]

You mentioned you have DHCP + WINS. If you do, than you do not need a static IP Address. Try these steps.

(1) Change the TCP/IP Settings back to "Obtain an IP Address
automatically from a DHCP Server
(2) On your Windows 98 verify what your IP Address is.(WINIPCFG)
Make sure you are getting an IP Address from the
DHCP Srver
(3) Recheck your DHCP settings. Make sure any settings
for downlevel clients are selected. Also check to
verify that your Windows98 workstation is receiving
an IP Address from here.
(4) Check your WINS again. Make sure you see this W9x
computer name in here.
(5) Also, try making your DNS settings to point to the
DNS Server (Here is a question and answer from MS)
Question: Do I need to point computers that are running Windows NT 4.0 or
Microsoft Windows 95, Microsoft Windows 98, or Microsoft Windows 98 Second
Edition to the Windows 2000 DNS server?

Answer: Legacy operating systems continue to use NetBIOS for name resolution to
find a domain controller; however it is recommended that you point all computers
to the Windows 2000 DNS server for name resolution.

 

[Portfox]

Yep I have done all of the above, i really think it is a protocol issue and have done some reading on the NTLM protocol which 95/98/NT4 uses to authenticate to a 2k dc.
Thanks for all your help
If you have any other ideas please suggest them

Cheers

 

[slr22]

I'm having this same problem with our 98 machines, did you ever figure out a way to resolve this issue?

Thanks,
Sandy

 

[triangleman]

I had been having the exact same problem. I finally got it resolved by going to TCP/IP Properites in Network Settings and unchecking the LMHOSTS Lookup checkbox. Hope this helps.

 

[GlenJohnson]

I've seen this when a nic starts going bad on a server. Pre w2k machines are affected first because they don't have the same setup the w2k machines have. Check your nic for bad broadcasts. What happened to me, the users sometimes couldn't authenticate, kept getting worse until users couldn't authenticate at all. Stumbled accross the awnser while re-booting the problem server and people logged on, authenticating through the other server. 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.