Past several mornings now I've woken to find my Internet cable connection dead. Turns out it's the router. The router is totally locked up - can't even log into it to get into the admin controls or even ping it. Power cycling the router resets it.
It seems that DC++ is causing the problem - it only happens when I leave DC++ running overnight. Never had this problem before though. I have a spare router and I'm going to try swapping it out and see if that helps.
But why the heck would DC++ lockup the router? Nothing's changed - I'm just using port forwarding to forward port 412 to my dedicated DC system's IP.
Strange.
Then again I still get that bizarre "Your IP is already connected to this Hub 5 times" error once in a while to and then I can't get on the hub for a day.
Strange problem with DC++ client - keep losing my entire internet connection...
- FlyingPenguin
- Flightless Bird
- Posts: 33162
- Joined: Wed Nov 22, 2000 11:13 am
- Location: Central Florida
- Contact:
Strange problem with DC++ client - keep losing my entire internet connection...
---
“The Government of Spain will not applaud those who set the world on fire just because they show up with a bucket.” - Prime Minister of Spain, Pedro Sánchez

“The Government of Spain will not applaud those who set the world on fire just because they show up with a bucket.” - Prime Minister of Spain, Pedro Sánchez

-
Absolut Talent
- Almighty Member
- Posts: 2868
- Joined: Mon Jan 07, 2002 12:30 pm
is it a belkin router?
I had the exact same problem with mine. When I used to use DC it would drop my connection overnight. Even if I pinged servers in ANY halflife mod, it would drop (but other games, ie desert combat would ping alright)
Ditched the belkin router and got a linksys and never had any problems
I had the exact same problem with mine. When I used to use DC it would drop my connection overnight. Even if I pinged servers in ANY halflife mod, it would drop (but other games, ie desert combat would ping alright)
Ditched the belkin router and got a linksys and never had any problems
Gone for good. But never say never
- FlyingPenguin
- Flightless Bird
- Posts: 33162
- Joined: Wed Nov 22, 2000 11:13 am
- Location: Central Florida
- Contact:
- DoPeY5007
- Almighty Member
- Posts: 4259
- Joined: Fri Dec 27, 2002 5:50 pm
- Location: Moved to the hood, a few blocks from USC
- Contact:
I have / Had the same issue when I use a BT client, it would kill my net after just letting it run for a few min, sometimes it would go a hour or more, but often it would kill the cable line with in minutes.
I have a NexLand router, it wouldnt kill the router, just the cable ( note the DSL on the Linksys to the Nexland would remain on )
I have a NexLand router, it wouldnt kill the router, just the cable ( note the DSL on the Linksys to the Nexland would remain on )
- FlyingPenguin
- Flightless Bird
- Posts: 33162
- Joined: Wed Nov 22, 2000 11:13 am
- Location: Central Florida
- Contact:
Well I made an adjustment and it's behaving so far. Can't see why it would make a difference. I was originally forwarding ports 411 & 412 when all I needed was 412.
Let's see if it continues to behave.
Let's see if it continues to behave.
---
“The Government of Spain will not applaud those who set the world on fire just because they show up with a bucket.” - Prime Minister of Spain, Pedro Sánchez

“The Government of Spain will not applaud those who set the world on fire just because they show up with a bucket.” - Prime Minister of Spain, Pedro Sánchez


