ipconfig /release not working

[Greg Zlatunich]

I'm trying to connect my PC to a DSL modem. It had been
working but in troubleshooting a problem with the ISP
software they had me remove their software. In doing
that, I lost connection to the DSL connecting. In trying
to fix the problem I am finding that the
ipconfig /release commmand does not clear the ip
address. Anyone know what might be causing this behavior?

Thanks,

Greg

 

[Steve Winograd [MVP]]

I'm trying to connect my PC to a DSL modem. It had been
working but in troubleshooting a problem with the ISP
software they had me remove their software. In doing
that, I lost connection to the DSL connecting. In trying
to fix the problem I am finding that the
ipconfig /release commmand does not clear the ip
address. Anyone know what might be causing this behavior?

Thanks,

Greg

Is the IP address 169.254.x.x? If so, it wasn't assigned by DHCP, so
it can't be released by ipconfig. That address indicates that the PC
tried, but failed, to get an IP address from a DHCP server.
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com

 

[Jamir Correa \(MSFT\)]

Greg,

Let me ask you a few questions if you don't mind.

1- Do you get any message when trying to use the /release switch with
ipconfig?
2- How is your tcp/ip configured? To obtain the IP automatically? Set
statically?
3- What happens when you try to right click on your connection and choosing
"Repair"? If it still fails, do you get any message?
4- Do you get any Errors on the System Event logs?
5- Have you tried to remove your NIC and reinstall it?

Thank you,

Jamir Correa
Microsoft Corporation

This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Greg Zlatunich]

Steve,

Yes, the address is 169.254.101.194. To eliminate the
cable from PC to router I put another PC on the line and
it worked. To eliminate the NIC in the PC, I installed a
new NIC in one of the PCI slots, same problem. I have a
Realtek NIC installed and I am not trying to find the
drivers so that I can reload. That seems odd though give
I just installed a new D-Link NIC with good drivers and I
have the same problem.

Thanks for the advice,

Greg

-----Original Message-----

 

[Greg Zlatunich]

Jamir,

1. I get no message when I use the /release switch. I
immediately get the results of an ipconfig command. The
ip address is 169.254.101.194
2. tcp/ip is configured to obtain the IP automatically
3. Repair fails specifically pointing to /renew not
working
4. No errors in the system log but plenty of warnings
involving dhcp. This is the error:

Your computer was not able to renew its address
from the network (from the DHCP Server) for the Network
card with address 0010DC8BD1E8. An operation was
attempted on somthing that is not a socket

5. I did not replace the NIC, it is too hard to get
behind the fan and get it out without opening the entire
box. I only wanted to try that as a last resort. I have
tried installing a new NIC in a PCI slot. Same problem.

Thanks for you reply,

Greg Zlatunich

 

[Steve Winograd [MVP]]

1. I get no message when I use the /release switch. I
immediately get the results of an ipconfig command. The
ip address is 169.254.101.194
2. tcp/ip is configured to obtain the IP automatically
3. Repair fails specifically pointing to /renew not
working
4. No errors in the system log but plenty of warnings
involving dhcp. This is the error:

Your computer was not able to renew its address
from the network (from the DHCP Server) for the Network
card with address 0010DC8BD1E8. An operation was
attempted on somthing that is not a socket

5. I did not replace the NIC, it is too hard to get
behind the fan and get it out without opening the entire
box. I only wanted to try that as a last resort. I have
tried installing a new NIC in a PCI slot. Same problem.

The "not a socket" error is probably the result of a corrupted TCP/IP
stack. Follow the steps in this Microsoft Knowledge Base article to
repair it:

How to determine and recover from Winsock2 corruption
http://support.microsoft.com/?id=811259
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com

 

[Steven Hull]

Before you go thru all that with the TCP/IP stack, tell me if you are
receiveing any packets. Double click your network connection to see. If
you are sending and receiving nothing is really wrong physically. Post back
with what you got. Sometimes just simply enableing/disableing your
connection works. (do that so it will reset to zero). I would have to say
that something could be wrong with the cable. As they always say, "Check
the cables first"!

Steve,

Yes, the address is 169.254.101.194. To eliminate the
cable from PC to router I put another PC on the line and
it worked. To eliminate the NIC in the PC, I installed a
new NIC in one of the PCI slots, same problem. I have a
Realtek NIC installed and I am not trying to find the
drivers so that I can reload. That seems odd though give
I just installed a new D-Link NIC with good drivers and I
have the same problem.

Thanks for the advice,

Greg