Article ID: 165170 - View products that this article applies to.
This article was previously published under Q165170
If you do not know the TCP/IP address of the computer that is running Microsoft Windows NT, Windows 98, Windows Millenium Edition, Windows 2000, Windows XP, or Windows Server 2003, you can determine it quickly by displaying up a Command Prompt and using IPCONFIG at the command prompt.
To start a Command Prompt on a computer that is running Windows 95, click Start, click Run, type WINIPCFG, and then click OK.
To start a Command Prompt on a computer that is running Windows NT, Windows 2000, Windows XP or Windows Server 2003, click Start, click Run, type CMD, and then click OK
To start a Command Prompt on a computer that is running Microsoft Windows 98 or Windows Millenium Edition, click Start, click Run, type COMMAND, and then click OK
When you run IPCONFIG, information that is similar to the following appears for each network adaptor that is installed in the computer:
The computer that is running Windows 95 displays a Window that is named IP Configuration with this information, and also to some information about the network adaptor.
Ethernet adaptor Local Area Connection: Connection-specific DNS Suffix . : yourdomain.com IP Address. . . . . . . . . . . . : 192.168.1.233 Subnet Mask . . . . . . . . . . . : 255.255.255.128 Default Gateway . . . . . . . . . : 192.168.1.1
This information is sometimes required when you set up a Remote OLE Automation Server. When you run the Clireg32.exe file on the client machine, the network address field requires either the machine name or the TCP/IP address of the server.
For more information about using Clireg32.exe, click the following article number to view the article in the Microsoft Knowledge Base:
155939"Visual FoxPro Developer's Guide," version 5.0, pp. 445-446.
(http://support.microsoft.com/kb/155939/ )How to use Clireg32.exe for remote automation
Article ID: 165170 - Last Review: July 12, 2005 - Revision: 4.4