Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Someone added a windows 7 workstation to this windows 2003 domain. They can login locally and say they are on the domain, and have mapped drive resources.

Trying to connect with psexec or anything else I have tried will not accept either the username/password combination or any domain administrator/password combination.

The workstation does not show in the AD but is listed in dns in the reverse lookup zone but not forward lookup zone and pinging resolves to the correct ip. DHCP shows a lease for a couple more weeks.

I have no idea what was done (because no one admits anything) it is a small network 25 machines.

Netdom won't work because I can't provide an accepted user/password combination. No one there has a clue enough to even walk them through anything. So I have to try remotely resolving this.

Any idea what to try next? Or what else I might try. I am a volunteer IT guy on this.

share|improve this question
Add the workstation to the AD. – George May 14 '12 at 22:25
It doesn't sound to me like the computer was actually joined to the domain. – joeqwerty May 14 '12 at 22:36
I don't really think this computer was added to the domain, yet it shows with the domain appended in dns. But how to add it remotely now is what I need to do – datatoo May 15 '12 at 13:51

Right click my computer and click properties. At the bottom it should say what domain it is connected to.

If it doesn't show up in AD users and computers then it isn't really on the domain. Remove it and add it again.

Mapped network drives doesn't mean they are on the domain. It may just have domain credentials saved for the drive.

share|improve this answer
I should have made it clearer, I am working remotely. How do you remove it when it accepts no login credentials? – datatoo May 15 '12 at 13:53
Ah. If you are working remotely you'll either need to guide the user through doing it (good luck!) or use something like TeamViewer to access the system remotely. – Grant May 15 '12 at 14:42
yeah I am afraid this is what has to happen. The person who put the machine on the network is their new network admin – datatoo May 15 '12 at 16:38
My usual strategy in this situation is to get them to load TeamViewer on their computer (which can take 20 minutes to walk a clueless user through, but can be done). From there install logmein or enable remote desktop so I can keep remote access. Then start troubleshooting. – Grant May 15 '12 at 17:00
Appreciated the note regarding mapped drives not indicating they are on the domain. – datatoo May 15 '12 at 21:45

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.