FP2000: TCP/IP Test Fails But Other Internet Programs Run

When you run the Network Test, No is returned on one or more tests, even though other Internet applications run without problems.

This problem occurs because FrontPage uses more of the Winsock features than most Internet applications. Unlike most Internet applications, FrontPage browses and retrieves files using Winsock, and it also requires your computer to act as a Web server.

Not every third-party TCP/IP stack includes all of the industry standard Winsock API calls. Therefore, if the TCP/IP test fails, FrontPage will be unable to work with that particular TCP/IP stack.

When it begins, the TCP/IP Test or Network Test loads the Wsock32.dll and looks for a list of entry points. If the test finds all the required entry points (from the list that follows), the test calls the WSAStartup startup routine (which is one of the entry points found) and it requests version 1.1 or higher of the Winsock API.

Then, the TCP/IP test or Network Test attempts to run the following Winsock API calls: FrontPage will only work with third-party TCP/IP stacks that properly support all of these API calls. For additional information about the Microsoft TCP/IP stack, click the article numbers below to view the articles in the Microsoft Knowledge Base: Winsock is the common name for the Windows Sockets Interface Specification. This specification defines a network programming interface for Microsoft Windows, which is based on the "socket" paradigm popularized in the Berkeley Software Distribution (BSD) from the University of California at Berkeley. It encompasses both Berkeley socket style routines and a set of Windows specific extensions designed to allow a programmer to take advantage of the message-driven nature of Windows.

For additional information, click the article number below to view the article in the Microsoft Knowledge Base: