Windows 7 Windows 7 & 2003 Domain

[chesh]

Ok, here's a weird one. I just got Win 7 all up and running and I've joined it to my domain. The domain in question is named Empire.local and we have two DC's. One's name is EOM with the IP of 192.168.10.150 and the other is EXCHANGE with the IP of 192.168.10.149. Once I'm logged into windows, I noticed that I couldn't access anything via \\EOM (our main DC with all the main programs installed on it). After doing some troubleshooting I tried to ping EOM from the command prompt and it resolved as 192.168.10.149, the IP address of the 2nd DC. I checked all the DNS reverse records and everything is set right. I then checked all the DHCP settings and they all have the correct information. Checked ipconfig /displaydns and there it was again, saying that the DNS reverse records pointed back to 192.168.10.149. Any ideas of where further to check out what the issue is here? I've gone to multiple other XP and Vista computers and their rDNS all work fine with EOM. I've tried rebooting both servers to no avail. I'm really at a loss of why this one computer would be pulling back the wrong information. Thanks for any help guys.

 

[ChatGPT]

It seems like you are facing an issue where the Windows 7 computer you've joined to your domain is resolving the incorrect IP address for the EOM domain controller. Here are some steps you can take to troubleshoot and potentially resolve this DNS resolution issue:

Troubleshooting Steps:​

1. Flush DNS Cache:
   • Open a command prompt with administrative privileges.
   • Run the following command to flush the DNS cache:

      ipconfig /flushdns

   []Check Hosts File:
   • Ensure that there are no entries in the Windows hosts file (C:\Windows\System32\drivers\etc\hosts) that might be overriding DNS resolution.
   []Verify DNS Settings:
   • Check the DNS settings on the Windows 7 computer to ensure it is pointing to the correct DNS servers, specifically to the primary and secondary DNS servers in your domain.
   []DNS suffix issues:
   • Check the DNS suffix configuration on the Windows 7 computer and make sure it's correctly configured to match your domain (Empire.local).
   []NSLOOKUP:
   • Use the nslookup command in the command prompt to directly query the DNS server for the IP of EOM. This can help determine if the issue lies within the DNS configuration.

      nslookup EOM

   []Check Group Policies:
   • Review any group policies that might be affecting DNS resolution on the Windows 7 computer. Ensure that there are no policies conflicting with the correct DNS resolution.
   []Network Traffic Monitoring:
   • Use network monitoring tools to inspect the DNS queries and responses between the Windows 7 computer and the DNS server. This can help in identifying where the incorrect IP resolution is occurring.
   []Firewall and Security Software:
   • Temporarily disable any firewall or security software on the Windows 7 computer that might be interfering with DNS resolution.
   []Update NIC Drivers:
   • Ensure that the network interface card (NIC) drivers on the Windows 7 computer are up to date. Outdated drivers can sometimes cause unexpected networking issues. By following these troubleshooting steps, you can pinpoint the source of the incorrect DNS resolution on the Windows 7 computer and hopefully resolve the issue. If the problem persists, further investigation into the network configuration and DNS settings may be required. Let me know if you need assistance with any of these steps or if you have further questions!