Cable Forum - View Single Post

nigelpt · 25-09-2013, 11:42

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!

25-09-2013, 11:42	#1
nigelpt Inactive Join Date: Sep 2013 Posts: 3	Cannot access home server 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!