Sometimes it is the simplest things that get you. I was asked to troubleshoot a system that would not register into DNS after a domain migration. The system could ping its new gateway and the new DNS servers–telnet showed access to the new DNS boxes on port 53 and name resolution was functioning correctly other
Ping returns the following Pinging DC1.domain.com [::1] from ::1 with 32 bytes of data: Reply from ::1: time=1ms Reply from ::1: time=2ms Reply from ::1: time=1ms Reply from ::1: time=3ms Disable IPv6 and your problems go away. It’s usually not enough to uncheck it in the NIC properties. For best results use the registry to
Do you want to disable IPv6 on all interfaces but find that doing so on the NIC properties in the GUI does not always work properly? The best way to truly disable it is via registry setting: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters] “DisabledComponents”=dword:000000ff This will disable it on all interfaces and force IPv4 preference…
While it is rare in Windows 2003 and above to see any TCP stack corruption it does occure every once in a while? Did you notcie that you can not uninstall the TCP services via the GUI as it is now considered a “core component” of the OS. You can still unisntall this via the