192.168.100.164 router login

To open the admin panel, type 192.168.100.164 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.164 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 credential pair is recorded for 192.168.100.164, and guessing at one would be irresponsible. A statically assigned host on a segment like this could be an access point, an IP camera, a print server, a controller or a management card, and each of those families handles its first login differently.

The device's own documentation is authoritative. Look for a factory username and password on the label, in the quick-start guide, or in the model-specific manual; enterprise-style gear sometimes ships with no password at all and prompts you to set one during the first login instead.

How to log in to your router

  1. Type 192.168.100.164 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.164, 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

If the interface at this address rejects you, check the obvious causes before anything drastic: a browser cached over HTTP when the device now expects HTTPS, a non-standard management port, an account that was renamed during setup, or a colleague who changed the password and did not record it.

A reset on a statically addressed host is disproportionately expensive, because the fixed address itself is usually part of the configuration you would be destroying. Along with the password you lose the addressing, so the device may reappear on a DHCP lease elsewhere and every system that referenced 192.168.100.164 will need updating.

192.168.100.164 falls within 192.168.0.0/16, 65,536 private addresses under a 255.255.0.0 netmask. This is the block consumer equipment lives in, which also means the same address is in use on countless unrelated networks at this moment. Nothing about it can be traced, geolocated or attributed to an operator, and any source claiming otherwise is describing something it cannot know.

The address sits in 192.168.100.0/24, where usable hosts run 192.168.100.1 to 192.168.100.254 and 192.168.100.255 is the broadcast address. Position 164 is not a gateway slot. Numbers in this part of a subnet are often used deliberately for fixed assignments, since administrators frequently reserve the upper portion of a /24 for static addresses and static DHCP reservations while leaving the lower portion to the dynamic pool. Our records cover all 254 usable addresses in this segment.

With roughly 128 searches a year, this page is usually reached by someone who has found the address written into a configuration file, a printer setup, a camera app or a saved bookmark, and who wants to confirm what kind of host normally answers on it.

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