Question Locked

Domain logon problem

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

I have a domain, Windows 2000 server and about 50 clients, a mix of XP Pro and Win 2k.

Just purchased some Acer desktops with Gigabit LAN on board. These machines cause a weird problem not experienced by any others in the domain.

I log on as local administrator and set up the domain access as follows

Primary DNS suffix is set to mydomain.local, so full computername comes out as mypc.mydomain.local

The domain is set as mydomain

I can join the domain, and when I reboot any user can log onto the domain without problem.

However, when they come in the next day, they cannot log in to the domain. Logging back in as local administrator I see the contents of the 'domain' box in MyComputer-Properties-ComputerName-Change has changed from "mydomain" to "mydomain.local" as would be expected but it will not log on. If I change it back to "mydomain" (remove the ".local" from the end) then anyone can log in OK until the PC is powered down for the night, then we're back to being unable to log on again.

Any ideas? This one is causing me a lot of earache since the PC's are for the senior managers' upgrades.

7 replies

by shady108

what individual pc names are you giving each pc? for example in my network they are names pc-asset001 pc-asset002 etc etc

are you making sure each name is unique. also what container are the computers in on Active Directory?

by alec.wood

Names are definately unique, I use similar system for naming

They are all in the container "Computers" in mydomain.local

by ashij

Hi! Alec, the proper naming convention for a host in a domain is usually: host.domain.com (any other suffix). Please try changing it to this and you shouldn't have that problem.

by alec.wood

For example PCMAN-00456.mydomain.local is the name of one of the PC's trying to connect, but PCASW-00545 (mine), a Fujitsu Siemens bought and set up on the same day and set up the same does not have this issue.

I use the suffix .local rather than .com - can't remember why, my "more knowledgable than me" chap helped me set up the domain originally.

I wonder if it is something in the OEM install of XP. Do you think a reinstall might be best course of action?

I have some breathing space now at least, big boss demands some urgent SQL work, so all the managers expecting their upgrades know they have to wait at leasta couple of days.

by shady108

i would try taking one off the domain..

delete the computer account from active directory

rename the pc to test

join it to the domain mydomain.local

and see what happens

i use the same domain structure ie mycompany.local and eveyrthing works fine here

i would also make sure the firewalls are turned off... there isnt any extra manufacturers software loaded on these machines is there?

by alec.wood

There was but I uninstalled it. As it happens I have a list of it and guess what, one of them is "settings protection" - it is uninstalled, but experience suggests that does not mean that whatever locks it put on have been taken off.

Will look more tomorrow,

This discussion is closed to new replies.