PeeEs
asked on
(Re-)joining a Domain fails with "... LinkId=5171" error.
Trying to solve a connection problem in my network (clients couldn't connect at all to a shared printer and connecting with the same clients other shares took several retrials), I decided to leave and rejoin the domain with the particular client (after other solutions didn't work out).
Rejoining however resulted in an error:
"The following error occurred validating the name "CONCORD". This condition may be caused by a DNS lookup problem. For information about
troubleshooting common DNS lookup problems, please see the following Microsoft Web site:
http://go.microsoft/com/fwlink/?LinkId=5171"
Following this link didn't help me any further. Neither did the numerous solutions that were posted on the web regarding this issue.
My network: 1 PDC (W2K), several desktop clients (W2K, WinME), notebook (WinXP), cable router, switches.
It seems that the PDC is OK. Rejoining did work out with the notebook (same TCP/IP configuration). W2K client that caused the problem doesn't seem to recognize the PDC as such. Ping however is OK. Registering clients IP adres in local DNS succeeded.
PDC is local DNS server (pointing to itself) as well as DHCP server (static local IP-adres: 192.168.0.3). WINS is not used.
Tried ipconfig /flushdns and ipconfig /registerdns on server as well as on client.
DC Diagnosis with dcdiag /s:192.168.0.3 resulted in:
"LDAP connection failed with error 58, ...
***Error: The machine, 192.168.0.3 could not be contacted, because of a bad net response. Check to make sure that this machine is a Domain Controler."
What I tried already:
Removing network componants from client: TCP/IP adapter, File sharing, Microsoft Network Client.
Deleting every link to 192.168.0.3 and to the domain name in the Registry of the client,
Reïnstalling network componants,
New attempt to rejoin,
Executing the same operation with another Userid (same role: administrator),
Changing from a static to a dynamic local IP-adres on the client.
Anothe curious thing is that although ipconfig lists the proper local gateway adres (as given by the DHCP Server), I can't connect to the internet anymore from the client. Pinging to an outside IP-adres succeeds, pinging to the name not (unknown host), neither does browsing to an outside IP-adres.
Rejoining however resulted in an error:
"The following error occurred validating the name "CONCORD". This condition may be caused by a DNS lookup problem. For information about
troubleshooting common DNS lookup problems, please see the following Microsoft Web site:
http://go.microsoft/com/fwlink/?LinkId=5171"
Following this link didn't help me any further. Neither did the numerous solutions that were posted on the web regarding this issue.
My network: 1 PDC (W2K), several desktop clients (W2K, WinME), notebook (WinXP), cable router, switches.
It seems that the PDC is OK. Rejoining did work out with the notebook (same TCP/IP configuration). W2K client that caused the problem doesn't seem to recognize the PDC as such. Ping however is OK. Registering clients IP adres in local DNS succeeded.
PDC is local DNS server (pointing to itself) as well as DHCP server (static local IP-adres: 192.168.0.3). WINS is not used.
Tried ipconfig /flushdns and ipconfig /registerdns on server as well as on client.
DC Diagnosis with dcdiag /s:192.168.0.3 resulted in:
"LDAP connection failed with error 58, ...
***Error: The machine, 192.168.0.3 could not be contacted, because of a bad net response. Check to make sure that this machine is a Domain Controler."
What I tried already:
Removing network componants from client: TCP/IP adapter, File sharing, Microsoft Network Client.
Deleting every link to 192.168.0.3 and to the domain name in the Registry of the client,
Reïnstalling network componants,
New attempt to rejoin,
Executing the same operation with another Userid (same role: administrator),
Changing from a static to a dynamic local IP-adres on the client.
Anothe curious thing is that although ipconfig lists the proper local gateway adres (as given by the DHCP Server), I can't connect to the internet anymore from the client. Pinging to an outside IP-adres succeeds, pinging to the name not (unknown host), neither does browsing to an outside IP-adres.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
kind regards, Peter