Adding new computer to domain

[cooper]

Hi 30 of the 32 ict workstations added to the domain with no problem

 

Im getting

 

"the following error occurred attempting to rename the computer the user name could not be found"

 

anyone know whats gone wrong here?

 

thanks

 

Cooper

[Lithium]

How are you putting in the username?

 

As username?

 

or domain\username?

 

I remember after we disabled NETbios, that I had to change it to being FQDN\username...

 

Worth a try..

 

FQDN: Fully Qualified Domain Name... example.blah.blah.blah.blah or hello.local etc.

[technical_man]

Hi

 

domain\username is the norm

 

If you have ghosted or copied disk images across machines? then you need to run SSID.exe to thange security id on each workstation.

[technical_man]

Hi

 

domain\username is the norm

 

If you have ghosted or copied disk images across machines? then you need to run SSID.exe to thange security id on each workstation.

Sorry ....change security id... can email ssid.exe if helps

 

Or getting obvious now but???

 

- are rouge machines named uniquely? B4 attached to network, if not the machine a/c on server disabled?

 

- may sound silly but is rogue machines seeing network? (Ping server, ipconfig etc) reason is, not unusual to have different network card/chip on batches of machines so if ghosted or imaged then maybe driver issue

 

- If not then sometimes network card/chip has trouble initialising so de-install and re-install driver

 

- also some 1Gb networked PC’s on old PIII ‘ish sluggish servers have trouble or on slow 10/100 networks so could try setting to 100mbps instead.

[cooper]

all machines are new and all ghost with the same image giving the same username, i have run an app to give it a new sid, and server is a new d-core running on a gig network.

 

I am going into my computer, computer name change, setting name as

ict-10 and putting name of domain in the domain box.

 

its making connection with the server.

 

Cooper

[FN-GM]

Try making the computer account in active directory first if you haven’t already done. Also it maybe the corporate firewall or windows firewall causing problems. Also try a different network point it might sound silly but it might just be a bit of wiring not just right. Are the machines laptops? If sp try disabling the wireless. Is the computer got a IP address properly from the DHCP server?

[Guest Guest]

Ive seen similar when duplicate computer names are in AD. Might be worth a try renaming the PC while not on the domain and then trying to join. You can always change the names back after

[Phreadlock]

If your using static ip's remove the the computer from the dns host list, it may be listed under ip only.

 

Also as suggested remove from AD.

 

regards Phreadlock

[GlennT]

I agree with j17sparky, try taking it out of the Domain, reboot, rename, reboot then join the Domain again.

[Pumaedition]

when I have ghosted machines, and tried re-naming them, I cant just change the name of the PC, I have to use the whole Network ID Wizard to get it to connect to the network properly...otherwise I get a n error stating that the trust relationship isnt valid between the PC and the PDC....so might be worth trying the Network ID wizard....

[ChrisH]

when I have ghosted machines, and tried re-naming them, I cant just change the name of the OC, I have to use the whole Network ID Wizard to get it to connect to the netowrk properly...otherwise I get a n error stating that the trust relationship isnt valid between the PC and the PDC....so might be worth trying the Network ID wizard....

 

That definately sounds like your not using sysprep or any other software to change SIDs after ghosting.

[cooper]

Fixed my problem by adding the computer to a workgroup then back to the Domain.

 

All ok now

 

Thanks for all the advice given

 

Cooper

[helpmehelpyou]

Yup, same worked for me!

 

Fixed my problem by adding the computer to a workgroup then back to the Domain.

 

All ok now

 

Thanks for all the advice given

 

Cooper