Problem with router log in (update)

[Tim+]

I mentioned a few weeks ago that I was having problems logging into my
mother’s router. The normal correct 192.168.1.1 address just wouldn’t work.
I needed to be able to log in as my mother’s ISP was going to change.

Service moved today and I managed to get my mum back on line using an older
router- modem. The change over was delayed by a month because TalkTalk
screwed up the records and openreach couldn’t identify which line was my
mother’s.

Finally managed to get the “new” router home today and determined using my
iPad that the router address was now 192.168.1.102. Unfortunately, even
using this address my iPad couldn’t connect or access the router log in.

Anyhoo, one hard reset later and connected to my wife’s laptop, it’s all
sorted and behaving again.

The new ISP is IDNET and I have to say I’m really impressed by their
customer support. Emails answered within 24 hrs and phone calls answered
quickly by helpful people. A breath of fresh air after all the hassle with
TalkTalk!

Tim


--
Please don't feed the trolls

[Roderick Stewart]

192.168.1.102 doesn't look like a router address to me. It looks like
an address given out to a connected device by a DHCP server in a
router with a range starting at 100.

Routers typically have addresses lile 192.168.1.1 or 192.168.1.254 and
will automatically hand out other local addresses to devices that
connect to them. These other addresses must not clash with the
router's own address so will often start at 192.168.1.2, though it's
possible to configure them to begin at some higher number so you can
allocate lower ones as static addresses if you want to. Sometimes
they're set up this way by default. I've seen DHCP ranges set up by
default to begin at 64, 100 and 200, which would suit most domestic
usage, though you can set them yourself to anything you like. It looks
as though yours has been set to 100, so connected devices will be
given addresses of 100 upwards.

In the response to an "ipconfig" command from a computer (I don't know
how you would do this from an iPad because I've never had one, though
there's probably a way) the router will be shown as "default gateway"
and will almost certainly have an address ending in 1 or 254. An
address of 102 will be the address of the iPad.

Rod.

[Graham J]

Roderick Stewart wrote:
[snip]

I've already told him how to use his iPad to show this information, see
my post of 16/12/2020 20:53 where I wrote:

"
Look in in Settings - WiFi and you should see the network name (SSID).
Tap the information icon - it should show Configuration is automatic,
the IP address, subnet mask and router IP address.

Knowing the router's IP address open a browser at that address and see
if you get a login prompt.
"

I suspect he has simply misunderstood this, so I'm dubious about
offering any more help ...


--
Graham J

[Tim+]

Nope, I followed these instructions and I’m almost certain that the router
address was the one I gave.

Anyhow, the hard reset has fixed it now. I just couldn’t do that before as
I had no computer with me at my mother’s flat.

[Roderick Stewart]

On 8 Jan 2021 14:05:54 GMT, Tim+ <tim.d...@gmail.com> wrote:

>> I suspect he has simply misunderstood this, so I'm dubious about
>> offering any more help ...
>
>Nope, I followed these instructions and I’m almost certain that the router
>address was the one I gave.

I'm almost certain you are mistaken. I've never seen a router with a
default address of 192.168.1.102 but it's very common for such an
address to be given to a device connected to one.

Rod.

[Andy Burns]

Roderick Stewart wrote:

> Tim+ wrote:
>
>> I’m almost certain that the router address was the one I gave.
>
> I'm almost certain you are mistaken. I've never seen a router with a
> default address of 192.168.1.102

FWLIW, me neither.

[NY]

"Andy Burns" <use...@andyburns.uk> wrote in message
news:i5tcda...@mid.individual.net...

The gateway address can be set *manually* to any address in the same subnet
that DHCP uses, though you might have fun trying to exclude it from the
scope (range) of addresses that DHCP hands out.

I've never seen a router that is factory-configured to use any gateway
address other than 129.168.x.1 or 192.168.x.25y (ie at the very bottom or
close to the top of the subnet). I've seen a few with unusual values of x
(the third byte) - my dad's first router was factory-configured to gateway
and DHCP of 192.168.7.y

So if the OP is certain that the gateway address (and not the computer which
was trying to connect the the router's web interface) was 192.168.1.102,
then it has *probably* been manually configured that way.

We'll never know, since it's now been reset to factory state. I presume its
gateway address is now 192.168.x.1 or .254, and is no longer .102.

[Invalid]

In message <dluivfheem9f8ed7s...@4ax.com>, Roderick
Stewart <rj...@escapetime.myzen.co.uk> writes

My router lives at 10.0.0.10. However it has been manually configured to
that. My routers have lived at that address for close on 20 year and the
reason is now lost in the mists of my memory.

I wonder of the OP's mothers router was truly "new", or had she been
sent a recycled unit that someone had manually configured?
--
Invalid

[Roderick Stewart]

On Sat, 9 Jan 2021 11:42:19 -0000, "NY" <m...@privacy.invalid> wrote:

>I've seen a few with unusual values of x
>(the third byte) - my dad's first router was factory-configured to gateway
>and DHCP of 192.168.7.y

Belkin perchance? They sometimes choose different numbers from the
usual ones (probably just for the sake of being different).

Rod.

[NY]

"Roderick Stewart" <rj...@escapetime.myzen.co.uk> wrote in message
news:8jplvf5pfdhend7ra...@4ax.com...

It wasn't Belkin. It was a manufacturer I've never heard of before or since.
I'm not sure why he chose that make. It might have been what PlusNet (as
Force9 in those days) was supplying with its broadband contract at the time.