Domain Controller Not Found...

[DoesSpeedTurnUon]

Normally, you'd think the server was not configured right. Well thats what i thought, except 7 other machines joined the domain just fine, except this ONE PC. I've made EVERY setting identical to one of the ones that joined and still nothing. I've googled, i've turned off firewalls, i've done everything short of taking the network card out of the Machine. Does anyone know anything else i can try?

Going from workgroup to a domain.

[nitrofreak]

I would try a different NIC if you can. A workgroup is not as picky as a domain to malformed or dropped packets. You might also be sure that it has the right DNS server as the primary and that you can get to the dns server. This will raise all hell. One more thing...when you put the domain name in, try to use the FQDN instead of the WINS name to force it to use dns to resolve it instead of WINS. If it is an older OS, this might make a difference.

[GT Dan]

bad network card... does it pick up an IP address and see other machines?

[DoesSpeedTurnUon]

[QUOTE=nitrofreak]I would try a different NIC if you can. A workgroup is not as picky as a domain to malformed or dropped packets. You might also be sure that it has the right DNS server as the primary and that you can get to the dns server. This will raise all hell. One more thing...when you put the domain name in, try to use the FQDN instead of the WINS name to force it to use dns to resolve it instead of WINS. If it is an older OS, this might make a difference.[/QUOTE]

It's an XP Pro machine going to a Windows 2000 server. I'm thinking it might be the NIC the more i read and find out. We'll be testing that tonight! I'll let ya'll know the outcome!

GTDan... it can get on the internet so it has to have an ip, hell i configured a static ip in it.

Also, i don t have the machine in front of me right now, so alot of this is from memory.

[trey85stang]

if the nic works.. check your dns settings.

[Sgt Beavis]

Check the following

First the obvious settings:
IP
Subnet mask
gateway
DNS

Can you ping the DC by its IP? Can you ping it by its FQDN? If you can ping by IP but not FQDN,then it is a DNS issue of some sort....

Check the following services

Server service - should be running
Workstation service - should be running
DNS client - should be running
Netlogon - set to manual, might be running
Remote Procedure Call (RPC) service - shoud be running
RPC Locator - set to manual, might be running

I'm going from memory, so I might have missed one but you need all those services to connect to a Win2k Domain...

Also, check the NetSetup.log file in C:\windows\debug. That tells you what problems you might be experiencing when trying to reach the DC.

If you can get onto the internet or can ping the DC, then I'd be looking at the configuration of the Windows OS or services before considering the NIC as the source.. The only way to tell after that is to get a NETMON trace and follow it to the point of failure.

[DoesSpeedTurnUon]

well, uninstalled the nic, deleted all the properties, reinstalled a new nic in a different slot, started it, joing a domain perfectly. now i hope it joins the one i need it to, tommorow.

[DoesSpeedTurnUon]

Note: This information is intended for a network administrator. If you are not your network's administrator, notify the administrator that you received this information, which has been recorded in the file C:\WINDOWS\debug\dcdiag.txt.

The following error occurred when DNS was queried for the service location (SRV) resource record used to locate a domain controller for domain ptc.local:

The error was: "DNS name does not exist."
(error code 0x0000232B RCODE_NAME_ERROR)

The query was for the SRV record for _ldap._tcp.dc._msdcs.ptc.local

Common causes of this error include the following:

- The DNS SRV record is not registered in DNS.

- One or more of the following zones do not include delegation to its child zone:

ptc.local
local
. (the root zone)

For information about correcting this problem, click Help.

[DoesSpeedTurnUon]

[QUOTE=Sgt Beavis]Check the following

First the obvious settings:
IP
Subnet mask
gateway
DNS

Can you ping the DC by its IP? Can you ping it by its FQDN? If you can ping by IP but not FQDN,then it is a DNS issue of some sort....

Check the following services

Server service - should be running
Workstation service - should be running
DNS client - should be running
Netlogon - set to manual, might be running
Remote Procedure Call (RPC) service - shoud be running
RPC Locator - set to manual, might be running

I'm going from memory, so I might have missed one but you need all those services to connect to a Win2k Domain...

Also, check the NetSetup.log file in C:\windows\debug. That tells you what problems you might be experiencing when trying to reach the DC.

If you can get onto the internet or can ping the DC, then I'd be looking at the configuration of the Windows OS or services before considering the NIC as the source.. The only way to tell after that is to get a NETMON trace and follow it to the point of failure.[/QUOTE]

This is from the NetSetup.Log
06/30 10:13:55 NetpValidateName: checking to see if 'ptc.local' is valid as type 3 name
06/30 10:13:57 NetpCheckDomainNameIsValid for ptc.local returned 0x54b
06/30 10:13:57 NetpCheckDomainNameIsValid [ Exists ] for 'ptc.local' returned 0x54b

[DoesSpeedTurnUon]

I dont understand why it would join one domain, and not another?!

#%)*&%*)&!)*&)*O!&)*&%^)!#*&)*(&)!$#^

[mind]

i get the ones that won't join sometimes. i don't know why, never looked into it. i just change the name on the machine, delete the account in AD, recreate the account in AD, then change the name back, then join the domain.

[DoesSpeedTurnUon]

[QUOTE=mind]i get the ones that won't join sometimes. i don't know why, never looked into it. i just change the name on the machine, delete the account in AD, recreate the account in AD, then change the name back, then join the domain.[/QUOTE]

Right, right this moment, i dont care "why", i just need to know "how"

I renamed the workstation computer
deleted the user account in AD
recreated the user account in AD

and tried to join, and no luck... am i missing something!?

[Sgt Beavis]

0x54b means "Error no such domain"

Your system is going out to DNS and looking for the SRV (service) record for LDAP (directory services)

There is NO SRV record on the DNS server you are connecting to for the domain you are trying to connect to. Otherwise that DCDIAG you posted would have listed the FQDN of the domain controller.

You've got a DNS issue.

Are you on DHCP? In a command prompt, run IPCONFIG /ALL. Make sure the IP address for DNS is exactly the same as the other workstations that CAN connect to the Domain Controller.

BTW did you check to see if you can ping the DC by its FQDN? (Fully Qualified Domain Name)

FQDN = computername.domainname.com
example = Yofuckedupdomaincontroller.fuckedupdomain.com ;)

Get back to me soon because I'm going out of town tomorrow afternoon and won't be back until July 6th.

BTW, I'll come fix it for you but I charge 50 bucks an hour at a two hour minimum ;)
And thats the discounted price :D

[DoesSpeedTurnUon]

[QUOTE=Sgt Beavis]0x54b means "Error no such domain"

Your system is going out to DNS and looking for the SRV (service) record for LDAP (directory services)

There is NO SRV record on the DNS server you are connecting to for the domain you are trying to connect to. Otherwise that DCDIAG you posted would have listed the FQDN of the domain controller.

You've got a DNS issue.

Are you on DHCP? In a command prompt, run IPCONFIG /ALL. Make sure the IP address for DNS is exactly the same as the other workstations that CAN connect to the Domain Controller.

BTW did you check to see if you can ping the DC by its FQDN? (Fully Qualified Domain Name)

FQDN = computername.domainname.com
example = Yofuckedupdomaincontroller.fuckedupdomain.com ;)

Get back to me soon because I'm going out of town tomorrow afternoon and won't be back until July 6th.

BTW, I'll come fix it for you but I charge 50 bucks an hour at a two hour minimum ;)
And thats the discounted price :D[/QUOTE]


haha actually, today was my last day with the company. I mapped the drives they use for quickbooks and thier user folders on the server so he could atleast work.

I couldn't ping the FQDN.

However, all the DNS settings, IP settings, are all the same on a known good computer and the bad one.

The router is passing out DHCP.

One day, very soon... i'll be as smart as you guys :D (still in school, but know enough to get me in trouble :D)

[Sgt Beavis]

hahaha... Now its the next guys problem :)

Next time you run into a problem, try the forums on http://www.tek-tips.com There are some good people over there that are always willing to help. I'm usually on the VMware forums but I also frequent the Windows OS forums.

Good luck with the next job.

[DoesSpeedTurnUon]

[QUOTE=Sgt Beavis]hahaha... Now its the next guys problem :)

Next time you run into a problem, try the forums on http://www.tek-tips.com There are some good people over there that are always willing to help. I'm usually on the VMware forums but I also frequent the Windows OS forums.

Good luck with the next job.[/QUOTE]

Thank you much! I'm going to finish my MCP, CCNA, CCNP, CWNA and security +

but i think i'm going to contact out for some cash while i do the training/school thing.