Internet connected but browser not working
Closed
opelander
Posts
3
Registration date
Sunday 10 August 2014
Status
Member
Last seen
14 August 2014
-
10 Aug 2014 à 13:04
opelander Posts 3 Registration date Sunday 10 August 2014 Status Member Last seen 14 August 2014 - 14 Aug 2014 à 11:09
opelander Posts 3 Registration date Sunday 10 August 2014 Status Member Last seen 14 August 2014 - 14 Aug 2014 à 11:09
Related:
- Internet connected but browser not working
- Internet connected but browser not working windows 11 - Guide
- Ur browser - Download - Browsers
- Crazy browser - Download - Browsers
- Torch browser - Download - Browsers
- Connected no internet access pldt ✓ - Network Forum
2 responses
opelander
Posts
3
Registration date
Sunday 10 August 2014
Status
Member
Last seen
14 August 2014
11 Aug 2014 à 10:59
11 Aug 2014 à 10:59
i did it through device manager i Found out that the drivers were outdated, but for some reason it doesnt seem to be the problem since the problem is still there.
btw it actually works in safe mode
thx for the reply and I hope you can help fixing this
btw it actually works in safe mode
thx for the reply and I hope you can help fixing this
xpcman
Posts
19528
Registration date
Wednesday 8 October 2008
Status
Contributor
Last seen
15 June 2019
1,824
10 Aug 2014 à 21:17
10 Aug 2014 à 21:17
the server's transport detected a error condition and reset your TCP/IP connection. There lots of reasons for this but it is best to focus on the ones that are caused by your side of the connection (you can fix those).
Number 1: your network driver assembles a TCP/IP packet incorrectly (corrupts a packet) the checksum routines request the packet again, the server
sends it and your network driver assembles it incorrectly (again) the checksum routine finds a error and request the packet to be sent again, the server does this over and overt until a certain counter goes off and the server gives up and resets your connection.
same thing happens if your netcard just drops a packet, it just keeps asking for the packet # over and over. server sends it over and over then gives up and resets the connection.
Ok, number one solution to this problem is to update your network drivers to a current version.
if you do this and it fails, you could be in the rare condition where the packets are being corrupted by your router or some other network device.
but that takes more effort to prove/fix. Just start with your network driver update and see if that fixes your issu
Number 1: your network driver assembles a TCP/IP packet incorrectly (corrupts a packet) the checksum routines request the packet again, the server
sends it and your network driver assembles it incorrectly (again) the checksum routine finds a error and request the packet to be sent again, the server does this over and overt until a certain counter goes off and the server gives up and resets your connection.
same thing happens if your netcard just drops a packet, it just keeps asking for the packet # over and over. server sends it over and over then gives up and resets the connection.
Ok, number one solution to this problem is to update your network drivers to a current version.
if you do this and it fails, you could be in the rare condition where the packets are being corrupted by your router or some other network device.
but that takes more effort to prove/fix. Just start with your network driver update and see if that fixes your issu
opelander
Posts
3
Registration date
Sunday 10 August 2014
Status
Member
Last seen
14 August 2014
14 Aug 2014 à 11:09
14 Aug 2014 à 11:09
pls answer
