Computer cannot obtain the domain controller name

Question

I want to take two sounds that contain a dominant frequency and say 'this one is higher than this one'. I could do FFT, find the frequency with the greatest amplitude of each and compare them. I'm wondering if, as I have a specific task, there may be a simpler algorithm.

The sounds are quite dirty with many frequencies, but contain a clear dominant pitch. They aren't perfectly produced sine waves.

Solution 1

Obviously, be sure that the "problem" computers have the same DNS server specified as the "working" computers. (Ideally they're having that set by DHCP.)

It seems unlikely that your Ethernet switch's spanning tree implementation would be blocking access, but to be sure that it's not switch port-related you might try one of the "problem" computers on one of the ports used by a known-working computer.

Some NICs have a problem with "media sense" and can cause problems with Group Policy processing. If you see event log entries from the NIC driver about the network connection coming up after the entries complaining about being unable to find the domain controller name then you've probably got a media sense problem. Have a look here for more background:

• http://support.microsoft.com/kb/239924

• http://support.microsoft.com/kb/326152

Solution 2

Make the client PCs use the Domain Controllers as DNS servers. Check that the proper SRV records are in the DC's DNS records. Run DCDIAG /TEST:DNS on the Domain Controllers to check for any errors in the DNS records.

Comments

[Admin]

Are these computers joined to the domain?

[Admin]

Quite right. My tunnel vision strikes again.

[Admin]

I have the same problem. I don't have DHCP. DNS was written manually. And it works properly (nslookup receive an IP by domen name). Moreover another PC's in this subnet work good - there isn't any errors. BUT 1! On problem PC I have a Comodo firewall. I put it inactive mode. May be when it starts it blocks ICMP (Helvick answer) and only after login put firewall in inactive mode. BUT 2! I had made several experiments with local group policy on problem PC before.

[Admin]

user35115, did disabling the firewall resolve the issue?

[Kcmamu]

<pedantic> That of course is assuming the DCs are Domain Name Servers, as they don't have to be. </pedantic>

[Wesley]

Indeed! One more lesson about questioning my assumptions.

[CandyCo]

Interestingly enough there was an updated driver for a gigabit nic card that specifically stated it addressed an issue with AD. However, even after updating and rebooting several times, the issue persists. Same with the registry edit. Great info either way, as I'm sure it was needed. Still searching for teh solution though. And yes, all DNS servers are consistent across 'working' and 'problem' computers.

[CandyCo]

These problematic machines connect through the same switch that healthy machines are connected to. Thank you for the suggestion, however.

[CandyCo]

Selecting this as my solution, because for all intents and purposes, it was at least part of the resolution.

[Joe]

Thanks. I thought so. It's just sometimes people say "Oh yes of course use algorithm X hadn't you heard of it?".

[Alex Wilson]

Perhaps they will shortly. But I can't think of anything obviously sensible that's better... :-)