Superhub : unable to access router after installing SuperHub as modem only

[nextenso]

I have Virgin cable broadband using the old ntl modem and a Netgear WGR614v7 router. Last week I upgraded the router to a TP Link WR1042NR router, all was fine accessing the router on 192.168.0.1

Yesterday I installed the SuperHub Virgin sent me using instructions as the 4th article down on http://forums.overclockers.co.uk/sho...php?t=18275743.

As that instructs, I set the TP router IP address in the SuperHub DMZ list to direct all traffic to the router, disabled the Hub firewall and clicked the modem only button.

All internet services work fine with the TP router serving our various machines correctly with excellent wireless speed. BUT, although I can access the Hub on 192.168.100.1, I can no longer access the TP router.

In IPConfig/all I can see the TP router (as Realtek RTL8191SU wireless LAN.....) as 192.168.1.1 and if I query that IP I get the TP login page which correctly identies the name and model number of the router.

BUT, any combinations of logins will only result in the login saying that username & pswd do not match, try again.

I did a hard reset on the TP router , powering it up and waiting 20 or so secs with the rest button is pressed in until after the SYS light comes on. Same result on login.

I tried the press reset and wait 30secs, power off and wait 30 secs, power up with the rest pressed in for 30 sces, then open a new browser page and login in - same result.

I have tried using the different browsers I have after each reset (Safari, IE, Chrome, FFox and Opera) to make sure I was not calling a cached page. Al;ways same result.

All internet services work well, I just can not access the TP router to change config which I need to do, urgently.

I have run out of ideas other than wiping out the TP router install, re-installing the Netgear one, then re-installing the TP router, which stops everyone here accessing their online content once again.

Please does anyone know what else to do.

Rgds Jonathan

---------- Post added at 17:51 ---------- Previous post was at 17:15 ----------

I left out that I have a cable connection to my main computer, which as the online instructions I gave the url for, was in the last stage connected to the TP router.

This main computer also has a wireless dongle to 'speak' to all other machines and smart phones via wireless. All that works fine.

Rgds Jonathan

[General Maximus]

I got half way through your post dude and stopped because you are getting yourself in a pickle. Playing around with the shub setting, assigning ips and putting stuff in the dmz is great when you are using the shub in router mode and want to connect additional routers, but you don't. All you needed to do is put the shub straight into mode and leave your Tp Link router as it was.

You are probably best off starting from scratch again and I would do a pin hold reset on both devices. Put the shub in modem mode and let it restart and its ip address will be 192.168.100.1. Connect the TP Link router to it without changing anything and I assume it will have a default ip of something like 192.168.0.1 which you can go in and change if you want to.

[bonzoe]

I got myself into a pickle this PM trying to connect Shub to my router. Solved it in the end, and you just have to be very logical. General Maximus, I wish I had seen your post before you even posted it That is what I found in the end ( refers to me!)

[nextenso]

Thanks for the post Maximus. I followed the directions from a person who seemed to know what to do and had good speed results afterwards.

Without seeing that, I would have done, and had initially done, what you suggest

I will revert to this forum after trying to see if I can access my TP router again.

Thanks & rgds Jonathan

[nextenso]

A quick note to say that after resetting SHub to factory status and restarting SHub with the TP router disconnected, then re-booting computer with TP router linked to the SHUb got all working ok, but had to re-boot computer twice to get Windows to rebuild the IP addresses and remove conflicts.

Only then did TP router revert back to 192.168.0.1 and allow me access. Prior to that it kept staying on 192.168.1.1 and being inaccessible.

Thanks for the help. Rgds Jonathan