Client cannot be managed on DC
hi,
I get following error on my SBS2003 when i try to manage a pc on the domain "Computer \\clientPC cannot be managed. the network path was not found. choose 'connect to another computer' from the action menu to manage a different computer."
I can ping and RDP is working fine..
It's only on that one pc, the rest of them works fine..
does anyone know how I can resolve this?
edit:
I noticed that there was no A record in the dns, refering to the pc.
after inserting this record in the dns i get following error:
"Computer \\clientPC cannot be managed. you were not connected because a duplicate name exists on the network. choose 'connect to another computer' from the action menu to manage a different computer."
i checked the pc names they look all fine..
any idea?
tia
Robby
I get following error on my SBS2003 when i try to manage a pc on the domain "Computer \\clientPC cannot be managed. the network path was not found. choose 'connect to another computer' from the action menu to manage a different computer."
I can ping and RDP is working fine..
It's only on that one pc, the rest of them works fine..
does anyone know how I can resolve this?
edit:
I noticed that there was no A record in the dns, refering to the pc.
after inserting this record in the dns i get following error:
"Computer \\clientPC cannot be managed. you were not connected because a duplicate name exists on the network. choose 'connect to another computer' from the action menu to manage a different computer."
i checked the pc names they look all fine..
any idea?
tia
Robby
a_ro_no
Firewall on the PC?
I've seen this happen when a computer is formatted and reloaded then added back to the domain without resetting the computer account in active directory. The computer has the same name and appears to connect to the domain, however the problem is that after the reload the computer generates a new SID (Security IDentifier). Because the Old SID was never cleared in active directory, the new and old SID's do not match, therefore Active directory assumes that 2 computers with the same name exists, meanwhile, you only see one.
The fix for this is to remove the computer from the domain, then delete the computer object from active directory, force replication (or wait 15 minutes) and then add the computer back to the domain. I usually rename the comupter before adding it back to the domain, just to be sure. Sometimes that is not an option, especially if other computers have mapped shares to that computers name.
The fix for this is to remove the computer from the domain, then delete the computer object from active directory, force replication (or wait 15 minutes) and then add the computer back to the domain. I usually rename the comupter before adding it back to the domain, just to be sure. Sometimes that is not an option, especially if other computers have mapped shares to that computers name.
ASKER
It's not the firewall
and we already try to move the pc out of the domain, changing his name, rejoin the domain, but the problem is not resolved.
any suggestions?
and we already try to move the pc out of the domain, changing his name, rejoin the domain, but the problem is not resolved.
any suggestions?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
formatted the workstation and rejoin the domain
ASKER
tried this but no positive result, thx anyways