 How To Repair A Broken Ip Stack, PC can't get IP address from DHCP server |
Welcome Guest ( Log In | Click here to Register a free account now! )
Register a free account to unlock additional features at BleepingComputer.com
Welcome to Bleeping Computer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.| Important Announcement: The winners of the BC Million Post contest have been announced. You can read who the winners are at this post. - BleepingComputer Management |
  |
 Mar 27 2007, 07:56 PM
Post
#1
|
|
|
New Member  Group: Members Posts: 6 Joined: 9-March 07 Member No.: 116,504  |
|
 |
 
|
|
Mar 28 2007, 08:41 AM
Post
#2
|
|
 Forum Addict Group: HJT Junior Classmen Posts: 3,980 Joined: 7-January 07 From: UK Member No.: 105,123 |
Hello,
Download this tool and tell it to do a scan, it will fix network problems and conflicts. http://iobit.com/AdvancedWindowsCarePersonal/index.html If that doesn't work, go to start run and type services.msc make sure that the services with network, wireless and dhcp are all started. then try to connect. If that doesn't work go to start then run and type cmd when it comes up, type ipconfig /release press enter ipconfig /renew press enter ipconfig /flushdns press enter Once you have done all this try and connect If that still doesn't work, go to your network adaptors, right click the one that you are trying to use, select properties scroll down the list until you find internet protocol tcp/ip select that and go to properties. make sure it is set to recieve ip address automatically. Hope this helps -------------------- Regards
Alan |
|
|
|
|
Mar 29 2007, 09:27 AM
Post
#3
|
|
|
New Member Group: Members Posts: 6 Joined: 9-March 07 Member No.: 116,504 |
Thank you for your suggestions nigglesnush85. I tried all your suggestions without success but was able to correct the problem by running netsh winsock reset command in a DOS box. This automatically detects & repaired the problem.
Thank you again! |
|
|
|
|
Mar 29 2007, 09:32 AM
Post
#4
|
|
 Bleepin' Conundrum Group: Global Moderator Posts: 9,325 Joined: 26-April 04 From: 65 miles due East of the "Logic Free Zone", in Md, USA Member No.: 235 |
Thanks for telling us what worked for you AllenB.
That may well help another on the BC too. -------------------- |
|
|
|
|
Mar 29 2007, 09:55 AM
Post
#5
|
|
|
New Member Group: Members Posts: 6 Joined: 9-March 07 Member No.: 116,504 |
My pleasure KoanYorel.
The specific method of using this is to open a DOS box, (windows-run-cmd & OK), then type "netsh winsock reset" at the default prompt without quotes & press the Enter key. Thank you all for your support. Together we can win this! |
|
|
|
|
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:
| Lo-Fi Version | Time is now: 22nd November 2008 - 12:10 PM |
© 2003-2008 All Rights Reserved Bleeping Computer LLC.