Logon / Account problems

[timbeullens]

Hi guys!

I have a problem on our NT domain.
First off all, our original DC (the only one) had (an has) hardware issues, old hardware that reaches the end of its life i guess.

No problem annymore since i managed to revibe it, and installed a new NT4 server on a virtual machine that is now PDC and has all DHCP WINS and DNS features installed.

BUT...

Since I did this, a new problem occured.

We all (30 people) have 1 user accouns, Administrator...
WORST thing you can imagine! I just work here 5 months, it wasn't my idea

I will install a new deacent 2003 environment by christmas, but for now I have to keep the current system alive and kiking.

There are 6 PC's that give errors when logging in. We all use XP pro pc's. They can login if the network cable is disconnected, but if they are connected to the network, they get the message that the domain controller eather don't excist or is unreachable... after like 15 times the system is able to login.

What I discovered is that the users that have this problem have the account Administrator.PCNAME in stead of Administrator.DOMAINNAME But they all log in with xp with administrator, the domain administrator password and the correct domain selected.

I don't know how this happend or what went wrong when those PC's or accounts where put in the domain (this is the work of the previous IT guy)

I think this might be the problem. But I don't know how I can fix this.

I have verry little experience with NT, and I want to avoid to make new accounts for those people since all settings and outlook accounts will be gone. (or I have to fix things in the registry's to work around)

Please, can annyone give ideas or does annybody recognize this problem and does annybody know how I can fix this issue?


Manny thanx!!!!!

Tim

tim@executiveresearch.com

 

[WhoKilledKenny]

What I discovered is that the users that have this problem have the account Administrator.PCNAME in stead of Administrator.DOMAINNAME But they all log in with xp with administrator, the domain administrator password and the correct domain selected.

This happens because the user is using the Local Administrator Account not the Domain Administrator Account. Since you unplugged the network the account never logged on to the domain. Chances are that your local and domain Admin account uses the same password.

However, the problem you are having is the workstation is unable to find a domain controller. This is usually resolved by checking the TCP/IP settings of the workstation. Verify that DNS and/or WINS settings are pointing to the proper IP addresses of your DNS and WINS servers. If not, make the change and re-boot workstation (NT4)...

Jesse Hamrick

http://www.powershellpro.com

 

[timbeullens]

They all get TCP-IP settings via DHCP that is running on the DC.

So that seems OK

Today, I experienced the same problem as well with my PC.

Verry strange! I have the proper account.

When I disconnect from the network I can log in succesfully. My guess is that XP looks in his local SAM to validate username and password when the PC is not connected to the domain network. But I still don't know what goes wrong when the PC is connected in the domain. Since the computer recieves its settings via DHCP, the DC must be reachable.

Are there certain protocols that must be installed?
I have all protocols and services installed on the DC, but my guess is that TCP-IT and maybe NETBUI are all I need for simple communication.

It's getting a big mistery to me :-s

 

[WhoKilledKenny]

But I still don't know what goes wrong when the PC is connected in the domain. Since the computer receives its settings via DHCP, the DC must be reachable.

You should verify this by:
1. From the PC Ping the domain name. example, ping domain.com
Does it ping? yes - should not be an issue with Network Setting. No- go to step 2.
2. Ping the IP address of the PDC.
Does it ping? yes - Network settings are fine. Must be an issue with Name resolution. Check that the IP Address given out by DHCP are correct. From the PC do the following command: "ipconfig /all" check the IP Address for WINS and DNS to verify you are pointing to the proper IP address. If not, change the scope settings on your DHCP server. Then renew the address on the PC.
Ping = No. Possible mis configured gateway or IP address. Possible issues with Network Cable and possible Network issue all together (Patch Panel, Switch, Router).

Jesse Hamrick

http://www.powershellpro.com

 

[timbeullens]

I found something, not quite sure it will solve the problem but I fixed it annyway.

In my new PDC, the DNS and WINS entrys still pointed to the previous DC... It is still there as a BDC but has no DNS and WINS running annymore...

This server has IP settings manually entered, so it seems that i forgotten to change those settings.

The rest of the IP settings provided via DHCP are correct.

Thanks WhoKilledKenny! It was with your information that I discovered this!

We'll see if it solves annything

 

[WhoKilledKenny]

Great to hear. FYI - Make sure the server that is running WINS is pointing to itself (TCP/IP Settings)as it's Primary WINS server. If you have two WINS servers, make the replication partner the Seconday WINS server.

Jesse Hamrick

http://www.powershellpro.com