Most users can't log on

[tbalazs]

I am testing my new 2000 server using a 2000 Pro client on a crossover cable. A bunch of users have been set up on the server but...
only users tony and teresa can log on to the domain, as can administrator. This is true from 2 different client machines. All other users get a message that "the system cannot log you on now because the domain DOMAINNAME is not available".
I have a feeling that something needs refreshing on the server but I don't know what.
Any help much appreciated.
Tony.

 

[danbiggs]

If you have Active Directory installed on your server try logging in using username@fullyqualifieddomain instead of specifying the user and domain seperately, eg bob@domain.com in the user field. This uses DNS to find the domain instead of NETBIOS broadcast.

I'm presuming you have joined the workstation itself to the domain (if you have a domain)?

 

[tbalazs]

Interesting reponse, Dan, thank you, which has produced the following:
Whereas logging on as teresa or tony does work, using their FQDN does not: I get the "the system cannot log you on now because the domain DOMAINNAME is not available" message.
2 questions: does each workstation need the IP address of the server in the DNS field in the LAN dialog box? By joining the workstation to the domain, do you mean simply listing it as a computer in the Computers container? I have done that, yes.
Tony.

 

[danbiggs]

You will need to have the IP address of a DNS server that is aware of your domain in the workstation's LAN settings for the FQDN login to work. And yes, that's what I mean by joining the workstation to the domain.

I'm scratching my head a bit here - did you log tony and teresa on during a previous incarnation of this machine (eg when either was an NT4 machine, or before you made a configuration change that has affected connectivity)?

The reason I ask is that tony/teresa might be logging onto the domain using cached credentials on the workstation, meaning that there is no connection at all to the DC even though it appears that way. Hence other users can't log on.

 

[tbalazs]

I think you are on to something here. For example, logging tony or teresa on the the workstation locally still gives apparent domain access, I have discovered.
How about running dcpromo again and demoting the server? Or will I lose the domain entirely? (There's only the one domain). Tony and Teresa have both been previous users of the workstations, but have only been set up the once on the server.

 

[tbalazs]

The server has had SP2 applied; the workstations are SP1 (or no SP). Could the problem be to do with differring encryption levels?

 

[jrdebug]

just a quick confirmation, how did you add your workstations to the domain? were you able to confirm the procedure as successful?

if you don't mind, can you please give a more detailed information about your setup.

Jeffrey Rebong
Computer Engineer/Network Administrator
jrdebug@yahoo.com

 

[tbalazs]

Thanks Jeffrey.
So as not to compromise the office Win2K Pro workgroup, I have been testing things out using the following:

A 2 CPU RAID 5 Server running Windows 2000 Server SP-2(which was installed at the factory) connected via a CAT 5 crossover cable to either of 2 old PCs running AMD K6-2 500MHz CPUs and Win2K Pro SP-1.

Could you please explain what you mean by confirming as sucessful the addition of the PCs to the domain?

Thanks.
Tony.

 

[GlenJohnson]

Can you ping the server from the machines that can't log on. I've also found that while not needed, hosts and lmhosts sometimes help with just general communications. Also, go to a dos prompt on the users that can't logon, and just type ipconfig /all for the fun of it and see what you can see.

 

[tlcscousin]

You could also try going back to workgroup, and then rejoin the domain. I have run across this once or twice that although I joined the domain, nothing worked properly. Going back to workgroup and then hoining the domain again solved the problem.
Before I went back to the workgroup, some things worked properly and some did not. I spent two days trying stuff, and finally went back to the workgroup, and when I rejoined the domain everything was good.