Superhub : Confused - not difficult I know :(

[5quirrel]

Hello,

I have an unusual problem that has started to happen over the last week. I do not seem to be able to connect to a few servers that I did last week and I was wondering if anyone could shed any light on this.

The two main servers that I could access last week but not this week are:

pop.ivao.aero (78.47.116.210)
gb.forum.ivao.aero (213.239.201.245)

I get timed out when I ping these two but never had a problem before last week. If I traceroute, the ICMP packets are blocked, which is fine, but if I ping from a browser everything is fine.

If I use a proxy in IE then I can access the forum pages, but using my virgin IP this too times out.

Where should I start troubleshooting from?

Regards,

[Qtx]

No ICMP packets blocked on any part of the route when I traceroute to both of those ip addresses on a VM connection. Full traceroute shows for both. Both give ping replies.

So I would guess a VM routing problem but localised to a specific are/segment of their network. A lot of these seem to be popping up lately for VM customers, where certain areas can't access particular sites.

All you can do is report it to VM and supply your traceroute as far as I know.

[craigj2k12]

Are you using a superhub? And are you in router mode or modem mode?

[Sephiroth]

No problem accessing those address here in browser.

[5quirrel]

Thanks guys, I am using a superhub in router mode. Last week I could access the pop server but suddenly I cannot. Also last week I could browse the forum, but not this week (unless I use a proxy, then I can browse without a problem).

Interesting that Qtc can TR to the server as their sys admin says he cannot himself as their firewall block icmp (?)

I guess asking VM for help is going to be my only option but I will not hold my breath...

Is there a simple way to change IP on my superhub to see it it is a specific IP block on those servers?

Thanks,

[Sephiroth]

I'd have thought quickly trying in modem mode (which gives you a different IP) would be a sensible move.

[5quirrel]

Very sensible to the point of it working perfectly in modem mode However I need to run in router mode coz of all the devices I have. Is there a way to sort the superhub routing out or is it looking like a blocked IP at the server end?

Many thanks so far!

[Sephiroth]

The point about trying modem mode was to see if the problem of accessing the pop server went away.

There would be no blocked IP at either end. It's possibly a DNS issue which can be a pig to sort out except in modem mode when you can choose your own DNS in the separate router.

You could try and enter the IP and host name into the HOSTS file of your system and force the route that way.

The chances of the routing issues being resolved with the Superhub are slim to none. Buy a cheap router and leave the SH in modem mode. If you search the forum for Superhub posts you'll get an idea.

[5quirrel]

I used to have another wifi router in place but thought the SH would do all in one. Is the SH really that flakey. It's a shame it looks like two boxes will be needed

Great advice guys, I am glad I posted here!

---------- Post added at 00:13 ---------- Previous post was at 00:09 ----------

Oh would you believe it. Just checked again and I've lost the forum and cannot reach the pop server again. This was working until I went to watch TV for an hour, now it's all broken again - even more confused now...

[5quirrel]

Then this morning all is fine again in modem mode. Very odd.

[qasdfdsaq]

Probably affected by the fibre break in London last night.

Some idiots dug through about 800 fibre-optic cables leading to the Telehouse exchange. At least *some* routes to those sites go through Telehouse