NIC not able to release IP address

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have an IBM T40 Laptop with an Intel Pro 100/VE Adapter card

My user was following the VPN install list
and the TCP/IP Service is no longer working we've uninstalled the card a few
times and still nothing
we get this message when we try to release the ip address

This is what we get

"All adapters bound to DHCP do not have DHCP addresses. The Addresses were
automatically configured and can not be released"

the IP address is 169.254.139.244
subnet mask 255.255..0.0

Any help would be great thanks!!!

Ant
 
Your problem is that the network card is not seeing your DHCP server or
device and is being assigned a private IP address. You cannot release or
renew it. The first thing you need to discover is why you aren't picking up
an IP address automatically, or at least where you should be getting an IP
address from.

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm
 
That is APIPA in action (Automatic Private IP Address 169.254.0.0/24) and can
be very difficult to 'undo'. One way is to disable and enable the NIC without
resorting to reboot. As you have already found out, "ipconfig /renew" or
"ipconfig /release" does not often work.

If APIPA bothers you, try disabling it.

See
http://support.microsoft.com/default.aspx?scid=kb;en-us;244268
for more info on how this may be accomplished.

Do let us know if it helps. Thanks!
 
If you have multiple adapters, you could try and release the IP address
of the particular adapter like this
% IPCONFIG.exe /release "Local Area Connection 2"

Have you tried this?

If you have problems with DHCP, try setting a fixed address and then
pinging the DHCP server, if this is successful, set the adapter back to
recieve an IP address via DHCP then you might want to edit the following
key in the registry.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\<adapterCLSID>

and setting "DhcpServer" to the IP address of the DHCP server

or if you are using APIPA set the following parameters
"IPAutoconfigurationAddress" and "IPAutoconfigurationMask" under the
same key to reflect your APIPA address configuration.

All the best. Please let us know how you get on and how you resolved
this issue.
 
Back
Top