Link to home
Start Free TrialLog in
Avatar of jjrunner
jjrunner

asked on

Win 2003 and Win 98 Clients

I have a problem that is driving me crazy.   I have a new windows 2003 server that i am trying to connect all my client machines to.   All of my Win XP and 2000 clients work fine.   However, I have just started working on a 98 client that I have and I am having problems.    I have run the DSClient on the 98 workstation, and have configured all the netword and logon settings.  What makes no sense is that I can log on as myself on the computer and log onto the network server with no problems.   Which at first led me to think this was a rights issue.  However, after giving her every right under the sun, she still can not log on the the server.   She has more power on the network now than i do, and i am the network admin.   Anyway, I get the error message saying "The Domain password you supplied is not correct, or access to your logon server has been denied."   I have made sure that the password is correct, I have scanned the registry on the workstation taking out any mention of her name, but still no luck.  I don't know what else to try.  Any assistance would be appreciated.  
Avatar of stevenlewis
stevenlewis

the first thing that comes to mind is password complexity
does her password meet the complexity requirement?
also what shows up in event viewer?
Avatar of Renante Entera
Try to follow the steps given by the Microsoft Support regarding your problem.

This is the site :

    http://support.microsoft.com/default.aspx?kbid=272594

Goodluck!
eNTRANCE2002 :-)
i have an identical problem which i resolve each time by changing the client machine ip address.

As per the MS workaround but if u dont use dhcp just change the ip address.
Avatar of jjrunner

ASKER

I am using a static IP address, and i have changed it on the workstation, but still can not log on as the other user.   I can log onto any other machine as the user, but not this one.  

Here are the security event viewer stats that i am getting:

    Event Id:  529
    Logon Failure:
    Reason:  Unknown user name or bad password
    User Name: Judyd
    Logon type: 3
    Logon Process:  NTLMSsp
    Workstation Name \\WS144

    Event ID:  680
    Logon Attempted by:  Microsoft_Authentication_Package_V1_0
    Logon Account:  Judyd
    Source Workstation:  \\ws144
    Error Code:  0xC0000006A

i can ping the workstation from the server, and the workstation can ping the  server by IP address and by name.  I can still logon as myself, but it will not let Judyd logon.  
     
     
Yes, her password does meet the complexity requirements, it will let her logon on other machines.    There is nothing in her account that i can see that should keep her from logging on.  
Possibly cached user password.

delete *.pwl from the Win98 system, reboot and try again..
yes, i had thought of that as well, and tried it, and it did not work either.   Is there any other place that might cache user information?
Ok, to make matters even more confusing is that I can not log onto the network with this machine with the network "Administrator" account, or any other user account, except for my own.    
Mostly Win98 passwords are cached in .pwl.  It's been a long time - I think you can create a persistent network logon in registry (manual or poledit).  I will look at this later.

Are you using DFS to share?  Logon as yourself and check for persistent network share or mapped network drive and remove them.

Check the following articles to see if it's related to your problem.  You may need to run poledit and see if the particular user-ID is persistent on that Win98.

http://support.microsoft.com/default.aspx?scid=kb;en-us;272594&Product=w98
http://support.microsoft.com/default.aspx?scid=kb;EN-US;278558

cheers
Well, after trying everything, I finally gave up.   I just fdisked the machine and installed Win 2000 on it.  I could not spend any more time on it.   I appreciate the assistance and all the advice, i just was not able to get it to work in my situation.    
ASKER CERTIFIED SOLUTION
Avatar of Gnart
Gnart

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Gnart, thanks for your continued assistance, even if it might not have given me my final solution, i learned some things in the process.    I do appreciate the effort.  

Similar problem.
But in my case this problem cropped up all of a sudden.
The machine has 98 running on win2003 domain. 98 machine worked fine till yesterday evening
& even logged successfully this morning but SInce the used had to restart it after installing a printer . It refused to log on to the domain. I released the complexity level of password. reset the users password asking the user to change the password at next logon,
The 98 user got the dialog box stating ' your password has expired & requires a change'
The new password is accepted well but the machine ultimately fails to logon to the domain
I know this one has been left open for a while but I belive I have a solution.

I had to call Microsoft for this one but it seems to work.

here is how I am able to connect win 98 machines to our 2003 server.

1) install DSclient
2) the following is a reg file that you need to copy in to a file like c:\windows\desktop\server.reg, Please note the couple of enteries you need to change for your network they are in []'s:
-------------------------------------------------------------
REGEDIT4

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\lsa\MSV1_0]
"NtlmClientSec"=dword:20000000

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\lsa]
"LMCompatibility"=dword:00000003

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\VNETSUP]
"LMAnnounce"="0"
"Directhost"="0"

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\MSTCP]
"EnableDNS"="1"
"Lanabase"="0"
"Domain"="[YOUR INTERNAL DOMAIN]"
"NameServer"="[IP ADDRESS OF YOUR INTERNAL DOMAIN SERVER,INTERNET DNS SERVER1,INTERNET DNS SERVER2]"

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSNP32\NetworkProvider]
"AuthenticatingAgent"="[IP ADDRESS OF YOUR SERVER]"
"LogonDisconnected"=hex:00,00,00,00
"Name"="Microsoft Network"
"ProviderPath"="msnp32.dll"
"Description"="Microsoft Network"
"NetID"=hex:00,00,01,00
"CallOrder"=hex:00,00,00,40
"DisableReLogin"=hex:00,00,00,00
-------------------------------------------------------------

3) after saving the above run it. then say yes or ok (i can't rember)

4) goto start > settings > control panel > network
a) click on network neighborhood and select "Client for Microsoft Networks"
b) click properties
c) check the box for "Log on to Windows NT domain"
d) click ok

5) click ok to leave the network properties window and apply your changes, it will propably need the windows 98 disc. don't restart yet

6) get your windows 98 cd if you have not already, and do this:
a) goto start > run
b) type "sfc" (no quotes) then press enter
c) type "vredir.vxd"
d) click start
e) browse to your windows 98 CD or type it (mine was d:\win98\)
f) save file in : "c:\"
click ok
click start
click close

7) goto start > run
a) type command
b) type "path=c:\windows\command"
c) type "attrib -h -r -s -a c:\msdos.sys"
d) edit c:\msdos.sys
e) look for a line that says "bootdelay="
          i) if you do not see one add it under [Options]
f) have it read like this "bootdelay=5"
g) goto file>save (if it asks to save say yes)
h) file > exit
i) type exit

8) restart machine (start > shutdown > restart , OK

9) when you see the words "Starting Windows 98" press the F8 key until you see a menu
a) do "command prompt only"
b) type the following:
c: (then enter)
cd\ (then enter)
cd\windows\system (then enter)
copy c:\vredir.vxd c: (then enter)
y (then enter) (you are going to replace a system file)

10) type win (enter)

this will restart windows and you will hopefully be able to connect to the domain.
I have short and dirty alternative that has worked - goto the Windows 2003 Server Local Security Settings, Local Policies, Security Options and DISABLE the Policy that says Domain member/Domain Server: digitally encrypt or sign secure channel data (always)
you must have been on the same course as me solutionsx

i was at MS yesterday and we covered this problem. It is related to levels of data encryption used for file sharing and such. The dsclient.exe is designed to fix this for nt4 and 9x clients but the expected level of (smb) file sharing encryption can be reduced to fix the problem. this will decrease the overall security of your network.
gl