Discussion Locked

No domain server was available - error

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

Using Win98SE client. Connecting to NT4 Domain. Getting error:

No domain server was available to validate your password. You may not be able to gain access to some network resources.

If I do Cancel or OK, then all programs are available usingTCPIP protocol. I have tried removing client for Microsoft networks and protocols. Not yet the interface drivers. I also tried re-running setup to the same C:\Windows\ directory. Is there a tip to try before installing Windows from scratch?
Thanks in advance.

14 replies

by butlerchuck

I am a bit confused bye your question? If you have no domain server then any program that you try to reach will not be avlible to you. That is, if you trying to reach things inside the domain? Can you dee things in network neib? what do you mean"all programs are available using TCPIP protocol." Could you give more info: You are using network programs? You can see servers? You can ping servers? The answear to these wuestions and a little more info would be a of great help. Also, try somthing like \\yourserver\yourfile if files show up clilck on them. Can you open the file? please post info.
Chuck

by fleon

Yes there is Domain Server. Even getting the error message, folders within the Domain Server are available if I have security setup to access. If i try using Network Neighborhood can't browse the network. By saying all programs are available that uses IP protocol I mean, Outlook e-mail, Telnet to Unix servers and IE to browse the Intranet and the Web all work within the client hard disk. Yes I can ping servers. Hope this helps you.

by jimjennings

Check to make sure that you are logging onto the right domain (network properties, and then the properties of the microsoft network service) and that you are using an id and password that are valid (and not locked out). You may actually be logging into a BDC (backup domain server) at your site. If this is the case, you may have a synchronization problem between your PDC and BDC, probably with WINS.

by fleon

I am looking into this. The LAN on this network segment is small only 5 PC's and 3 printers. There is of course no PDC or BDC. The logon information gets accessed remotely via the PDC or BDC on other locations. However the WINS portion you suggest is a possibility since I do not remember seeing the setting on the WINS section, for primary and secondary. WIll give it a try and let you know later. Thanks.

by jolly roger

Does the third line of the Login dialog box appear and does it contain the correct domain name? If it does not appear, click on the button which will show it (I can't remember the button name) and confirm the domain name is present and is exactly right.

by fleon

Yes the domain name field appears there and Yes the name of the correct domain is entered.

by butlerchuck

We have lots of consoltants here. some have nt and some have 9x. I find that changing all the nework settings to exactly what are standerds are does not always work. For instance yesterday after reading this I had a guy come in with nt that I could not get on the network. He was able to get on after a chaged him from logging on to a domain (our domain!) to logging on to work gorup. The work group was the same name as are domain. This is the first time that I have had this happen. The point is just play with the network settings. Right every thing that you change down. Incase you need to put it back. The previous guy is right about the msclient and making sure that you are logging in to domin. when you click on it and it opens youcan put the domain name in the box and put a check mark in loginto domain. If this is not done you still can use apps. If you are using dhcp or static Ip. So this means your tcp/ip is configuerd corectly. Your apps prove that. Did you set outlookup with nt athentication for domain pasword in the client settings? If you did and you are getting promted for a password then this is a good sign that you are not logging in to the domain. The same goes with IE if you are using proxy along with your firwall, and you have the ip address for proxy in IE you should only get prompted once for your password. If every time you open ie or a new window you get prompted you have two things going on. one you are not hitting the proxy and you are going stright to the firewall. two you are not on the domain. Granted this all depends on how you have every thing configured. I hope that this will help you pin point the problem. I don't think that reinstaling windows is a good idea in less you arepresssed for time. It is better to figure this problem out. KIT

by fleon

Yes the box for the NT domain name is there and it is the correct domain. The TCPIP setting is static and works fine because all applications works well after Cancelling or OK'ing the error bootup message. Outlook is configured to authenticate agains the NT account. Normally the first logon to NT is necessary to get to the email without a second login prompt at the time of the startup of Outlook application. On this PC, even when user cancel the first error message, Email is available without a second login prompt. I will play around with the network settings and inform later today about the results. Thanks.

by larromac

Look for computer name conflicts.
Also make sure that your loginID IS NOT the same as your computer name.
I hope this helps.

by fleon

The login name userid is different from the Network computer name. There are no name conflicts.

by it tech

Check the Identification tab on you 98SE machine amd set your workgroup to the same name as you NT domain, it fix my problem which was the same thing you are describing. I could use tcp/ip, ping other computers, but could not browse Network Neighborhood. Making the workgroup the same name as the domain on the workstations fixed the problem. Hope this helps.

by fleon

What I ended up doing was entering the WINS server information into the TCPIP properties tab related to WINS. THis fixed the problem.

This discussion is closed to new replies.