[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 337
  • Last Modified:

Windows 98 clients on Windows 2003 Server Domain logon problems if users have a password

The specific problem I have is that having set up a Windows 2003 Server with a variety of clients from Windows 98 to Windows 2000 to Windows XP, the Windows 98 clients seem unable to process a logon if the user has any password at all.

Win 2k and XP clients have no problem but trying to log on from Windows 98 results in the error message about your domain password being incorrect or access to logon server being denied.  If you then reset the user's password to blank you can successfully log on from any client including Windows 98.

I have tried the Microsoft solution in Community Solutions Article 555038 but to no avail.  So I have installed IE 6, Enabled NTLM2 Authentication, Enabled SMB Signing, installed DSClient etc.

Is it to do with the default policies that are put in place on a Windows 2k3 server?  If so what ones do I turn off? I step by step guide would be useful.
0
Phill_b1
Asked:
Phill_b1
  • 5
  • 4
  • 3
1 Solution
 
dokpikCommented:
Do you have WINS installed, if not do so and this will fix the problem..
0
 
dokpikCommented:
98 as well as 95 machines rely on netbios to communicate through the network and since 2003 utilizes DNS, these machines cannot communicate with the network even if DNS is configured properly on them....just make sure you install WINS and set it up correctly.......I went through the exact same problem during a migration after installing and configuring WINS the 95 machines even worked.

Good Luck,

dokpik
0
 
Phill_b1Author Commented:
WINS is installed on the 2k3 server and it appears to be running ok.  The Windows 98 clients point to the 2k3 server as the DNS server and the WINS server.  I noticed that the option to use NetBIOS over TCP/IP was greyed out in the Network properties of the 98 clients.

Should I follow the Microsoft solution at all?  Do I need to install DSClient?  I did all the reg fixes in 98 as per Microsoft instruction, couldn't find the article to do with hotfix Q323466.
0
Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

 
crissandCommented:
Install DSclient. Configure all workstation to authenticate from the domain (I guess you've done that), and, when compouter starts to see:
User name:
Password:
Domain:
Use the netbios name of the domain here.

Run the next registry file on all workstation, to disable saving windows password:

REGEDIT4

[HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\Network]
"HideSharePwds"=dword:00000001
"DisablePwdCaching"=dword:00000001

Restart wins service on the server.
0
 
dokpikCommented:
Install the DSClient from a 2000 Pro CD not the one from the download site. Send me an email at administrator@sjhsnights.com with address and I will send you the client I utilized.
0
 
Phill_b1Author Commented:
dokpik, I tried sending you an email but it bounced back.

I've got a 2000 Server CD so I presume I have the correct DSClient.

Do I need to change any default Group Policy settings on the server?  Like setting LM and NTLM responses?
0
 
crissandCommented:
As I remember the default is good enough.
0
 
Phill_b1Author Commented:
Thanks.  Will try it this week.
0
 
Phill_b1Author Commented:
Have tried just putting DSlient on the client computers on one of my customers' networks and its no different.  If the user has no password you can log straight in, but if they have any sort of password at all then you get the message and you can't log in!
0
 
crissandCommented:
The user must have a domain password and the computer must get the user list from the domain. Do you have the logon screen:

User name
Password
Domain

Have you run the reg file I wrote?

How Windows starts, in the network properties there is Windows Logon or Network Logon? It must be Network logon.
0
 
Phill_b1Author Commented:
Yes I did everything you said but still the same problem.

I am sure it is server related as I connected some Win 98 clients to an existing Win 2k3 server successfully.  The installers of this server must have done something to allow them to connect because I didn't and I didn't do anything to the Win98 clients to get it to work.

I thought that there must be a policy somewhere that has been disabled.
0
 
crissandCommented:
Verify the nic of the server: The Firewall must be disabled and the Authetication to be disabled too. Go to TCP/IP properties and enable netbios over tcp/ip.

On windows 98 you don't have ipsec, so disable it on the server. If you enable it, download and install the client from microsoft: http://www.microsoft.com/windows2000/server/evaluation/news/bulletins/l2tpclient.asp

The Group policy does not apply on Windows 98. The kerberos authetication does'n't work.

I think this is enough.
0

Featured Post

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

  • 5
  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now