Microsoft KB Archive/269851

= How to troubleshoot whether a connectivity issue is related to FrontPage 2000 or to a network connection =

Article ID: 269851

Article Last Modified on 9/28/2004

-

APPLIES TO


 * Microsoft FrontPage 2000 Service Pack 1

-



This article was previously published under Q269851



IN THIS TASK

 * SUMMARY
 * Test 1 - Ping the Loopback Address
 * Test 2 - Ping the Server
 * Test 3 - Browse to the Server
 * Test 4 - Open the Web in FrontPage



SUMMARY
This article can help you troubleshoot whether a connectivity problem is related to FrontPage or to your network connection. If you are having a problem connecting to a Web site, follow these steps to determine whether the problem is related to FrontPage or your network connection. To verify your network connection, you should be able to pass all of the following tests.

back to the top

Test 1 - Ping the Loopback Address
 Click Start, and then click Run. In the Open box, type command and then press ENTER. If you are using Microsoft Windows NT or Microsoft Windows 2000, type cmd instead of &quot;command&quot;, and then press ENTER. From the command prompt, type ping 127.0.0.1   If you have a successful connection, you should see a reply similar to the following:

Pinging 127.0.0.1 with 32 bytes of data:

Reply from 127.0.0.1: bytes=32 time<10ms TTL=128 Reply from 127.0.0.1: bytes=32 time<10ms TTL=128 Reply from 127.0.0.1: bytes=32 time<10ms TTL=128 Reply from 127.0.0.1: bytes=32 time<10ms TTL=128

Ping statistics for 127.0.0.1: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average =  0ms

If your connection is successful, proceed to Test 2. If your connection fails, there is a problem with the TCP/IP stack. Contact Microsoft Technical Support for your version of Microsoft Windows. 

back to the top

Test 2 - Ping the Server
 Click Start, and then click Run. In the Open box, type command and then press ENTER. If you are using Windows NT or Windows 2000, type cmd instead of &quot;command&quot;, and then press ENTER.  From the command prompt, type ping where   is the name of the server that you are attempting to connect to. For example: <pre class="fixed_text">ping microsoft.com </li>  If you have a successful connection, you should see a reply similar to the following:

<pre class="fixed_text">Pinging microsoft.com [207.46.197.101] with 32 bytes of data:

Reply from 207.46.197.101: bytes=32 time<10ms TTL=128 Reply from 207.46.197.101: bytes=32 time<10ms TTL=128 Reply from 207.46.197.101: bytes=32 time<10ms TTL=128 Reply from 207.46.197.101: bytes=32 time<10ms TTL=128

Ping statistics for 207.46.197.101: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average =  0ms

If your connection is successful, proceed to Test 3.

If you receive the following message, there is a domain name resolution issue. You should contact your Internet Service Provider (ISP), Web Presence Provider (WPP), or network administrator:

<pre class="fixed_text">Unknown host microsoft.com.

If the connection fails, you should see something similar to the following:

<pre class="fixed_text">Pinging microsoft.com [207.46.197.101] with 32 bytes of data:

Request timed out. Request timed out. Request timed out. Request timed out.

Ping statistics for 207.46.197.101: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average =  0ms </li>  Repeat step 2, using the IP address instead of the server name. The IP address is the series of numbers in brackets after the host name.

For example, 207.46.197.101 is the IP address in the following line: <pre class="fixed_text">Pinging microsoft.com [207.46.197.101] with 32 bytes of data: If the connection fails using the IP address, there is a problem establishing a connection with the server. You should contact your network administrator or Internet Service Provider (ISP). If the connection fails using the host name but works with the IP address, there is a name resolution issue that should be addressed by your network administrator or Internet Service Provider (ISP).

NOTE: If you are in a corporate environment or behind a firewall, you may be unable to ping your server yet still be able to connect to it with FrontPage. </li></ol>

back to the top

Test 3 - Browse to the Server

 * 1) Open your Web browser (for example, Microsoft Internet Explorer or Netscape).
 * 2) In the address box of your Web browser, type the URL of your Web site, and then press ENTER.
 * 3) If you can view the page, continue to Test 4; otherwise, continue with step 4.
 * 4) If you cannot browse the Web site by using the server name, try to browse to the IP address that you obtained in Test 2.
 * 5) If step 4 fails as well, contact your network administrator, Internet Service Provider (ISP), or support for the Web browser that you are using, because you are having a problem navigating to the site.

back to the top

Test 4 - Open the Web in FrontPage

 * 1) On the File menu, click Open Web.
 * 2) In the Folder Name box, type http:// (where   is the host name of your server), and then click Open.
 * 3) If the site opens, you have no network problems. If you are prompted for the password but cannot open the site, either you are using the wrong user name and password, or there is an authentication issue with the way that FrontPage is configured and working.
 * 4) If you receive an error message when you open the Web site via the host name, start over by using the IP address from Test 2.
 * 5) If step 4 fails, verify that any proxy settings you have in your Web browser match the settings you have in FrontPage. Start over at step 1. In FrontPage 2000, your settings should match already, because FrontPage shares the Internet Explorer connection settings.

NOTE: You may want to contact your network administrator or Internet Service Provider to verify any proxy settings.
 * 1) If this still fails, contact your network administrator or Internet Service Provider, because FrontPage is having a problem connecting to the site over your specific network/Internet connection.

back to the top

Additional query words: front page tcp/ip tcp ip tshoot troubleshooting howto troubleshooter

Keywords: kbhowtomaster kbwebserver kbnetwork kbcommandline kbopenfile KB269851

-

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

© Microsoft Corporation. All rights reserved.