Moving flats or: switching your router to a new TCL connection

Forums › LAN (ethernet/Wifi/routers/Bluetooth) › Moving flats or: switching your router to a new TCL connection

1 | 2

duckInferno

89 posts

Master Geek
+1 received by user: 21

#421907 27-Dec-2010 18:12

Mind if I crosslink to the LAN forum? Since it likely isn't a TCL issue anymore.

freitasm

BDFL - Memuneh
80646 posts

Uber Geek
+1 received by user: 41030

Administrator

ID Verified

Trusted

Geekzone

Lifetime subscriber

#421926 27-Dec-2010 19:06

121.x.x.x? I didn't know this was a TelstraClear cable range. I always thought it was 203.x.x.x.

Also, netmask should be 255.255.255.0 as pointed. Gateway the same IP but x.x.x.1.

And DNS should be 203.97.78.43 and 203.97.78.44. Those are the Clearnet servers, don't use the Paradise ones.

By any chance did you plug your laptop before plugging the router, then switched with the router (which didn't work) then switched back to the laptop?

Referral links: Quic Broadband (free setup code: R587125ERQ6VE) | Samsung | AliExpress | Wise | Sharesies

Support Geekzone by subscribing (browse ads-free), or making a one-off or recurring donation through PressPatron.

sbiddle

30853 posts

Uber Geek
+1 received by user: 9996

Retired Mod

Trusted

Biddle Corp

Lifetime subscriber

#421934 27-Dec-2010 19:17

freitasm: 121.x.x.x? I didn't know this was a TelstraClear cable range. I always thought it was 203.x.x.x.

Most cable IP's in the last few years have all been 121.xxx.xxx.xxx

cyril7

9073 posts

Uber Geek
+1 received by user: 2499

ID Verified

Trusted

Subscriber

#421959 27-Dec-2010 20:59

And DNS should be 203.97.78.43 and 203.97.78.44. Those are the Clearnet servers, don't use the Paradise ones.

Interesting, I have dealt with router installs on several new connections recently and the cable installer left the paradise DNS server IPs.

Cyril

duckInferno

89 posts

Master Geek
+1 received by user: 21

#421964 27-Dec-2010 21:04

freitasm: 121.x.x.x? I didn't know this was a TelstraClear cable range. I always thought it was 203.x.x.x.

Also, netmask should be 255.255.255.0 as pointed. Gateway the same IP but x.x.x.1.

And DNS should be 203.97.78.43 and 203.97.78.44. Those are the Clearnet servers, don't use the Paradise ones.

By any chance did you plug your laptop before plugging the router, then switched with the router (which didn't work) then switched back to the laptop?

Yeah I was a bit thrown off when I first learned our IP, too. Gateway and subnet are "corrected" and correct, respectively. I use the clearnet DNS servers but have been swapping back and forth to paradise in my attempts.

The first thing to get plugged into the router is the modem. My PC followed. My laptop was a late third, it's now dispensing temporary wireless to my flat while I get this sorted. My laptop and PC are identical in terms of functionality in this situation (both work with the modem directly, both can share it to the flat over a virtual wireless access point, neither can connect to the net through the router, etc).

Just worked with a networking friend of mine who also was stumped, though we did managed to glean something new: I can't ping the modem when it's connected to the router (192.168.100.1). I am able to ping it when the modem is directly plugged in to the PC/laptop.

This DD-WRT firmware has a command prompt, but it's web based and seems buggy... I was able to perform a test ping through the firmware to 192.169.0.1 which returned successful results, then it stopped working entirely... it won't return any results on pinging anything anymore, let alone the modem. Even through a router restart. >:(

Still, it's another avenue of investigation.

Finally, a trace route to a DNS server:

C:\Users\Tom>tracert 203.96.152.4
Tracing route to 203.96.152.4 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms DD-WRT [192.168.1.1]
2 (my ip address) reports: Destination host unreachable.
Trace complete.

My network buddy thought this was very odd. Maybe you will too.

duckInferno

89 posts

Master Geek
+1 received by user: 21

#422136 28-Dec-2010 15:21

Had a mostly uninteresting chat with linksys live support.

from Ivy (11486) to All Participants:
You cannot ping the modem or any external IP as long as the router was not configured yet.

from Tom Norman to All Participants:
okay, that's promising

so if I can ping the modem from the PC it's plugged into at the moment -- and external IP's -- and access the net, that proves it's all working there.

but if I can't ping the modem when it's plugged into the router, that proves the settings are not correct in the router. is that what you're saying? just to be sure

from Ivy (11486) to All Participants:
If the PC is directly connected to the modem, you should be able to get online.
Yes, you got it right.

She seemed to know her stuff otherwise so I don't think she pulled that out of her arse.

Dell

Shop now for Dell laptops and other devices (affiliate link).

antoniosk

2382 posts

Uber Geek
+1 received by user: 742

ID Verified

Trusted

Lifetime subscriber

#422140 28-Dec-2010 15:31

duckInferno: Had a mostly uninteresting chat with linksys live support.
from Ivy (11486) to All Participants:
You cannot ping the modem or any external IP as long as the router was not configured yet.

from Tom Norman to All Participants:
okay, that's promising

so if I can ping the modem from the PC it's plugged into at the moment -- and external IP's -- and access the net, that proves it's all working there.

but if I can't ping the modem when it's plugged into the router, that proves the settings are not correct in the router. is that what you're saying? just to be sure

from Ivy (11486) to All Participants:
If the PC is directly connected to the modem, you should be able to get online.
Yes, you got it right.

She seemed to know her stuff otherwise so I don't think she pulled that out of her arse.

So:

You were on TCL cable with you router, which is setup just the way you like it and has the right access settings etc.

You've changed to a new TCL cable location, but nothing in your router has been changed?

I'm just wondering if your router has some setting or parameter somewhere that is preventing you from getting access.

SO have you blown away the router's settings to factory....? I know it's extreme and shouldn't be required... but should/shouldn't is an overabused word in the ICT world....

________

Antoniosk

duckInferno

89 posts

Master Geek
+1 received by user: 21

#422151 28-Dec-2010 16:15

Yeah. Factory reset, firmware upgrade, new firmware (DD-whateveritwas), back to linksys firmware, another factory reset...

Atm I'm waiting on the head tenant to add me to the list of trusted folk for the TCL account. Maybe I can get more out of them than "we don't support routers".

duckInferno

89 posts

Master Geek
+1 received by user: 21

#423000 31-Dec-2010 15:48

Confirmed with TCL that I'm using the correct IP/Subnet/Gateway/DNS servers, but I pretty much knew that already.

So, yeah. Dead end. :(

On a (possibly related) issue, my connection is damaged in some way. It has 4-8% packet loss and TCL have scheduled a techy to come and look at it, they say that the connection died 330 times in the last 24 hours :X. Explains why the previous router was trippy, I hope, but I wonder how much of a problem that'd cause the new one.

At this point, however, the most likely issue is that it's borked. Sigh!

antoniosk

2382 posts

Uber Geek
+1 received by user: 742

ID Verified

Trusted

Lifetime subscriber

#423034 31-Dec-2010 17:09

duckInferno: Confirmed with TCL that I'm using the correct IP/Subnet/Gateway/DNS servers, but I pretty much knew that already.

So, yeah. Dead end. :(

On a (possibly related) issue, my connection is damaged in some way. It has 4-8% packet loss and TCL have scheduled a techy to come and look at it, they say that the connection died 330 times in the last 24 hours :X. Explains why the previous router was trippy, I hope, but I wonder how much of a problem that'd cause the new one.

At this point, however, the most likely issue is that it's borked. Sigh!

Bizarre, but if it's going to be repaired things can only get better... but that wouldn't explain why your router isn't able to connect to the cable modem in bridge mode and act as a gateway.

________

Antoniosk

duckInferno

89 posts

Master Geek
+1 received by user: 21

#423433 2-Jan-2011 16:59

It works! And guess what I did:

NOTHING.

Well... not entirely true. I was using my laptop as a temporary gateway, which meant I had to replace the short ethernet cable between the router and the modem with something longer so it could reach into my room. I moved the router in here (unplugged), figuring it'd be easier to plug/unplug stuff when I get around to tinkering with it more.

So, it's been like 3 days since I did anything. Moved the modem's ethernet cable from my laptop to the router. Connected to the router wirelessly and brought up its admin page. Www.google.com just to verify it's still broken.

The page loads.

Double you tee eff, mate. So, I figured it was the short cable... but I'd already tested it, it was one of the first things I did. So I disconnected wireless, and connected the computer to the router via the short cable... and it works fine, so it's not that. I did absolutely nothing to warrant this turnabout.

Not complaining though! :D I'm just damn glad it's working... I loved this router to the very line between intense like and sexual desire of an inanimate object, and am exceptionally poor at the moment. Thanks for all the help in the thread!

Geekzone

Want to support Geekzone and browse the site without the ads? Subscribe to Geekzone now (monthly, annual and lifetime options).

sbiddle

30853 posts

Uber Geek
+1 received by user: 9996

Retired Mod

Trusted

Biddle Corp

Lifetime subscriber

#423436 2-Jan-2011 17:10

Definately sounds like an ARP caching issue then.

1 | 2