FIX for IPCONFIG failing with Unknown media status error

[JNavas]

If the following error occurs when attempting to run IPCONFIG when using a wireless network adapter:

Code: Select all

Windows IP Configuration
An internal error occurred: A device attached to the system is not functioning.
Please contact Microsoft Product Support Services for further help.
Additional information: Unknown media status code.

The likely cause of the problem is a wired network adapter that isn't connected, and as a result has been automatically Disabled in Network Connections after about 30 secs or so by its network driver, while still being enabled in Device Manager. IPCONFIG reports an error because the wired hardware is enabled, but it can't get the media status since the Network Connection (driver) has been disabled.

This issue is known to affect at least some Intel wired network adapters with Windows XP drivers dated 2006 and later. For example, disconnected Intel PRO/1000 MT Mobile wired network adapter in a ThinkPad T41, driver e1000325.sys:

Code: Select all

VERSION        DATE     SOURCE                      RESULT
6.4.16.36  (06/13/2003) Original Windows XP driver  Cable Unplugged
7.2.17.101 (10/26/2004) Lenovo Software Installer   Cable Unplugged
8.7.1.0    (04/27/2006) Microsoft/Windows Update    Auto Disable
8.7.9.0    (10/24/2006) Lenovo T41 driver download  Auto Disable

(IPCONFIG works with Cable Unplugged, but not with Auto Disable.)
My hypothesis is that this problem was introduced by Intel in Version 8 of its drivers, probably as a well-intended minor improvement that fell prey to the Law of Unintended Consequences.

Fix:

• Use Windows XP Driver Roll Back or Uninstall/reboot/reinstall to go back to the original Windows XP driver, or otherwise install an older driver that doesn't exhibit this problem.
• Hide any updated driver in Microsoft/Windows Update to prevent unintentionally recreating this problem in the future. Likewise avoid recent driver updates from Lenovo.

Workarounds:

1. (Verified)
   1. Click Start > Control Panel > Network Connections, and for any wired network adapters that are Disabled:
   2. Right-click on My Computer, and click Manage to start Device Manager
   3. Disable wired Network Adapters that are disabled in Network Connections
   4. Run IPCONFIG as desired
   5. Re-Enable wired network adapters in Device Manager
2. (Verified)
   1. Click Start > Control Panel > Administrative Tools
   2. Double-click Services
   3. Scroll down to Routing and Remote Access
   4. If Routing and Remote Access is Disabled, change it to Manual
   5. Start Routing and Remote Access, or Stop and Re-Start it if it's already running
3. (Not verified)
   1. Uninstall Access Connections, Keyboard Customizer, Wi-Fi drivers, and Ethernet drivers
   2. Reinstall in this order Ethernet, Wi-Fi, Keyboard Customizer, Access Connections

Notes:

1. Turning off driver Power Management doesn't help.
2. ThinkVantage Access Connections isn't installed, so wouldn't seem to have any bearing on the problem.
3. The problem occurs whether or not the Intel PROSet for Windows Device Manager is installed.
4. There is no apparent option for turning off this auto Disable in Intel Version 8 drivers.

[Stargate199]

My Netgear wireless adapter in my desktop has this problem. I cannot use IPCONFIG nor the Repair utility. My workaround when it acts up (which is very rare) is to disconnect it manually from the Zero Config utility and then reconnect to my wireless. My Belkin wireless card in my T21 does not have this problem which is nice since I connect to multiple wireless networks. Pair this with Access Connections and I can keep different settings for my school's network and my home network.

[PatrickE]

Thanks, I was just running into this problem trying to set up port-forwarding.

This just made my day.

[JNavas]

This problem persists in the Intel PRO/1000 MT driver;

8.10.3.0
2008/08/20

As before, the fix is to fall back to driver:

7.2.17.101
2004/10/26

John

[Fignuts]

Can anyone recommend where to get the version 7.2.17.101 (or earlier) Intel PRO/1000 MT Mobile driver or installer? It doesn't seem to be available any more from Lenovo or Intel, and the only available driver versions cause this issue in Windows XP SP3.

Update: Found the answer to my own question. Get the 7.2.17.101 driver package here:
http://www-307.ibm.com/pc/support/site. ... 54046.html

Note: the installer file is named "1urc13ww.exe", released 2005/04/22, Build 94590. The Lenovo package description says it is only for Intel PRO/100 VE Network Connection, and is version 7.0.28.0, but it includes the 7.2.17.101 driver for the PRO/1000 MT Mobile.

You may have issues with Windows XP not allowing you to revert to the older driver, because it thinks a newer version is installed. In this case, you can "erase" the newer driver from Windows' driver cache by following the steps listed here:

http://winhlp.com/node/199

In the above example, replace the string "WG311T" with "e1000", to find the Intel PRO/1000 MT driver files.

[mslatte]

I just want to say I have NEVER registered for an account on a forum like this before in 20 years of online activity. However the advice here including how to revert back to a previous version of the Ethernet driver which was messing up the WLAN was perfect.

Many thanks.

I have now upgraded my T42 WLAN card successfully to a 802.11g from my now-dead T43.

MANY THANKS!!!

[JNavas]

I just want to say I have NEVER registered for an account on a forum like this before in 20 years of online activity. However the advice here including how to revert back to a previous version of the Ethernet driver which was messing up the WLAN was perfect.
Many thanks.
I have now upgraded my T42 WLAN card successfully to a 802.11g from my now-dead T43.
MANY THANKS!!!

Good to hear it helped! Thanks for letting us know.

[Jinx_Dojo]

I found another workaround on my R51: I was able to simply disable and then re-enable the wired Network Connection, then perform the "ipconfig" command within 30 seconds or so. This is similar to the first workaround above, but a bit easier to access than the Device Manager, and requires no re-enabling afterward (the connection remains enabled for me despite being unplugged). Let me know if this works for anyone else / any other models.

Beyond resource use and requiring admin, is there any not to set "Routing and Remote Access" to automatic? Is there a security issue here?

I'm really surprised IBM hasn't addressed this issue. IPConfig is important, and we shouldn't have to roll back drivers or even enable non-essential services to obtain proper functionality. Still: in my relatively short experience with this Thinkpad, I've been very happy to find most all of the issues I faced already addressed in a Knowledge Base article and an appropriate software solution was provided. It seems this is the one case where they dropped the ball. Nothing worth an angry e-mail to them, but still a tiny blemish on my otherwise high regard for their do-it-yourself support.

[Puppy]

No need to use older version of the driver. The fix is to edit a registry value as described here http://www.intel.com/support/wireless/w ... 031466.htm Taken from discussion here http://forums.lenovo.com/t5/T61-and-pri ... d-p/111425

I can confirm it works with my R51

[dr_st]

Nice!

Does this fix only the Wifi connection / IPCONFIG failures? Does the LAN itself still appear as disable (and impossible to reenable) when the cable is unplugged?

[Puppy]

Both LAN and WiFi works as expected now. I have Windows XP SP3, Access Connections not installed. Driver versions:

Intel PRO/1000 MT Mobile Connection - 8.10.3.0
Intel PRO/Wireless 2200BG Network Connection - 9.0.4.39