Sabnzbd, Fios connection, disables networking

[sevi]

I have a windows 7 latop, connected to a router - wired, with VZ fios 35 Mbit service. I'm using latest version of sabnzbd. I've been using it for about 6-9 mths. Not a heavy user in general, block service on NewsGroupDirect or something like that. Recently i would be getting good speeds about 3.5 MB/sec and after anywhere from 10 mins to 30 mins later, my speed would slow down to crawl and than zero. My connection would than be totally disabled, i can't surf net or get out. Opening the networking page in windows, i see that red line, disconnect indication basically. Unplug cable and plugged back in, no go. Only option is to reboot than it works. I say 10 to 30 mins, 'cos it seems if i were to start getting files after a few days, it would be longer before the problems start. Once it starts, subsequent tries will becomes shorter for the problem to happen. Can VZ have the ability to disable my network altogether on this particular laptop? I have other machines connected and they are fine.

Thanks in advance.

[shypike]

Does SABnzbd show the same behaviour when you run it on the other systems?

[sander]

If the different machines are on the same LAN, behind one NAT/router/modem, I think it is very unlikely that Verizon can throttle one machine.

First thing to check: can you still ping your router while you have no Internet connectivity? If not, it is a local problem.

[sevi]

1) I haven't tried it on other system, but working on testing on another.

2) No I cannot ping anyone when it finally drops to zero. It actually disables my network adapter it looks like. And I'm saying that 'cos under control panel, the networking section, it basically is in red as far as connectivity to anywhere.

[sander]

2) No I cannot ping anyone when it finally drops to zero. It actually disables my network adapter it looks like. And I'm saying that 'cos under control panel, the networking section, it basically is in red as far as connectivity to anywhere.

So you can't ping your router during an outage? Then I would say it's a local networking thing, nothing to do with Verizon.

Wireless connections can be buggy and can loose connectivity if you download a lot, but AFAIK this is very unusual for wired connections (which you use, right?). For a try, you could update the firmware of your modem/router and update the network driver for your ethernet device on your Windows system.

[sevi]

Yes I am using a wired connection.

Ok I will try those updates and test. Thanks for the tip!

[sevi]

So i've been trying a few things all not going anywhere.

1) Updated NIC driver on laptop --- still disconnects
2) Was not going direct to VZ provided router at first, changed that, now I'm going direct from laptop to VZ provided router/modem -- still disconnects
3) VZ router --- no update on firmware so i'm updated already
4) Changed my server from EU to US location, tracre route shows better response time with US server -- still disconnects
5) I did a trace collect can't really see anything, just all of sudden, I get the errors of messages asking who 'IP of my laptop is', it's like it's unable to resolve, then i know it's totally down.


Also, when I get disconnected, my other machines are NOT able to surf and go outside as well so i'm totally down at home.

[sander]

Also, when I get disconnected, my other machines are NOT able to surf and go outside as well so i'm totally down at home.

So that means it has nothing to do with SABnzbd nor your machine; it is a network thing. It might a DNS problem, and that's easy to detect.

You said you could not ping your router anymore during an outage. Can you post the exact command you use, including the output?

And, can you "ping 8.8.8.8" both at normal network functionality and during outage?

[sevi]

Here are the outputs after I loose connectivity:

C:>ping 192.168.1.1

Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.X: Destination host unreachable.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),

C:\>ping 8.8.8.8

Pinging 8.8.8.8 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.1.X: Destination host unreachable.

Ping statistics for 8.8.8.8:
Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),

C:\>ping www.yahoo.com
Ping request could not find host www.yahoo.com. Please check the name and try ag
ain.

I don't think it's my machine or sabnzbd, but i'm wondering if it's the router or VZ.

[sevi]

This is when connectivity is back on.

C:\>ping 8.8.8.8

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=59ms TTL=53
Reply from 8.8.8.8: bytes=32 time=57ms TTL=53
Reply from 8.8.8.8: bytes=32 time=58ms TTL=53
Reply from 8.8.8.8: bytes=32 time=57ms TTL=53

Ping statistics for 8.8.8.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 57ms, Maximum = 59ms, Average = 57ms

[sander]

And what is the output of "ping 192.168.1.1" when connectivity is OK? Please leave in the IP addresses (they are LAN-only, so no worries about privacy).

[sevi]

When connectivity is ok

C:\>ping 192.168.1.1

Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=50ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 50ms, Average = 13ms


So what are you thinking so far?

[sander]

When connectivity is ok

C:\>ping 192.168.1.1

Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=50ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 50ms, Average = 13ms


So what are you thinking so far?

Well, if you can ping your router normally, and you cannot ping it during an outage, the problem is on your local network (not Verizon, not Internet, not SABnzbd, not DNS).
If the other PCs on your LAN show the same problem, it is a central problem, so your router/modem/switch.
If the other PCs do not show the same problem, it is a problem with your PC or its ethernet cable.

[sevi]

got it, I'll see if I can switch out my router with VZ. Hey, really appreciate the time/effort and help in this!!

[sevi]

some update with maybe new symptoms ..

1) Replaced router
2) Connected laptop with old lan cable -- still disconnects
3) Connected laptop with new lan cable that came with router from VZ -- still disconnects
4) Decided to configure another machine with sabnzbd - difference in machine laptop win 7 pro (64bit) vs iMac booted into win 7 home (32bit) patition.