Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

unable to connect to internet, unable to renew/release ip address 1

Status
Not open for further replies.

GrymJak

Technical User
Dec 11, 2002
5
US
i have an xp pro system on a network with 2 other xp machines. connected through a hub to a cable modem. all 3 were connecting to the internet. recently 1 machine stopped connecting to the net. nothing i know of has changed internally. changing the nic didn't repair it. changing cables and ports on the hub also didn't help. reseting tcpip didn't help either. the net connection says it's connected. gives a 169.xx ip addy says the nic is working fine. setting are for getting ip addy auto, use dhcp. auto detect settings. the other 2 machines have no problem connecting to the net. i've tried connecting without the hub (connected straight to the cable modem) and with the hub but with the other machines turned off/on. nothing changes. when i try using ipconfig /release it says no adapters available to preform this operation. same for /renew. any suggestions? if you need more info leave a message. it's really pushed me to the end on this problem. thanks everyone
 
Two questions:

- Are you using a simple hub or a cable/DSL router?
- What do the IP address of the other machines start with?

If you are just using a hub then you might have one of those cable companies that will give you more than one IP ... is it possible that they've decided to reduce the number down to two? If so get yourself a cable/DSL router.

I believe the 169.xxx.xxx.xxx address is the fail over address that Windows XP gives if it cannot find a DHCP server. This means that you either have connection problems or the DHCP server is neglecting to give you an address like the situation I describe above.

Later ...
 
ozcdn its a simple hub, the other machines that still connect have ip's of 24.xx.xx.xx

if it was the isp limiting the ip addresses, shouldn't the computer connect when it was the sole computer connected to the cable modem because it doesn't.

bcastner i will try the winsock repair, i'm not at the problem computer. thanks again y'all.
 
bcastner -that fixed it! thank you, so very much!
problem solved, thanks everyone.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top