Microsoft KB Archive/829528

= Network troubleshooting tools for Microsoft Business Solutions CRM installations =

Article ID: 829528

Article Last Modified on 9/14/2007

-

APPLIES TO


 * Microsoft CRM 1.2
 * Microsoft Business Solutions CRM 1.0

-



SUMMARY
This article describes network troubleshooting tools that you can use to troubleshoot potential issues with Microsoft Business Solutions CRM.



MORE INFORMATION
Microsoft CRM is very dependent on your network and your Active Directory environment. Microsoft Windows 2000 and Windows XP contain many basic network troubleshooting tools to help you troubleshoot basic network issues that may be causing problems in your Microsoft CRM installation.

The following list describes some of these tools:  PathPing

You can use the PathPing tool to verify that you can contact a host. The results contain some basic information about packet loss. To use this tool from a command prompt, follow these steps:  Click Start, and then click Run. In the Open dialog box, type cmd, and then click OK. At the command prompt, type pathping, and then press ENTER. 

For more information about how to use PathPing, see the &quot;Test Network Connection with Ping and PathPing&quot; section in the Microsoft Windows 2000 Server Resource Kit, or see &quot;Testing the Network Connection with Ping and PathPing&quot; in Chapter 19 of the Microsoft Windows XP Professional Resource Kit documentation. IPConfig

The IPConfig tool returns the IP configurations of a workstation. To use this tool from a command prompt, follow these steps:  Click Start, and then click Run.</li> In the Open dialog box, type cmd, and then click OK.</li> At the command prompt, type ipconfig /all, and then press ENTER.</li></ol>

Use the results to do the following: <ul> Verify that the workstation has a correct IP address and a correct subnet mask. An incorrect IP address or subnet mask can cause connectivity problems.</li> If Dynamic Host Configuration Protocol (DHCP) is enabled, verify that the workstation has an assigned IP address. If you cannot obtain an IP address, you might have a problem with the DHCP server.

For additional information about how to set up, how to configure, and how to troubleshoot DHCP, click the following article number to view the article in the Microsoft Knowledge Base:

300429 Install and Configure a DHCP Server in an Active Directory Domain in Windows 2000

</li> Verify the default gateway. An incorrect default gateway can cause connectivity problems with the remote networks or with the Internet.</li> Verify the Domain Name System (DNS). Windows 2000 and Windows XP use DNS for name resolution. Generally, a workstation points to a Windows 2000 server for DNS.</li></ul> </li> NSLookup

The NSLookup tool (also known as Name Server Lookup) When you are troubleshooting Internet e-mail delivery problems, NSLookup reviews the DNS entries that are located on a DNS server and verifies mail exchange records (MX). To use this tool from a command prompt, follow these steps:  Click Start, and then click Run.</li> In the Open dialog box, type cmd, and then click OK.</li> At the command prompt, type nslookup, and then press ENTER.</li></ol>

Your NSLookup results should include two sets of data. The first set of data includes the server name of the domain controller and the IP address that is associated with the domain controller. The second set of data includes the name of the server that you performed NSLookup to and the IP address that is associated with that computer.</li> Route Print

The Route Print tool returns the learned routes and the static routes that are on a local workstation. Use this tool to determine the route that packets are traveling. To use this tool from a command prompt, follow these steps:  Click Start, and then click Run.</li> In the Open dialog box, type cmd, and then click OK.</li> At the command prompt, type route print, and then press ENTER.</li></ol>

A response that is similar to the following appears:

<pre class="fixed_text">Active Routes:

Network Address  Netmask           Gateway Address  Interface   Metric

0.0.0.0          0.0.0.0           10.1.1.254       10.1.1.3       1   10.1.0.0          255.255.0.0       10.1.1.3         10.1.1.3       1   10.1.1.3          255.255.255.255   127.0.0.1        127.0.0.1      1   10.255.255.255    255.255.255.255   10.1.1.3         10.1.1.3       1   127.0.0.1         255.0.0.0         127.0.0.1        127.0.0.1      1   224.0.0.0         224.0.0.0         10.1.1.3         10.1.1.3       1   255.255.255.255   255.255.255.255   10.1.1.3         10.1.1.3       1

For additional information about the Route Print Command, click the following article number to view the article in the Microsoft Knowledge Base:

169790 How to Troubleshoot Basic TCP/IP Problems

</li> <li>NetDiag

The NetDiag tool returns useful information about the network configuration of a workstation including the following: <ul> <li>IP configurations</li> <li>Server name</li> <li>Default gateway</li> <li>Winsock test</li> <li>DNS test</li> <li>Loopback test</li></ul>

For the best results, make sure that you bind TCP/IP to one of the network adapters that are on the server. The data that this tool returns appears in the Netdiag.log file. This file is located in the same folder as the Netdiag.exe file.

To download NetDiag, visit the following Microsoft Web site:

http://support.microsoft.com/kb/927229

</li></ul>

Additional query words: TK 31703 installation server administration

Keywords: kbmbsinstallation kbmbsmigrate kbinfo KB829528

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.