192.168.0.117 router login

To open the admin panel, type 192.168.0.117 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.0.117 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 are on record for 192.168.0.117, and for a mid-pool client address there frequently is no web login to begin with. Many leased devices expose no management page at all, so a blank browser tab is the expected result rather than a sign of a problem. Where the device does have an interface, get the defaults from its own label, its packaging insert or the manufacturer's manual for that model. If you are actually after the router, check your gateway address, which will usually be elsewhere in this subnet.

How to log in to your router

  1. Type 192.168.0.117 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.0.117, 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 goal is simply to identify the holder of this lease, no reset is needed. Compare the MAC address shown in your router's client list against the devices you own, or check the network details on each device in turn until one reports 192.168.0.117.

Resetting the client itself is a blunt instrument: it wipes that device's own settings, and because the address came from DHCP it will likely return with a different one, making the situation harder to trace. If you want the address to stay put, create a DHCP reservation on the router instead of changing anything on the device.

192.168.0.0/24 is one of the most heavily used private subnets anywhere, and 192.168.0.117 is a single host inside it. The usable range is 192.168.0.1 to 192.168.0.254, broadcast is 192.168.0.255, and .117 falls squarely in the middle where DHCP pools are usually set. An address like this almost always identifies a client that was handed a lease, a laptop, phone, console, television, printer or smart-home device, rather than the router itself.

The parent range, 192.168.0.0/16, holds 65,536 addresses under a 255.255.0.0 netmask and is the consumer block. Home routers, hotspots and small office access points default into it so consistently that the same host address recurs on countless separate networks, which is exactly why it carries no owner, provider or location. Whatever is on 192.168.0.117 on your network has no relationship to whatever holds it on anyone else's.

The practical questions people bring here are which of their devices took the address, whether an unfamiliar entry in the router's client list is something to worry about, and why typing the address into a browser produces nothing. We have 249 other addresses documented in this /24, reflecting how densely the range gets used.

Block192.168.0.0/16
Netmask255.255.0.0
Subnet192.168.0.0/24
Usable192.168.0.1 – 192.168.0.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