Jump to content
SubSpace Forum Network

Recommended Posts

Posted

Well, trace looks fine. Try calling your ISP and having them check the line (and hope they check it at a moment when it is going bad).

 

I assume you have tried with all other programs off? And downloading programs off too?

Posted

You could try without the router as well, if the possibility exists to connect the internet directly to your computer.

 

Or try it without the other computers for a few hours.

Posted

The trace shows that it isn't a problem with your computer(s) or your router.

The problem is located at a router/switch near the server, something you can't do anything about. I suggest waiting until the problem resolves, there is not alot more you can do.

Posted

Sorry, Mav, that's incorrect.

 

The trace shows that everything is in perfect working order, really.

As I have said several times on this board, the only hop that matters is the last one. And this 1% can be discarded as measurement inaccuracy. So, everything looks fine.

Posted
As I have said several times on this board, the only hop that matters is the last one.

Why so?

A trace is a graph that displays the response time (and packet loss %) per hop, right? If response time and/or packets is longer/gets lost at the X hop, that would show a problem with that hop, correct?

What I see at the trace from ProMemoreX, packets gets lost at the 14th hop which would explain his problem.

 

However its weird the packetloss is gone at the last hop, however what is the reason behind the packetloss at the 14th then? :D

Posted

Crappy routers blum.gif

 

Which is exactly why its not weird that it dissappears at the last hop smile.gif

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Maybe I should explain? Bah, I'm tired. Just take my word for it :D Maybe in the morning... almost midnight here... reply if you still don't get it smile.gif

Posted

No, I meant some other routers were crappy on the net, not yours :D

 

Anyway, what happens is that the router with the big loss gets a ping (=trace) packet. Now, it sees that the ping packet is meant to itself. It figures "WTF? I ain't no host! Stupid annoying kids... this could even be some freaky D®DOS. Psh!" and just drops it. (It actually seems to reply to the packet but only once (that's why its not 100% loss), it ignores any repeated packets)

 

But when it sees that the packet is not meant for itself, it lets it through, which is why hops after the annoying routers are fine.

Guest
This topic is now closed to further replies.
×
×
  • Create New...