Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, 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.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

How To Repair A Broken Ip Stack


  • Please log in to reply
4 replies to this topic

#1 AllenB

AllenB

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:12:29 PM

Posted 27 March 2007 - 07:56 PM

A static address can't see the router & this computer can't get an IP address from the router either. Does anyone know how to repair this kind of problem? Thank you in advance!

BC AdBot (Login to Remove)

 


#2 nigglesnush85

nigglesnush85

  • Members
  • 4,371 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:UK
  • Local time:07:29 PM

Posted 28 March 2007 - 08:41 AM

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.

#3 AllenB

AllenB
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:12:29 PM

Posted 29 March 2007 - 09:27 AM

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!

#4 KoanYorel

KoanYorel

    Bleepin' Conundrum


  • Staff Emeritus
  • 19,461 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:65 miles due East of the "Logic Free Zone", in Md, USA
  • Local time:03:29 PM

Posted 29 March 2007 - 09:32 AM

Thanks for telling us what worked for you AllenB.

That may well help another on the BC too.
The only easy day was yesterday.

...some do, some don't; some will, some won't (WR)

#5 AllenB

AllenB
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:12:29 PM

Posted 29 March 2007 - 09:55 AM

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!




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users