Bizarre tracert for router vs modem

SamH · 19-02-2007, 16:39

I have something of a paradox going on here. I have a D-Link 624+ router, to which I connect via patch cable. I use a gaming server to play games. When I'm connected to the router, the tracert is different from when I connect directly to the modem. When connected to the router, one of the hops is dead and as a result I have high pings (35-70ms) and thus an unstable gaming connection. When I connect directly to the modem, I have a solid 16ms connection. All this when there is only MY PC connected.

How the hell am I getting sent a different (DUFF!!) route to the gaming server ONLY when I connect through my router? And how the hell do I get that route fixed?

And also.. how the hell do I get past the monkeys to tell someone with a braincell about the crapped out switch/node so that they can fix it? I know it's within the NTL/TW/VM network because the IP before and after it belong to them.

Also, a quick rant.. I cannot abide being lied to. When I phoned VM to talk about my connectivity issue, I was told that they'd investigated the gaming server and that it was that server that had the connectivity issue. I asked several times, and I was assured that this was the case. Well here's the news.. I OWN that bloody gaming server, and I RDC onto it much of every day, and I KNOW FOR A FACT that the connectivity on the server was fine. It's at Blue Square and it's on a kick-ass, uncontested switch.

So, Virgin Media, get some damn employees that DON'T FRIGGIN LIE!! I was livid! Still AM! I can cope with MANY things, but I cannot bear to be bareface lied at! Next stop YouTube. I feel like ranting.

rikur · 20-02-2007, 17:33

Hi

not quite sure on this one - but I think you will be getting allocated a different IP address depending on whether you connect your PC directly to the modem, or whether you connect the router.

It is therefore conceivable that the route back to your PC from the other end is different depending on which device you connect. To the best of my knowledge routing on ntl:tw's core is only based on destination address and not the source address - hence I couldn't see how you could get different outbound routes.

Is your router also acting as a firewall?
It is possible that your router is adding the latency - I don't know about your particular model, but cheap and/or early models were designed for 512kbps style connections, and don't necessarily have the processing power to transparently handle 10mbps

Given you have access to the host server, it would be interesting to compare tracert's from that end back to your home connection to see if they go completely different routes.