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

Set network configurations from the command line in Windows

One of the quickest and easiest ways to set network configuration on a network adapter is via command line. Lets use the following criteria: We will be setting up Local Are Connection IP: 192.168.200.2 MASK: 255.255.255.0 GW: 192.168.200.1 GW Metric: 1 Here is the syntax for IPv4: netsh interface ipv4 show config netsh interface ip set address name=”Local

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

Increase maximum number of TCP port connections that are available on a Windows server

While this is extremely rare you may encounter a web application that loves to open TCP connections to the point where the default pool of available TCP connections are exhausted. [HKEY_LOCAL_MACHINE \System \CurrentControlSet \Services \Tcpip \Parameters] MaxUserPort = 5000  (Max = 65534) Just increase the value from the default 5000. Note: You should investigate if

Limit dynamic RPC port range on Windows Server

RPC by default can grab any dynamic port above 1024.  Security sometimes may ask you to limit that to a much narrower range.  A the minimum you should have about 100-200 ports available for RPC communication. Here is the registry setting: HKEY_LOCAL_MACHINE\Software\Microsoft\Rpc Ports: REG_MULTI_SZ: 5000-5100 PortsInternetAvailable: REG_SZ: Y UseInternetPorts: REG_SZ: Y   Full MS KB

Remove ghosted network adapter from windows

The IP address you have entered for this network adapter is already assigned to another adapter… From time to time you may encounter this error on a newly P2V system. In the past it was a registry fix but now Microsoft has a prefered GUI solution: Click Start, click Run, type cmd.exe Type set devmgr_show_nonpresent_devices=1

Find out what ports your Windows box is listening on

One of the easiest ways to see what ports a windows system is listening on is to use netstat. To get a comprehensive list open a command prompt netstat -an Active Connections Proto Local Address Foreign Address State TCP 0.0.0.0:135 0.0.0.0:0 LISTENING TCP 0.0.0.0:445 0.0.0.0:0 LISTENING TCP 0.0.0.0:1494 0.0.0.0:0 LISTENING TCP 0.0.0.0:2598 0.0.0.0:0 LISTENING TCP

IPv6 will not disable properly

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…