Windows Forum

Ask something
Discussion Locked

Can't log into domain anymore

0 helpful
17 replies

by iphicles 1 view

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

I have a NT 4.0 server (sp6)and 2 Win2K (sp3) workstations. Server acts as a PDC/DHCP/WINS/Print server. all of a sudden, my workstations are logging in with cached accounts because the event viewer says it can't find a domain controller. i can ping the server and workstations by ip and netbios name. the workstations are listed as DHCP clients on the server and can be seen from the server in the network neighborhood (but i can't explore them).
can't browse the network from the workstations, either.
Netbios over TCP/IP is enabled. I've even tried using LMHosts files to no avail.
On the wins part, my pdc is listed with the 1C code as the domain controller. users are in the administrator group.
haven't installed anything new; it's just that all of a sudden, they can't log into the domain anymore. haven't tried removing them and then adding again cuz i don't wanna have to reinstall all the programs again. any ideas?

17 replies

by singlasandeep

Hi have u tried by creating a new user account & logging with the new user account from any woin2k server.
It may happen ur PDC is not able to authenticate any users also or it does not find any profile.

Also check the permissions on profiles folder, users must have full rights on individual's profiles.
i believe ur problemn will get solved with this.

regards

sandeep singla

by iphicles

I only have one server on this LAN (NT 4.0). I've tried mutiple logins with users. Even domain admins aren't authenticated.

by joseph moore

Weird.
You state that you used the LMHOSTS file "to no avail." But, did you put in 2 records in the LMHOSTS file? People often times use LMHOSTS incorrectly.
For example, let's say your PDC is 10.1.1.1 with a NetBIOS name of MYPDC, and your NT domain name is DOMAIN. The 2 records you would put in the LMHOSTS files on all of your client workstations would look like this:

10.0.0.1 MYPDC #PRE #DOM:DOMAIN
10.0.0.1 "DOMAIN \0x1b" #PRE

You need to define the PDC name and its IP address. You also need the #PRE commands; they force those records to be loaded in. If you forget the #PRE, then the records are NOT loaded by the OS. People often forget the #PRE.

Here is a Technet article on LMHOSTS usage:
http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q180094
(please remove any spaces)

hope this helps

by ian mclaws

Didn't by any chance rename your domain, did you?
Seriously, here's a bunch of thoughts...Take a look to verify that the NETLOGON service has started on the server. (also check the event logs for clues...
You might want to enable auditing of domain logons, both success and failures, to get more clues. If you can get your hands on a copy of the Win2K resource kit, there's a tool that can check a PDC's ability to authenticate.
After you are logged on with cached credentials, can you access shares on the server? What message do you get when you try?

Hope some of this jumble is helpful.

Ian

by iphicles

I did rename my domain, but I rejoined the 2 workstations successfully. then all of a sudden, after about 2 months, i got this problem. have verified that NETLOGON is on. after cached login, I can't browse the network, I get "the server is not configured for transactions" error. as for the event viewer, i get successful logon of all the user names i've tried:
Successful Logon:
User Name: michele
Domain: WLVILLAGE
Logon ID: (0x0,0x162E7B)
Logon Type: 3
Logon Process: KSecDDAuthentication Package: MICROSOFT_AUTHENTICATION_PACKAGE_V1_0
Workstation Name: \\MICHELE
then immediately, afterwards i get:
User Logoff:
User Name: michele
Domain: WLVILLAGE
Logon ID: (0x0,0x162E7B)
Logon Type: 3
this entry isrepeated several times, all within 2 seconds, in the event viewer. now that you mention it, i think i should concentrate on these entries, more. any more ideas?

by pocono

Just to cover everything...make sure you check your NIC on the server...Peace

by trece

Anything odd in the event viewer? I have this problem from time to time with an NT server I have due to Liscense violations. A reboot alwaws fixes it though.

by iphicles

check comment to answer 3. any ideas why the entries would repeat like that? and i've tried multiple reboots.

by iphicles

i get this error (summarized) in the event log of the win2k workstations: "there are no NT domain controllers. network address is invalid" or "no RPC servers".
also, on PDC, when I browse my LAN, i can see the win2k workstations, but when i try and double click them, i get "there are currently no logon servers available to service your request". but NetLogon is running.

by canucker

run nbtstat -c from cmd line

see if old domain name is still cached, if so nbtstat -RR will refresh and reload

also check WINS for old domain records depending on your scavenging intervals they still be in there causing confusion

by iphicles

yep, already tried that. the only nb names that show are current. my WINS server is listing only good names, too. thanks.

by daveg

We have run into issues regarding the secure channel that needs to be established between the domain controllers and workstations. We used NETDOM from the NT resource kit to reestablish these connections when they fail. You can use NETDOM for member servers, bdc, to reset the secure channel. If there is no secure channel, it says that no RPC service is available. I didn't see this in all of the answers, thought maybe it might help.

by iphicles

o.k. i just redid the server and had everyone rejoin. i noticed that my server was infected with the egghead virus. not sure if this could cause my problems, but after redoing the server, everything is working.
thanks for all the advice.

This discussion is closed to new replies.