Can log on Local can't log on to domain

[speckytecky]

I'm setting up as few computers onto a network at the moment, all set up to the domain OK but now they are moved to the classroom two will only log on local. No probmlems seeing the network or connecting to internet. Any ideas please folks?

[SYNACK]

Any error message or event log errors? Hows DNS in your new location ("nslookup servername")?

[FN-GM]

Come-on your like one of the teachers with the sketchy details ;-)

 

I would check your IP addresses and make sure you haven’t got anything else on the network leasing addresses out.

[speckytecky]

Nslookup is ok it's just when I switch to the domain and try to logon that it tells me it can't find the domain - grr!

[SYNACK]

can you do a lookup on your fully qualified domain name, ie networkname.schoolname.school.uk ?

[FN-GM]

Are the clients on the same IP range as the servers?

[speckytecky]

can you do a lookup on your fully qualified domain name, ie networkname.schoolname.school.uk ?

 

Yes and again that comes up OK?

[speckytecky]

Are the clients on the same IP range as the servers?

 

Thanks FN - no problems there. I have tried everything and every wich way I can think of but still no joy!

[FN-GM]

Thanks FN - no problems there. I have tried everything and every wich way I can think of but still no joy!

 

So you have tried them on the same IP range as the server?

[RabbieBurns]

try logging on local as admin and see if re-joining them to the domain works

[speckytecky]

try logging on local as admin and see if re-joining them to the domain works

 

 

What I did fing on ipconfig /all was that these two computers had been given the same name (by a teacher I might add!) when he set them up. I have now changed the name but still have the same unable to lopg onto the domain problem.

[FN-GM]

Can you see the computer account in Active Directory?

 

Z

[SYNACK]

Given that they both had the same computer name when joined to AD the computer account may have been damaged in AD or simply redirected to the last computer joined. I would suggest rejoining the problematic machine to the domain under a different name after of course changing it back to workgroup mode first so that it does not try to update the existing account to the new name.

[speckytecky]

Given that they both had the same computer name when joined to AD the computer account may have been damaged in AD or simply redirected to the last computer joined. I would suggest rejoining the problematic machine to the domain under a different name after of course changing it back to workgroup mode first so that it does not try to update the existing account to the new name.

 

 

Ran out of time today and toward the end of the working day my mind was getting fuzzy but I'll do this. Now ayay from the 2 offending computers suspect that the domain name they had been given might have not been totally correct.

 

Thanks for all the help folks.

[rusty155]

Ran out of time today and toward the end of the working day my mind was getting fuzzy but I'll do this. Now ayay from the 2 offending computers suspect that the domain name they had been given might have not been totally correct.

 

Thanks for all the help folks.

 

Hmmm...

 

You must have had the domain name set correctly or it wouldn't have joined?!!

[L.Kay]

If you have a clash of names, then not only will you need to rename and re-join the domain for the incorrectly named one, but you may also have to re-join the domain for the original correct machine to work too.

[Inbir316]

try removing the accounts in active directory and rejoin on domain?