From Newsgroup: alt.internet.wireless

NY wrote:

This may be a silly question...

You've got the router that your are trying to configure on the same LAN
as the the PC that you are trying to access. But have you removed the
router that you normally use to access the internet? It is an error to
have two DHCP servers (test router and normal router) on the same LAN.

If you've not already done this, try it and check that ipconfig gets an
IP address of the form 192.168.1.x and a gateway of 192.168.1.1 - I'm wondering whether the ip config details you are seeing have been
allocated by your "real" router.

Maybe make up a test LAN with your PC connected to the test router, bypassing the real router altogether (and turn off wifi on the PC - I
notice that ipconfig is listing both Ethernet and wifi with different
IPs which *may* be an inadvisable setup).

Apologies if this has been suggested as I only skimmed the answers so far.

As far as I know, you do not need to "log into" the router to test connectivity, since you can ping it instead (which is a simpler protocol).

Like everyone here, I've set up a billion routers, where, IMHO, the safest
way is to connect it DIRECTLY to the PC by the RJ45 Ethernet cable.

1. You manually set your PC to be on your subnet, e.g., 192.168.1.2
2. You connect the RJ45 PC output to a router LAN (not WAN!) port
3. You should be able to pint the router from the pc
c:\> ping 192.168.1.1

Once you can ping it, you've at least established it's communicating.
Then you can worry about http vs https and password casing, etc.

You can do this if you only have Wi-Fi on your pc too, but it's not
as direct since the wired connection is a far simpler connectivity.
--- Synchronet 3.21f-Linux NewsLink 1.2

From Newsgroup: alt.internet.wireless

Maria Sophia wrote on 4/23/2026 2:38 PM:

NY wrote:

This may be a silly question...

You've got the router that your are trying to configure on the same LAN
as the the PC that you are trying to access. But have you removed the
router that you normally use to access the internet? It is an error to
have two DHCP servers (test router and normal router) on the same LAN.

If you've not already done this, try it and check that ipconfig gets an
IP address of the form 192.168.1.x and a gateway of 192.168.1.1 - I'm
wondering whether the ip config details you are seeing have been
allocated by your "real" router.

Maybe make up a test LAN with your PC connected to the test router,
bypassing the real router altogether (and turn off wifi on the PC - I
notice that ipconfig is listing both Ethernet and wifi with different
IPs which *may* be an inadvisable setup).

Apologies if this has been suggested as I only skimmed the answers so far.

As far as I know, you do not need to "log into" the router to test connectivity, since you can ping it instead (which is a simpler protocol).

Like everyone here, I've set up a billion routers, where, IMHO, the safest way is to connect it DIRECTLY to the PC by the RJ45 Ethernet cable.

1. You manually set your PC to be on your subnet, e.g., 192.168.1.2
2. You connect the RJ45 PC output to a router LAN (not WAN!) port
3. You should be able to pint the router from the pc
c:\> ping 192.168.1.1

Once you can ping it, you've at least established it's communicating.
Then you can worry about http vs https and password casing, etc.

You can do this if you only have Wi-Fi on your pc too, but it's not
as direct since the wired connection is a far simpler connectivity.

Thanks Mary. I think this thread needs a full blown Tutorial to solve
the problem in depth.


--- Synchronet 3.21f-Linux NewsLink 1.2