windowswideopen.com

How to detect Misconfigured TCPIP Configuration

Running IPConfig.exe
• From a Command Prompt, run the command “IPCONFIG /ALL”
• If the Output from the customer returns an error, then there is a more serious Networking issue.

Checking for Multihomed Settings
If the Output from the IPCONFIG /ALL shows:
1. Multiple network Adapters installed
2. Multiple IP Addresses for any Adapter

Then the system is considered Multihomed. As such, the system may be performing as designed, yet causing problems with applications or components that are not Multihome-aware.
Refer to the following KB Articles to determine whether any of the issues may relate to the problems being experienced.

• You cannot transfer files from a multihomed computer to another Windows Messenger user by using Windows Messenger 5.0 - http://support.microsoft.com/default.aspx?scid=KB;EN-US;835972
• How to troubleshoot event ID 8032 and 8021 messages on master browsers - http://support.microsoft.com/default.aspx?scid=KB;EN-US;833441
• Clients cannot log on to domain controllers that are Windows Server 2003-based DNS servers, and network interfaces that are not registered in DNS can still perform dynamic updates - http://support.microsoft.com/default.aspx?scid=KB;EN-US;832478
• Group Policy Settings Do Not Apply to a Client Computer That Is Multihomed - http://support.microsoft.com/default.aspx?scid=KB;EN-US;830513
• Name resolution and connectivity issues occur on Windows 2000 domain controllers that have the Routing and Remote Access service and DNS installed - http://support.microsoft.com/default.aspx?scid=KB;EN-US;830063
• An IP multicast may not be sent correctly from Windows 2000, Windows XP, or Windows Server 2003 - http://support.microsoft.com/default.aspx?scid=KB;EN-US;827536

Checking for Redundant Gateways

If the Output from the IPCONFIG /ALL shows:
1. Multiple Default Gateways on any one Adapter installed
2. A separate Default Gateway IP Address on each of multiple Adapters
Then the system is using Redundant Default Gateways. As such, the system may be performing as designed, yet there may be some performance or connectivity issues with applications or components that are not designed to communicate properly using the Default Gateway mechanism in place.
The Default Gateway strategy for redundant Default Gateways is known as Dead-Gateway Detection. Details on this implementation are available at the following locations:
• Default Gateway Behavior for Windows TCP/IP -http://www.microsoft.com/technet/community/columns/cableguy/cg0903.mspx
• Microsoft Windows Server 2003 TCP/IP Implementation Details - http://www.microsoft.com/downloads/details.aspx?FamilyID=06c60bfe-4d37-4f50-8587-8b68d32fa6ee&DisplayLang=en
Refer to the following KB Articles to determine whether any of the issues may relate to the problems being experienced:
• Multiple Default Gateways Can Cause Connectivity Problems - http://support.microsoft.com/default.aspx?scid=KB;EN-US;159168
• Dead Gateway Detection Does Not Fail Over UDP Traffic to Alternate Gateway - http://support.microsoft.com/default.aspx?scid=KB;EN-US;319778
• Default Gateway Configuration for Multihomed Computers - http://support.microsoft.com/default.aspx?scid=KB;EN-US;157025
• How to use an IP settings test to determine whether a customer has Internet connectivity

NetworkNetwork

Filed under: Network