Discussion Locked

No Domain Server was available to val...

0 helpful
29 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

3 Oct 2000
"No Domain server was available to validate your password. Access to some network resources may be unavailable." error message appears when loggin on to Win98 while trying to conect to my WinNT 4.0 (SP3) server.

I have been stuck on this one for weeks now. I am trying to connect a Win98 PC to a WinNt server. The cable and the card have both checked out as I have swapped components and have witnessed them in action. My NT server (which has four other PC's connected one of whichis running Win98 as well), strictly runs TCP/IP. I used the exact same settings as the other Win98 PC and still no luck. Someone suggested I install IPX/SPX on both the server and the workstation, and that didn't work either. Any help would be greatly appreciated. Thanks in advance.

Jeff Quinn
New Jersey

29 replies

by t dub

Go to a DOS prompt on the Win98 PC and type NBTSTAT -R. If it does not purge the table successfully then remove everything in network neighborhood, reboot and reinstall. I have found that sometimes the IP table gets corrupted and the only fix is reinstalling the entire network neighborhood.

by jeffers

Are you sure the card configuration (IRQ, memory i/o range and media type thinnet, cat5 etc..) is set correctly..and then check the installed config matches what the hardware is set to. Also can you ping any other machines on your network from the command line. The other thing to do is upgrade to SP5 or SP6 (we had authentication problem with RAS giving the same message when we were running SP3).

Also what cards/hubs are you running? you could try downloading the latest driver pack form themanufacturers web site...

Last thing double check all your network settins are correct, IP address, WINS resolution etc..

Goos luck

by jeffers

You might want to try NETBEUI, I have found that it helps with naming issues.

by stacydev

Is the Windows 98 machine plugged into a 10/100 Switch. I have seen this problem when the Spanning Tree Protocol is enabled on a switch. Is the NIC in the Win 98 machine a 10/100 card? If it is try bumping it down to 10 MB and half duplexing. That has worked for me in the past.

After you get the "No Domain server" message you could also try to logoff and back on (No restart). Sounds very stupid, but it has worked.

Last thing I would try if you are using DHCP is to release the IP address in winipcfg.

by baziite

IT doesn't seem like you have subnets or routers on your network , so why don't you try NETBEUI . Its very efficient on small networks . Actually the reason I am saying this is because On WINNT with Win98 clients under TCP/IP you can almost be sure of running into problems , because Win98 does not participate in browser elections on a WinNT domain . So when you logon , Win98 cannot browse into the WinNT domain looking for specific computer names . You can check this by trying to find a WinNT computer from a Win98 under TCP/IP . I suggest you go with a different protocol and remove TCP/IP for good .Do let me know if I've goot this wrong !

Good Luck

by jared

The first thing you need to do is verify that the computer is in fact on the network. Can you ping the server's IP address? Can you ping it by name? Can you map a drive to a share on it? Put the PC into another port on the hub/switch. If you have two subnets make sure the client has a WINS server address. Check the speed/duplex settings on the NIC.

Whenever I get this error, it almost always ends up being physical connectivity, or WINS issues across subnets.

/Jared

by jared

The first thing you need to do is verify that the computer is in fact on the network. Can you ping the server's IP address? Can you ping it by name? Can you map a drive to a share on it? Put the PC into another port on the hub/switch. If you have two subnets make sure the client has a WINS server address. Check the speed/duplex settings on the NIC.

Whenever I get this error, it almost always ends up being physical connectivity, or WINS issues across subnets.

/Jared

by jesses2000

Jeff

1. I am quessing that you have a domain and the win98 connect to your domain (windows NT machine)if this is the case then your windows 98 machine will not be able to be authorised to get in to the domain becouse is not part of it. To add this machine to the domain go in to your Nt server machine and under aministrative tools go to server manager and add the computers "name" in the domain.

2. You better make sure that the user name your are using to log on to the domain through thewin98 machine is part of the domain. Also under network properties on your win98 machine make sure you have "client for microsoft networks" and under client for microsoft networks you check "log on to an NT domain" and the name of the domain.

3. I hope you are not using a duplicate name or IP on that win98 machine. Also is your NT server DHCP if it is you make sure the win98 machine is aware of that and it dosnt have a static ip.

If this does not help sent me an email with a few moredetails on your configuration and i will try to help you.

by dan-o

These are all good answers.

If you are getting no connectivity at all, those answers may in fact help you. One of the things that used to work for me was to change the NetBIOS name of the computer in the Identification tab of the Network Settings. This would often fix problems with Domain Server errors, although it may not be the best solution, particularly if your systems are set up for File and Print sharing. But it usually works for me.

Also, make sure there is only one network cardin the Device Manager. Sometimes several devices show up, even when there's only one physical component in the machine.

Hope this helps.

by jharring

In addition to the other suggestions (pinging particularly) my good colleagues have suggested, run WINIPCFG to verify the IP/Subnet/GW address for your domain is valid.
I have run into some issues w/ WIN98SE where the DHCP server doesn't respond quickly enough to a request and WIN98SE "self-assigns" a 169.x.y.z address. Likely you are not running this network addressing scheme and therefore, the error you experience. This apparently a "feature" included by microsoft for home networkers. "Windows 98 Second Edition Mtsutil.txt" provides details and also provides an INF file which turns off this "feature."
PS Sometimes this "feature" is so stubborn, I have had to assign a static ip address then later when the dhcp server is more available, set it back to DHCP and do a "winipcfg /release" to fix this problem.

by jeffjquinn

17 Oct 2000

Thank you to all that have responded thus far. As of today, I am still stuck with the problem, but wanted to mention that I am able to ping my own card, but the Server does not show up. Second, I am not using WINS or DNS on my server. This is a Windows 98 computer (HP Pavillion) trying to log into a WinNT 4.0 Server (SP3). Thank you again, and please keep 'em coming.

Jeff Quinn

by chris hirst

Well no one has mentioned the obvious yet. So whenever I get this problem on a machine (I babysit a 100 user network) there is usually one of two causes.
1/ Patch Lead Unplugged (No one ever unplugs them?!)
2/ Typing the users password into the domain name entry field

failing this check the domain name for spelling and extra spaces (Thats the obvious one)

by chrisw

I have just encountered the same problem with a WIN NT Workstation logging on to the NT4.0 Server following a server crash and restore. I can ping all computers by name and ip but the logon server is not available and i get entry by cached account information
if i find an answer i will let you know

by wlbowers

Since you can ping your card. And location hardware is good.

Lets go with the simple test.

Look in the event log and see if there are any error messages.

Get rid of ipx/spx

Confirm the machine and user is in the NT user list.

In network neighborhood check for
:log on to NT domain.
Log on and restore connection checked
Client for Microsoft network selected
Machine identification and domain are
correct

If your nic card has lights on it to show activity. Do you get lights. If not there is a connection problem.

Move a working cpu to the nonworking location to verify that the home run is good. If it isn't pull out the wire.

Plug the computer directly into the hub. Work? this will suggest a bad home run as well.

On the server, got to wins manager and look at the tcp/ip addresses. Write down an address that is not used Load this address and the correct subnet mask in to the network config. Enable wins. Enter the server tcp/ip address. It helps the box to know where momma is. Put a hosts file in the windows directory. This tells the computer where the server is when wins fails. There should be a hosts.sam file there to guide you. You can edit it with notepad. Make sure you remove the extention after you save it though. The hosts file doesn't use one

Reboot see what happens.

Good Luck

Lee

by Member 35451619

without wins services running on the network
netbios is not able to resolve which machine
on the network is the PDC for the domain
ie when you type nbtstat -c at a command prompt on the client machine there is no machine registered with
the proper netbios suffix as being a domain
controler to validate login requests
There is a line of code that can be added to
the lmhosts file to correct this problem but
the structure of the line is critical in regards to spacing between data.
email meat michaellambert@mindspring.com
and I will send you a sample of the file
this problem can also occur on a NT 4.0
network where wins services have failed or
the wins database becomes corrupted.

This discussion is closed to new replies.