Internet connected but browser not working
Closed
opelander
Posts
3
Registration date
Sunday August 10, 2014
Status
Member
Last seen
August 14, 2014
-
Aug 10, 2014 at 01:04 PM
opelander Posts 3 Registration date Sunday August 10, 2014 Status Member Last seen August 14, 2014 - Aug 14, 2014 at 11:09 AM
opelander Posts 3 Registration date Sunday August 10, 2014 Status Member Last seen August 14, 2014 - Aug 14, 2014 at 11:09 AM
Related:
- Internet connected but browser not working
- Internet connected but browser not working windows 10 - Guide
- Torch browser - Download - Browsers
- Flock browser - Download - Browsers
- Fenix internet l - Guide
- Ur browser - Download - Browsers
2 responses
opelander
Posts
3
Registration date
Sunday August 10, 2014
Status
Member
Last seen
August 14, 2014
Aug 11, 2014 at 10:59 AM
Aug 11, 2014 at 10:59 AM
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 October 8, 2008
Status
Contributor
Last seen
June 15, 2019
1,824
Aug 10, 2014 at 09:17 PM
Aug 10, 2014 at 09:17 PM
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 August 10, 2014
Status
Member
Last seen
August 14, 2014
Aug 14, 2014 at 11:09 AM
Aug 14, 2014 at 11:09 AM
pls answer
