INFO: A Quick Way to Determine the TCP/IP Address

Last reviewed: March 14, 1997
Article ID: Q165170

The information in this article applies to:

Microsoft Visual FoxPro for Windows, versions 3.0, 3.0b, 5.0, 5.0a

SUMMARY

If you do not know the TCP/IP address of your Windows NT machine, you can determine it quickly by bringing up an MS-DOS Window and typing IPCONFIG at the prompt. On a Windows 95 machine, type WINIPCFG at the Start/Run prompt.

Information similar to the following appears:

   Windows NT IP Configuration

   Ethernet adapter IEEPRO1:

      IP Address. . . . . . . . . : 157.54.53.197

      Subnet Mask . . . . . . . . : 255.255.240.0

      Default Gateway . . . . . . : 157.54.48.1

The Windows 95 machine displays a Window titled IP Configuration with the above information, in addition to some information on your network adapter.

MORE INFORMATION

This information is sometimes necessary when setting up a Remote OLE Automation Server. When running Clireg32.exe on the client machine, the "network address" field requires either the machine name or the TCP/IP address of the server.

REFERENCES

For more information about using Clireg32.exe, please see the following article(s) in the Microsoft Knowledge Base:

   ARTICLE-ID: Q155939
   TITLE     : How To Use Clireg32.exe for Remote Automation

"Visual FoxPro Developer's Guide," version 5.0, pp. 445-446.

Additional query words: tcp
Keywords : FxenvGeneral vfoxwin kbinfo kbinterop
Version : 3.0 3.0b 5.0 5.0a
Platform : WINDOWS

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: March 14, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.