Networks

Ask something
Discussion Locked

No domain Server available ...

0 helpful
11 replies

by microsloth 1 view

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
We have a small network, alternatively using Win95/98. When logging on one gets the following msg: "No domain server was available to validate your password ..." However, even though it says it does not log the users on, users are still able to access network resources such as the internet, exchange as well as other remote servers. We are not using DHCP. Any ideas?

11 replies

by tin.na

You may want to check the network setting, as well as the connection of your network. I encountered the same problem before, it was on the network, one of the hub had been switch off accidentally by the users.

by w6sa

I am assuming that you were able to validate prior to this time. What has been changed on your network? New equipment? New Software? New settings?

We had a similar problem after someone came in and installed new switches on our network.

Maybe this can be solved with a little more background information.

by microsloth

To be quite honest, I'm not too familiar with this network's settings as I started here a week ago. Apparently this has been happening for about 2 weeks now. It doesn't really cause any major problems, except that we are unable to browse the remote network, only the local one. According to the tech who was here on my arrival, no changes were made to the system. Also, the admin on the remote network says the problem is not on their side. So, what to do?

by gmscne

That message just means that the services provided by the domain server computer are not available. Obviously most of the network itself is functional. Perhaps the logon service on the pdc has been interrupted. Check it and its dependencies for status.

by vh_s

Hi,

Analysis of the situation:
Workstation working fine
Server working fine
Cable connection no problem

To my opinion, this typical thing might have been caused by 2-3 things:

1. bad driver
try reinstalling driver by removing it first from the network applet, shut-down and reinstall driver

2. Windows network requires 3 names to be similar,
a. workgroup name, which in your case should be fine
b. domain name in access control, which define how user on that typical workstation could access shared resources. Should be ok too.
c. (this is in your case the most important thing) name of the server in Client for Microsoft Network (in Network Applet in Control Panel), which define where it should log-on to validate users. It seems that different name than the other two have been used here. Try to validate it cautiously, as I have experienced putting a blank space followed by the name of the server, which caused wks didn't recognized the server, as blank space is also countedas a character.

by microsloth

Thanks for the reply ... unfortunately, it wasn't of any help. Nevertheless, it is good advice, those were some of the first things I had a look at when troubleshooting this net. This problem is really mystifying ... and most likely I will kick myself VERY hard when I find the source. ;-p

by vh_s

Sorry..sorry..

Correction to my previous answer

2.c. >>
Not the name of the server, but the domain name. Apology...

This discussion is closed to new replies.