WinIPCfg

Windows NT 4.0 had WIPCfg32.exe, and Windows 95/98/ME had WinIPCfg.exe. For some reason, this utility was removed from Windows 2000/XP. This program is a clone of WinIPCfg.exe, written for Windows XP. For those of you who are unfamiliar with WinIPCfg, it looks like this:



About the Author

Erik Gawtry

I have worked as a Software Engineer since 1985. I currently work with Windows, Unix/Linux, DSP, and Microcontrollers.

Downloads

Comments

  • gateway problem

    Posted by mlt2005 on 12/21/2005 11:59am

    Hello, On WinMe the gateway is not displayed, but on Win XP it is. Do you know why? Thanks.

    • update

      Posted by mlt2005 on 12/21/2005 12:10pm

      Actually the gateway is not displayed for a wireless adapter, but using the winipcfg original application it is displayed.

      Reply
    Reply
  • Exception on WinXP (SP1a)

    Posted by Manni HV on 11/03/2005 10:32am

    The utility runs great on W2k, but generates an exception on XP at startup.

    • Re: Update

      Posted by egawtry on 03/22/2006 07:17pm

      I just updated it. As soon as it is reviewed, it will be posted.

      Reply
    • Exception on XP SP1

      Posted by GLykos on 03/22/2006 12:59pm

      Greetings! You mentioned that you were going to revise the code and repost it - did that happen? Thanks. P.S. Error signature on XP SP1, FYI: AppName: winipcfg.exe AppVer: 1.1.0.0 ModName: winipcfg.exe ModVer: 1.1.0.0 Offset: 000030f3

      Reply
    • Re: Exception on W2K

      Posted by egawtry on 11/09/2005 12:19pm

      Great! That explains it. I will update the code and get it reposted. Thanks.

      Reply
    • Exception on Win2000

      Posted by mpauley1955 on 11/09/2005 09:24am

      I also got an exception on startup, but running Win 2000. 
      The problem seems to be when you have multiple adapters. 
      In the CWinIPCfgDlg::GetNICs routine you use GetAdaptersInfo() to load a buffer with the adapter info, then load the combobox item data with it. 
      You step through the returned data as if it were an array:
      
      	// Add each entry to the combobox
      	for(int i = 0; i < nCount; ++i)
      	{
      		CString sName = pIPAI[i].Description;
      		m_cbNetCard.AddString(sName);
      		m_cbNetCard.SetItemData(i, (DWORD_PTR)&pIPAI[i]);
      	}
      
      but it is actually a linked list. I changed it to this:
      
      // pIPAI is a pointer to a linked list of IP_ADAPTER_INFO structures.
      // The last valid one has it's "Next" member set to NULL.
      // Just walk the chain...
      	int i;
      	while ( pIPAI != NULL )
      	{
      		CString sName = pIPAI->Description;
      		i = m_cbNetCard.AddString(sName);
      		m_cbNetCard.SetItemData(i, (DWORD_PTR)pIPAI);
      
      		pIPAI = pIPAI->Next;
      	}
      
      and it works fine now.

      Reply
    • Re: Exception

      Posted by egawtry on 11/03/2005 01:52pm

      Can you give me more details? I have dozens of users on the networks that I support using this right now. If there is an issue, I would like to figure it out.

      Reply
    Reply
  • ???!!!

    Posted by voyager2 on 11/02/2005 03:51pm

    use ipconfig /all ipconfig /renew ipconfig /release or better ipconfig /?

    • Re: ???!!!

      Posted by egawtry on 11/03/2005 01:50pm

      This is for those of us that don't use command line (most of the users I support).

      Reply
    Reply
Leave a Comment
  • Your email address will not be published. All fields are required.

Top White Papers and Webcasts

  • With JRebel, developers get to see their code changes immediately, fine-tune their code with incremental changes, debug, explore and deploy their code with ease (both locally and remotely), and ultimately spend more time coding instead of waiting for the dreaded application redeploy to finish. Every time a developer tests a code change it takes minutes to build and deploy the application. JRebel keeps the app server running at all times, so testing is instantaneous and interactive.

  • Live Event Date: May 6, 2014 @ 1:00 p.m. ET / 10:00 a.m. PT While you likely have very good reasons for remaining on WinXP after end of support -- an estimated 20-30% of worldwide devices still are -- the bottom line is your security risk is now significant. In the absence of security patches, attackers will certainly turn their attention to this new opportunity. Join Lumension Vice President Paul Zimski in this one-hour webcast to discuss risk and, more importantly, 5 pragmatic risk mitigation techniques …

Most Popular Programming Stories

More for Developers

Latest Developer Headlines

RSS Feeds