B
BuPher
Hello, I've been experiencing a problem in my DSL network the past months, and I will try my best to explain what is going on, what I noticed and what I tried (with the results). I've been using the software mumble's connection interface to indicate whether I had internet access or not, and if yes, if I could use my internet and connect to servers (Sometimes ping shows up but with a severely high packet loss and inability to connect or use internet).
My setup:
Router/Modem (tbh I have no idea if my device is both a router and a modem, but it's the only device plugged to the phone line): SAGEM F@ST™ 2604
Hardware Version: 253124416
Serial Number: LK835025071
Software Version: 3.21a4G
Wireless Driver Version: 4.150.10.15.cpe2.2
Medium between the router/pc: A cheap ethernet cable (that was replace over and over again but the issue still stands)
PC Network Card: Intel(R) PRO/100 VE Network Connection
PC OS: unregistered copy XP Sweet (By kal)
Where the problem began:
A couple of months ago, I've noticed a weird increase in packet loss (>3%) and sometimes when the router is launching, the message "limited connectivity" would appear on my pc briefly before either going away or getting fixed when I click the "Repair" button in the "Status" dialogue representing my connection to the router. Note that nothing involving wireless connection was ever affected in anyways, and this problem only appeared on any device using ethernet and the only current one is my pc (sometimes I plug in my sister's laptop when playing a video game online)
However, we had to repaint our house at one point and so we removed the phone setup temporarily (The DSL was connected to the phone which acted as a tool to separate the phone line from the ISP (as the technicians literally said). ) When putting everything back, however, the home telephone's port got damaged and the phone cable was stuck inside it, however it was perfectly functional, internet went back to normal (after a small disconnection) UNTIL the next day...
The next day my PC's internet was barely functional and my download speed was 4.4 kB/s at startup (my cap speed is 4Mbits), however after half an hour it went back to normal with a packet loss that hovered between 5%-0%. The next day the internet download speed was even slower and the packet loss was higher than 20%, but after an hour or so it went back to being normal. This went on for a week, on startup the internet would be so bad and then it would get fixed, with each day taking longer than the previous one.
One day, it refused to work alltogether and my mumble's Interface said I had a "70 ping (perfectly normal) but a 40% packet loss rate". It didn't work for two days until I touched the phone cables a little and restarted the router a few times after reconfiguring the wires. So I assumed the problem was coming from the telephone and this proved to be correct as whenever anybody would touch the telephone, internet on my pc ALONE ( wifi devices were unharmed) would stop working and show a ridiculously high packet loss % and partially load a page (title only, background only etc...).
So I replaced the telephone, the phone and internet cable in the wall (reinstalled new ones), and my ethernet cable. The internet worked for a day or two before stopping again. Which made no sense to me as the previous setup was faulty but now it's all gone and it's replaced with proper devices, so I had to test the connection between the router and my PC. I noticed that each ethernet port, although still not working, provided different results. Port 1 Had the lowest packet lost and ping (40% and 68 ping), port 2 and 3 gave atrocious results, however port 4 was really complicated; it had bad results however whenever I manage to fix the connectivity and connect to internet, it was through port 4. Then I would just plug in the ethernet to port 1 and it would go back to normal, for the time being.
If I reboot the modem when the connection is all messed up, the pc would show the message "Limited internet connectivity: you are seeing this because your router failed to attribute an IP adress to this computer, click this message to resolve" (of course it doesn't resolve it), and when I go to the "Status" dialogue of my connection, it gives off a completely different ip than the one my router is using. So what I've done is I manually set the settings of my TCP/IP on my PC to match the ones on the router (with the only difference being the "gateway", because it was always my router's IP adress. However, on the router it shows a different adress, yet the internet works).
Doing this made my PC detect internet again and upon launching mumble (and after waiting a little) it showed "68 ping" that kept hovering around that value, however an extremely atrocious 92% packet loss. Port 1 showed that value, port 3 and 4 showed the same value and port 2 stopped working all together.
I launched the command prompt and trying pathpinging google using "pathping google" and it yielded these results:
(My pc is in french and I can't copy paste from it since im not using it so I had to roughly translate
==========================
Determining route to google.com [172.271.41.142]
With a maximum of 30 jumps:
0 sweet-c6236374e (//<= my pc) [192.168.1.14]
1 * * *
Treating statistics for 25 seconds:
Source Towards Here This node/link
Jump Ping Lost/sent = Lost/sent = Address
0 ---------- 100/100=100% [192.168.1.14] sweet-c6236374e
1 ------ 100/100=100% 0/100=0% [0.0.0.0] sweet-c6236374e
====================
So I tried pathpinging my router's ip (Im not sure if that works that way, but this is what I got anyways)
===============
Determining route to 192.168.1.1
With a maximum of 30 jumps:
0 sweet-c6236374e (//<= my pc) [192.168.1.14]
1 192.168.1.1
Treating statistics for 25 seconds:
Source Towards Here This node/link
Jump Ping Lost/sent = Lost/sent = Address
0 ---------- 90/100=100% [192.168.1.14] sweet-c6236374e
1 ------ 90/100=100% 0/100=0% 192.168.1.1
=================
I didn't entirely understand the test results, but I noticed that each time, the 192.168.1.14 jump is the one that caused trouble. So does it mean the problem is from my PC's Network Card? Or is it from my modem's ports? And if all Wifi devices function regularly, is a simple fix to purchase A wifi USB Key/Adapted and use it instead? Or should the pc be replaced? (it is an old pc, around 10 years old, however it's all I can afford for the time being).
My setup:
Router/Modem (tbh I have no idea if my device is both a router and a modem, but it's the only device plugged to the phone line): SAGEM F@ST™ 2604
Hardware Version: 253124416
Serial Number: LK835025071
Software Version: 3.21a4G
Wireless Driver Version: 4.150.10.15.cpe2.2
Medium between the router/pc: A cheap ethernet cable (that was replace over and over again but the issue still stands)
PC Network Card: Intel(R) PRO/100 VE Network Connection
PC OS: unregistered copy XP Sweet (By kal)
Where the problem began:
A couple of months ago, I've noticed a weird increase in packet loss (>3%) and sometimes when the router is launching, the message "limited connectivity" would appear on my pc briefly before either going away or getting fixed when I click the "Repair" button in the "Status" dialogue representing my connection to the router. Note that nothing involving wireless connection was ever affected in anyways, and this problem only appeared on any device using ethernet and the only current one is my pc (sometimes I plug in my sister's laptop when playing a video game online)
However, we had to repaint our house at one point and so we removed the phone setup temporarily (The DSL was connected to the phone which acted as a tool to separate the phone line from the ISP (as the technicians literally said). ) When putting everything back, however, the home telephone's port got damaged and the phone cable was stuck inside it, however it was perfectly functional, internet went back to normal (after a small disconnection) UNTIL the next day...
The next day my PC's internet was barely functional and my download speed was 4.4 kB/s at startup (my cap speed is 4Mbits), however after half an hour it went back to normal with a packet loss that hovered between 5%-0%. The next day the internet download speed was even slower and the packet loss was higher than 20%, but after an hour or so it went back to being normal. This went on for a week, on startup the internet would be so bad and then it would get fixed, with each day taking longer than the previous one.
One day, it refused to work alltogether and my mumble's Interface said I had a "70 ping (perfectly normal) but a 40% packet loss rate". It didn't work for two days until I touched the phone cables a little and restarted the router a few times after reconfiguring the wires. So I assumed the problem was coming from the telephone and this proved to be correct as whenever anybody would touch the telephone, internet on my pc ALONE ( wifi devices were unharmed) would stop working and show a ridiculously high packet loss % and partially load a page (title only, background only etc...).
So I replaced the telephone, the phone and internet cable in the wall (reinstalled new ones), and my ethernet cable. The internet worked for a day or two before stopping again. Which made no sense to me as the previous setup was faulty but now it's all gone and it's replaced with proper devices, so I had to test the connection between the router and my PC. I noticed that each ethernet port, although still not working, provided different results. Port 1 Had the lowest packet lost and ping (40% and 68 ping), port 2 and 3 gave atrocious results, however port 4 was really complicated; it had bad results however whenever I manage to fix the connectivity and connect to internet, it was through port 4. Then I would just plug in the ethernet to port 1 and it would go back to normal, for the time being.
If I reboot the modem when the connection is all messed up, the pc would show the message "Limited internet connectivity: you are seeing this because your router failed to attribute an IP adress to this computer, click this message to resolve" (of course it doesn't resolve it), and when I go to the "Status" dialogue of my connection, it gives off a completely different ip than the one my router is using. So what I've done is I manually set the settings of my TCP/IP on my PC to match the ones on the router (with the only difference being the "gateway", because it was always my router's IP adress. However, on the router it shows a different adress, yet the internet works).
Doing this made my PC detect internet again and upon launching mumble (and after waiting a little) it showed "68 ping" that kept hovering around that value, however an extremely atrocious 92% packet loss. Port 1 showed that value, port 3 and 4 showed the same value and port 2 stopped working all together.
I launched the command prompt and trying pathpinging google using "pathping google" and it yielded these results:
(My pc is in french and I can't copy paste from it since im not using it so I had to roughly translate
==========================
Determining route to google.com [172.271.41.142]
With a maximum of 30 jumps:
0 sweet-c6236374e (//<= my pc) [192.168.1.14]
1 * * *
Treating statistics for 25 seconds:
Source Towards Here This node/link
Jump Ping Lost/sent = Lost/sent = Address
0 ---------- 100/100=100% [192.168.1.14] sweet-c6236374e
1 ------ 100/100=100% 0/100=0% [0.0.0.0] sweet-c6236374e
====================
So I tried pathpinging my router's ip (Im not sure if that works that way, but this is what I got anyways)
===============
Determining route to 192.168.1.1
With a maximum of 30 jumps:
0 sweet-c6236374e (//<= my pc) [192.168.1.14]
1 192.168.1.1
Treating statistics for 25 seconds:
Source Towards Here This node/link
Jump Ping Lost/sent = Lost/sent = Address
0 ---------- 90/100=100% [192.168.1.14] sweet-c6236374e
1 ------ 90/100=100% 0/100=0% 192.168.1.1
=================
I didn't entirely understand the test results, but I noticed that each time, the 192.168.1.14 jump is the one that caused trouble. So does it mean the problem is from my PC's Network Card? Or is it from my modem's ports? And if all Wifi devices function regularly, is a simple fix to purchase A wifi USB Key/Adapted and use it instead? Or should the pc be replaced? (it is an old pc, around 10 years old, however it's all I can afford for the time being).
