Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1232
  • Last Modified:

NIC won't release IP config after cable is unplugged.

I have 3 users all with Dell Precision M4400 laptops on Win XP SP3 using Intel 82567LM NIC's and all with the same issue. If I unplug the network cable from the laptop and run ipconfig at a command prompt it still shows the adapter with it's address instead of showing "media disconnected" as it should. The system tray icon for the connection does show the cable unplugged message. If I try an ipconfig/release and renew it generates an 169.254 address on the adapter even though it's unplugged.

I discovered this problem because the users were complaining that when they unplugged from the network they would lose access to everything even though the wireless connection is working. Even though the wired connection was unplugged and the wireless connection was active with a valid address, the computer was still trying to route traffic over the wired connection because it still shows an IP address.

The only way I can get the wireless connection to work correctly is to disable the wired connection. I can't seem to figure why windows won't see the media disconnected state even though it shows the "network cable unplugged" in the system tray. I've updated the Intel 82567LM drivers, updated the BIOS and even uninstalled and reinstalled the drivers to no avail.

The network adapters both wired and wireless are configured for DHCP.

Any help is appreciated.
0
icecreman
Asked:
icecreman
  • 7
  • 3
  • 2
  • +1
1 Solution
 
hydrokidCommented:
1) ipconfig /release would only help when you are connected to the network.. it will drop the IP address from the DHCP server.

2) when you are wired then wireless, all your traffic will route via wired because it has a lower metric as this is the preferred route. you can do a route print to check your routing and therefore if wired is unplugged, there should be a period of down time then traffic will start using the wireless route.

3) I guess the network driver is the issue in this case, do a roll back or get the latest driver to see if it's working..
0
 
icecremanAuthor Commented:
hydrokid,

1) I only tried ipconfig /release because according to the command prompt Windows still think it's connected.

2) I agree with you on this but even after rebooting the computer with the cable unplugged Windows generates an Auto-assigned IP on the LAN connection. Wireless never gets a chance to take over because Windows never sees that the media is disconnected. I should clarify that by saying that it sees the disconnected in the system tray (Network Cable Unplugged popup message) but in ipconfig it still shows the connection as active with an address.

3) The drivers I started with when troubleshooting this issue were original. I updated to Dell's latest drivers then Intel's latest drivers but neither made a difference.

Thanks for your input.
0
 
jat0369Commented:
Dell has this "helpful" powersaver feature that will disable some hardware in order to save battery life when running on battery power.

I suggest you make sure you're not running on battery power, reboot the machine, and try again.
0
NFR key for Veeam Agent for Linux

Veeam is happy to provide a free NFR license for one year.  It allows for the non‑production use and valid for five workstations and two servers. Veeam Agent for Linux is a simple backup tool for your Linux installations, both on‑premises and in the public cloud.

 
icecremanAuthor Commented:
jat0369,

Thanks for the reply. I'm aware of Dell's "helpful" powersaver, I always disable it. This problem happens when it's plugged into power and on battery. The computer shows the cable unplugged (as it should) in the system tray but ipconfig still thinks the cable is plugged in. I thought it may be an issue with the TCP/IP protocol but all three computers of the exact same model have this issue. We are a Dell house and none of our other laptops have this problem.
0
 
glitch177kCommented:
Do you have a dock? Our dell laptops experience similar issues when docked/undocked as the laptop has a default behavior that changes with each status. When ours are docked, wireless doesn't function properly without manually altering the status of the wireless connection while docked and same goes for when it is not connected to the dock where we experience weird wired connection behavior.
0
 
icecremanAuthor Commented:
No dock. This isn't really a wireless problem. The real problem is that ipconfig doesn't know when the cable is unplugged. The system tray sees it but ipconfig acts as if the network cable is still plugged in. With the network cable unplugged ipconfig should say "media disconnected" for the LAN connection but it still shows the address information. Even rebooting the computer with the cable unplugged doesn't help. The computer just auto assigns itself an IP address.  I mention wireless because it's affected due to the routing table.
0
 
hydrokidCommented:
If you have quickset installed from dell. you should remove it in the add/remove programs.
0
 
icecremanAuthor Commented:
No Quickset. Dell uses DCP (Dell Control Point) now which is worse but I have that removed on all of our laptops.
0
 
jat0369Commented:
Just out of curiosity, can you ipconfig /all and show us what you're seeing?
0
 
icecremanAuthor Commented:
Here is a pic of the ipconfig/all screen.  Thanks.
ipconfig.jpg
0
 
hydrokidCommented:
I'm using the same drivers but this is behaving properly.
I suggest you go to device manage and uninstall the driver Intel 82567 and rescan hardware.
The LAN drive will automatically install again.

There are some diagnostics test on the intel driver tabs, you can run those test to see if it releases the APIPA IP.
0
 
icecremanAuthor Commented:
Thanks, I did uninstall and rescan the hardware but no change. I'll try the diagnostics next.
0
 
icecremanAuthor Commented:
Solved. I reset the the TCP/IP protocol using..

netsh winsock reset

and

netsh int ip reset resetlog.txt

at the command prompt and then rebooted. All is well now. I'm guessing 3rd party software modified something that needed to be reset.

Thanks to all for your suggestions.
0

Featured Post

Evaluating UTMs? Here's what you need to know!

Evaluating a UTM appliance and vendor can prove to be an overwhelming exercise.  How can you make sure that you're getting the security that your organization needs without breaking the bank? Check out our UTM Buyer's Guide for more information on what you should be looking for!

  • 7
  • 3
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now