ipconfig /release not working

J

Jerry

I'm trying to get my cable modem set up via a Linksys NIC.
I was originally connected via usb, but would like to
network so I installed the nic and have the current
drivers. Not going thru a router (yet), and I've got green
lights all around on modem and nic, however I can't get a
network connection. I'm set up as DHCP enabled and to
obtain ip and dns automatically. When I run ipconfig /all
I see a 169.254.xxx.xxx ip for my nic. I've tried to
repair it and to run ipconfig /release and renew, however
when I try to release the ip remains, and if I try renew I
get an error message saying I'm performing an operation on
something that is not a socket. How can I clear this ip
address and allow my nic to be assigned an ip from DHCP as
it should be? I've even tried the Microsoft-suggested
process of deleting winsock and winsock2 from the registry
and reloading tcp/ip from the netshell utility. I'm
stumped. Any ideas?
 
R

Robert L [MS-MVP]

quoted form http://www.ChicagoTech.net
Can't obtain/renew IP addresses from the DHCP server

Symptoms: 1) you have a DHCP client which may not be able to obtain/renew IP
addresses from the DHCP server intermittently. 2) after setup a workstation
to obtain an IP address from DHCP, the machine can't ping others and
ipconfig /all shows Autoconfiguration IP Address. . . : 169.254.x.x.

Resolutions: 1) If this is XP, obtain the latest service pack for Windows
XP.
2) Use the Network Diagnostics tool to identify any failed settings. To do
this, go to Help and Support>Use Tools to view your computer information and
diagnose problems>Network Diagnostics>Scan your system. When the process
finishes, check for any items marked "FAILED" in red, expand those
categories, and view the additional details about what the testing showed.
3) Assign a static ip on the client and ping the DHCP server. If you can't
ping the DHCP server, check the connection and hardware.
4) If you can ping the DHCP after assigning static ip, check the DHCP
settings.
5) Make sure no firewall is running on your LAN.
6) Run Repair this connection if it is XP. Or use netsh to reset TCP/IP
configuration.
7) If it is win98/w2k, remove and reinstall TCP/IP.
8) Try to upgrade the new NIC driver.
--
For more and other information, go to http://www.ChicagoTech.net


Don't send e-mail or reply to me except you need consulting services.
Posting on MS newsgroup will benefit all readers and you may get more help.

Robert Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN, Anti-Virus, Tips & Troubleshooting on
http://www.ChicagoTech.net
This posting is provided "AS IS" with no warranties.
 
S

sharon

If so, you have a damaged winsock2 key in the registry.

You should check System Information (winmsd)
START > RUN - type in winmsd and click OK
Expand Components / Network / click on Protocol -
if the section headings item of "Name" have a value
starting with anything other than MSAFD or RSVP
then that is probably what is causing the problem.

Examples:

MSAFD Tcpip [TCP/IP]
MSAFD Tcpip [UDP/IP]
RSVP UDP Service Provider
RSVP TCP Service Provider
MSAFD NetBIOS [\Device\NetBT_Tcpip...
and so on

It may be a third-party firewall or a Spyware or a Virus.
("New.Net" is a common spyware for example)
Make sure that MSCONFIG is in Normal Startup
and then see if uninstalling the third party firewall
(best done from its own uninstall program if available)
or the Spyware from Add Remove Programs will
resolve the issue. If it's a virus, then only an Anti
Virus Program
will be able to deal with that.

You may want to try downloading either Ad-Aware 6 or Spybot
to another computer and then installing one of them on the
infected XP Home/Pro
computer and try to wipe out Spyware and see if that
resolves the issue.

Ad-aware 6.0 build 181
http://download.com.com/3000-2144-10214379.html?tag=list

Spybot - Search & Destroy 1.2
http://download.com.com/3000-2144-10194058.html?tag=list


If none of that works or is possible, you could try this
method
for replacing the winsock and winsock2 registry keys:

Uninstall any third-party proxy software or firewall
programs before proceeding.
You may want to consider enabling the XP ICF at least
temporarily especially
if you are not current with the XP Critical Updates.

Step 1: Delete registry keys

A)Open Regedit from the Run line
B)Go to both of the following keys, EXPORT each of them,
and then delete them:
(To export a key, you right click on it and
choose "export" - you can choose where to export them to -
DESKTOP is handy -
and you need to type in a file name such as "exported
Winsock key" / "exported WinSock2 key"
and then click on SAVE)

HKLM\SYSTEM\CurrentControlSet\Services\Winsock
HKLM\SYSTEM\CurrentControlSet\Services\WinSock2
C)Restart the computer

NOTE: It is important to restart the computer after
deleting the Winsock keys.
Doing so causes the XP operating system to recreate shell
entries for those two
keys. If this is not done, the next step does not work
correctly.

Step 2: Install TCP/IP on top of itself

A)Open the properties window of the network connection
(Local Area Connection)
B)Click Install
C)Click Protocol, then Add
D)Click Have Disk
E)Type the path to the \%systemroot%\inf folder (usually
C:\Windows\inf) and click OK
(if you try to click Browse, then browse to the \inf
folder,
it may not show up in the list)
F)You should now see "Internet Protocol (TCP/IP)" in the
list of available
protocols. Select it and click OK.
G)Restart the computer

When the computer reboots you will have functional Winsock
keys.
If so, then be sure to delete the exported winsock and
winsock2 reg files.
(You don't want to accidentally put them back in the
registry)

Side effects and possible problems:

This method will restore basic functionality to the
Winsock keys, but is not a
complete rebuild. On a default install of Windows XP the
registry key:
HKLM\SYSTEM\CurrentControlSet\Services\Winsock2\
Parameters\Protocol_Catalog9\Catalog_Entries will have 11
sub-keys.
When applying this method, the Catalog_Entries will only
have 3 sub-keys.
However, it works and there does not appear to be any side
effects.
The missing entries relate back to the:
HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Int
erfaces key.
Also, third-party proxy software or firewalls may need to
be reinstalled.
==========================================================
 
G

Guest

Sharon, thank you so much. Your advice worked perfectly. The step I was missing was restarting the pc after deleting the winsock keys and before reinstalling tcp/ip. This step wasn't mentioned in MS's own instructions! Thanks again!
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top