Windows box fails to dynamically register its DNS with no errors recorded in Event Viewer

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

nslookup returns Default Server as Unknown

I was asked to troubleshoot a recently built DNS server that was having some difficulties. One of the errors had me scratching my head for a few minutes. When doing an nslookup the following would be displayed C:\nslookup Default Server: UnKnown Address: 192.168.1.4 As it turns out it’s not really an error –what it is describing is

TCP/UDP Ports for Windows Server and Workstation

Hey Firewall Admin–please open up the following ports for me.  🙂 Port Protocol Application protocol System service name n/a GRE GRE (IP protocol 47) Routing and Remote Access n/a ESP IPsec ESP (IP protocol 50) Routing and Remote Access n/a AH IPsec AH (IP protocol 51) Routing and Remote Access 7 TCP Echo Simple TCP/IP