Unsolved
This post is more than 5 years old
3 Posts
0
9454
June 8th, 2009 06:00
Error renewing IP Address
I was trying to go online and a error came up saying tht I had no connectivity to the internet, so I ran a diagnostic test. I tried to renew my IP address and received an error message stating Error renewing ip address: the semaphore timeout period has expired. my network adapter is working just fine, so I know that is not the problem.
My winsock diagnostic check was fine too, but when I ran a http, https and ftp diagnostic test I received an error for all three saying a connection could not be made. Can I fix this problem on my own?
0 events found
No Events found!
PudgyOne
11 Legend
•
30.3K Posts
•
106.6K Points
0
June 8th, 2009 08:00
davhaught,
Did you try turning off your ISP Modem router, your wireless router and your computer(s) for 60 seconds, then turn everything back on and see it the connection works?
Also try How to repair a connection
More tips can be found at...
Welcome, PLEASE READ FIRST
Rick
PudgyOne
11 Legend
•
30.3K Posts
•
106.6K Points
0
June 8th, 2009 08:00
davhaught,
Install any programs or updates just before this happened? IE8 by chance?
Please check your connections first. My wife accidentally bumped mine the other day and I couldn't connect and then she told me. I took out each connector and reconnected them and was back online in 5 minutes.
Here is how to rest your Winsock.
Winsock2 How to determine and to recover from Winsock2 corruption in Windows Server 2003, in Windows XP, and in Windows Vista
But...
it's simplier to try using WinSock XP Fix
and see if that correct your problem.
davhaught
3 Posts
0
June 8th, 2009 08:00
I do not have wireless, but I did reset my modem and turned my computer off for 60 seconds before I rebooted.
I also tried start, run, cmd, ipconfig /release, ipconfig /renew, ipconfig /flushdns and still could not get my ip address to renew.
davhaught
3 Posts
0
June 8th, 2009 09:00
I have not installed any programs or updates before this happened. I also ran an winsock diagnostic and the results were that the provider chains were valid along with the loopback communication test and the msafd tcpip loopback communication test. The last entry on the diagnostic test for winsock was that the connectivity is valid for all winsock providers.
Davet50
6 Operator
•
14.4K Posts
0
June 8th, 2009 10:00
ping your modem with this command ping -t (add the ip address of your modem.)
for example my modem is 192.168.100.1 so my comand would be ping -t 192.168.100.1
report back with the error messages.