Superhub : Cannot access home server

[nigelpt]

I have a strange problem and suspect that others might have encountered it too.

For years I have been running a simple cable modem which is on the ground floor of my house.

A CAT5 cable feeds up to the second floor into a Cisco wireless router running DD-WRT.

The router provides a good coverage for WiFi services, and an Ethernet cable connects the router to a 20 way Netgear gigabit switch. This switch then supports the wired connections in this office, including a web server – which is hiding in the router's DMZ.

The Problem: I have been upgraded to the new Virgin Superhub and this is set to 'modem' mode. Everything works extremely well, but for one thing – I cannot see my server when trying to call it from a browser. All attempts to call by the external IP address or assigned DynDNS URL fails totally. However, I can see it if I use Tor and call it from elsewhere in the World.

I suspect the issue lies with the fact that the 'modem' has its own IP address [192.168.100.1] and is wondering why I'm trying to call myself!

Has anyone had this experience and can they offer any guidance please?

Many thanks for reading this!

Cheers!

[qasdfdsaq]

If you're still using the same router then there should be no difference. Your previous 'modem' also had its own, same, identical IP address. The "calling yourself" happens at the router, not the modem. Again, in theory it should work identically to what you had before.

Have you made any changes at the router?

[nigelpt]

No, I made no changes at all, just 'plugged and played', so to speak.

I did have to engage the services of a very patient and helpful chap at Virgin, who had to change some parameters in the modem remotely before we could access the outside World, but other than that, nothing.

My earlier modem was just a plain cable modem with no in-built intelligence and didn't have an internal IP as far as I am aware. There was no in-built GUI for it was about 10 years old.

I was originally a Cambridge Cable customer, who were taken over by NTL and now Virgin, so it was very old tech.

[Kushan]

Originally Posted by nigelpt

No, I made no changes at all, just 'plugged and played', so to speak.

I did have to engage the services of a very patient and helpful chap at Virgin, who had to change some parameters in the modem remotely before we could access the outside World, but other than that, nothing.

My earlier modem was just a plain cable modem with no in-built intelligence and didn't have an internal IP as far as I am aware. There was no in-built GUI for it was about 10 years old.

I was originally a Cambridge Cable customer, who were taken over by NTL and now Virgin, so it was very old tech.

All cable modems have their own IP address and usually a web interface to list stats. 192.168.100.1.

If you disconnect the superhub, you should be able to access your server internally. If you can't, then the issue has nothing to do with the SHUB. If you can, connect the hub back up and then see if you can access it internally - if you can't then you may well be on to something (worth checking the hub is actually IN modem mode). Now, once you've got internal access sorted, time to work on external.

Your IP address will have changed. Double check your DynDNS service has updated correctly and is pointing towards the right address.

[nigelpt]

Many thanks for the excellent guidance chaps - much appreciated.

Also the heads-up re the modem IP. I will fire up the old one to see what I missed!

Given the points raised, I revisited the internal Cisco router and discovered a strange setting that had changed [?] I will have to look further into what was the cause of that, but I am pleased to report that I can now see the web server in the conventional manner.

Many thanks again qasdfdsaq and Kushan for sharing your wisdom!

[Kushan]

You're most welcome, glad you got it sorted!