192.168.100.170 router login

To open the admin panel, type 192.168.100.170 into your browser's address bar. If the page does not load, this is probably not the gateway address on your network — see the checks below.

192.168.100.170 router passwords

Where to find them:

  • The label on the underside or back of the router — most manufacturers print the default admin username, password and Wi-Fi key there.
  • The quick-start card or manual that came in the box.
  • Your ISP's account portal, if the device was supplied by them — many set a unique password per line rather than a shared default.

No default username and password is recorded for 192.168.100.170. Treat that as final rather than as an invitation to work through lists of common pairs, which are ineffective against most current equipment and frequently trigger lockouts.

If the device on this address has an administration page, the credentials it shipped with will be printed on the hardware — commonly on a label on the base or the back — or set out in the manual for that model. Where an internet provider supplied the equipment, its own support documentation is the right reference.

How to log in to your router

  1. Type 192.168.100.170 into your browser's address bar and press Enter. Type it by hand rather than accepting an autocomplete suggestion, which often fills in a different address you visited before.

  2. If the browser reports that it cannot reach 192.168.100.170, this is not the gateway address on your network. On Windows run ipconfig /all and read the Default Gateway line; on macOS open System Settings, Network, Details, TCP/IP; on Linux run ip route and read the address after "default via".

  3. If the login page loads but rejects your credentials, and you have never changed them, use the defaults printed on the device's label. If they have been changed and nobody knows the new password, a factory reset is the only way back in.

If you do not know the password

Before resetting anything, rule out the simple explanations: a stale DHCP lease, a device that has since moved to another address, or a browser insisting on HTTPS against a plain HTTP panel.

If access really is lost, remember what a factory reset costs. It removes saved wireless credentials, user accounts, schedules and any pairing the device had with an app or hub, and re-adding it usually means going through initial setup again. Follow the reset instructions published for that specific model rather than a general recipe.

Host 170 of 192.168.100.0/24 — a subnet whose usable addresses run from 192.168.100.1 to 192.168.100.254 and whose broadcast address is 192.168.100.255. High final octets like this one usually fall at the tail end of a DHCP range, so the address tends to belong to a device that joined the network relatively late or that takes a fresh lease each time it reconnects. No vendor is known to ship it as a default gateway.

The block containing it, 192.168.0.0/16, has a 255.255.0.0 netmask and 65,536 addresses. It is the consumer block: nearly every home router, mobile hotspot and small office access point ships a default gateway inside it, which is why it is the range most people encounter. RFC 1918 space is unallocated private space that anyone may reuse, so a lookup of 192.168.100.170 cannot return an operator, a subscriber or a country.

The practical question is what holds it right now. A router's DHCP or connected-clients page will map it to a MAC address and usually a hostname, and an ARP query from a machine on the same segment does the same locally. If it does not respond, the lease may simply have expired. All 254 host positions in this /24 are documented.

Block192.168.0.0/16
Netmask255.255.0.0
Subnet192.168.100.0/24
Usable192.168.100.1 – 192.168.100.254

Whois information for 192.168.0.0/16

#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/resources/registry/whois/tou/
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/
#
# Copyright 1997-2024, American Registry for Internet Numbers, Ltd.
#


NetRange: 192.168.0.0 - 192.168.255.255
CIDR: 192.168.0.0/16
NetName: PRIVATE-ADDRESS-CBLK-RFC1918-IANA-RESERVED
NetHandle: NET-192-168-0-0-1
Parent: NET192 (NET-192-0-0-0-0)
NetType: IANA Special Use
OriginAS:
Organization: Internet Assigned Numbers Authority (IANA)
RegDate: 1994-03-15
Updated: 2013-08-30
Comment: These addresses are in use by many millions of independently operated networks, which might be as small as a single computer connected to a home gateway, and are automatically configured in hundreds of millions of devices. They are only intended for use within a private context and traffic that needs to cross the Internet will need to use a different, unique address.
Comment:
Comment: These addresses can be used by anyone without any need to coordinate with IANA or an Internet registry. The traffic from these addresses does not come from ICANN or IANA. We are not the source of activity you may see on logs or in e-mail records. Please refer to http://www.iana.org/abuse/answers
Comment:
Comment: These addresses were assigned by the IETF, the organization that develops Internet protocols, in the Best Current Practice document, RFC 1918 which can be found at:
Comment: http://datatracker.ietf.org/doc/rfc1918
Ref: https://rdap.arin.net/registry/ip/192.168.0.0



OrgName: Internet Assigned Numbers Authority
OrgId: IANA
Address: 12025 Waterfront Drive
Address: Suite 300
City: Los Angeles
StateProv: CA
PostalCode: 90094
Country: US
RegDate:
Updated: 2012-08-31
Ref: https://rdap.arin.net/registry/entity/IANA


OrgAbuseHandle: IANA-IP-ARIN
OrgAbuseName: ICANN
OrgAbusePhone: +1-310-301-5820
OrgAbuseEmail: abuse@iana.org
OrgAbuseRef: https://rdap.arin.net/registry/entity/IANA-IP-ARIN

OrgTechHandle: IANA-IP-ARIN
OrgTechName: ICANN
OrgTechPhone: +1-310-301-5820
OrgTechEmail: abuse@iana.org
OrgTechRef: https://rdap.arin.net/registry/entity/IANA-IP-ARIN