192.168.1.100 — What This Address Is & How to Log In

What is 192.168.1.100?

192.168.1.100 is a private IPv4 address inside the most common home range, 192.168.1.x. The gateway on these networks is 192.168.1.1, so .100 is a host address, not the router. It appears constantly because many routers start their DHCP pool at 192.168.1.100 — making it the first address handed to a connected device — and because it's the go-to example IP in port-forwarding tutorials. Like all RFC 1918 addresses, it's only reachable from inside your own network.

What 192.168.1.100 usually turns out to be

Because the role varies, the first job is to find out which of these your 192.168.1.100 is before expecting a particular screen.

How to identify and log in to 192.168.1.100 — step by step

1. Open a browser and type http://192.168.1.100 in the address bar, not the search box. Use http://, not https.
2. If a login page appears, 192.168.1.100 is a camera, NAS, printer, or similar. Enter that device's admin credentials — check its label or manual, commonly admin / admin or admin with a blank password.
3. If nothing loads, 192.168.1.100 is almost certainly a regular client device (a PC, console, or phone) with no admin page — nothing to log in to.
4. If you actually want the router, open http://192.168.1.1 instead — that's the gateway on a 192.168.1.x network.

Why port forwarding keeps pointing at 192.168.1.100

If you arrived here from a gaming or server setup, that's no accident: port-forwarding guides routinely use 192.168.1.100 as the example internal IP. Forwarding only works if it points at a device whose address doesn't change, so the standard advice is to give your console, PC, or server a static IP — or better, a DHCP reservation — at 192.168.1.100 (or whatever address you choose). The reservation keeps the device on that IP through reboots so the forwarding rule never breaks.

"192.168.1.100 not working" — what to check

• Nothing loads: It's likely a client device, not an admin device. Use 192.168.1.1 for the router.
• The address moved: Without a reservation, DHCP can reassign .100 to another device after a reboot. Check the router's connected-device list.
• Use http, not https: Most device admin pages are served over plain HTTP; an HTTPS redirect will fail.
• Wrong subnet: If your device isn't on 192.168.1.x, your network may use 192.168.0.x instead — the router would be 192.168.0.1.
• Port forwarding still failing: Confirm the device actually holds 192.168.1.100 and that your ISP isn't using CGNAT, which blocks inbound connections regardless of your rules.

How to find your real gateway address

If you're unsure which address your router uses, check your device's default gateway: on Windows run ipconfig and read the "Default Gateway" line; on macOS open System Settings → Network → Details → TCP/IP; on a phone, view the Wi-Fi network details. Full walkthrough: how to find your router's IP address. Once you're into the right admin page, run a speed test to confirm your connection is performing as expected.