192.168.42.1 Admin Login: HT2000 Password
192.168.42.1 is the gateway for the older HughesNet HT2000 and some Pace gateways, and the tether address for Android phones. Find out which one you have.
You typed 192.168.42.1 into your browser and a login page opened, or nothing happened at all. I have seen this address mean three different things, and the right login depends on which device sits behind it. This guide sorts out the HughesNet login, the Pace gateway, and the Android tethering case, so you type the right password the first time.
This guide gives you the 192.168.42.1 login, the devices that use it, and the steps that get you in.
On the older HughesNet HT2000, 192.168.42.1 logs in with the username left blank and the password admin. Pace 4111N gateways use the same address with admin and admin, and Android USB tethering uses it with no login page at all. Check which device you have before you type anything.
The fastest way in: tap the button below, then sign in with the details in the box.
IP Address: 192.168.42.1
Username: (none — leave blank)
Password: admin
Login to Admin Panel →This button opens your device’s admin page at 192.168.42.1 directly. It works only when your device is connected to that network, by WiFi or cable. This login belongs to the older HughesNet HT2000. Pace gateways and Android tethering use this address differently, as the sections below explain.
How to Log in at 192.168.42.1
These steps cover the older HughesNet HT2000, which is the device with a verified login at this address.
- Connect your computer to the HT2000 with an Ethernet cable or over its Wi-Fi network.
- Open a browser and go to 192.168.42.1. Type the address into the address bar, not the search bar.
- Leave the username field blank and type admin in the password field, then click Login.
- The HT2000 status page opens, and you can check the signal, the Wi-Fi settings, or the connected devices.
- Change the admin password at first login, and write the new one down before you save it.

192.168.42.1 Default Username and Password
I keep this table short on purpose: only the devices with a documented login at this address belong in it. Find your device first, then try its row.
| Device | Username | Password | Login IP |
|---|---|---|---|
| HughesNet HT2000 (older units) | (none — leave blank) | admin | 192.168.42.1 |
| Pace 4111N-030 / 4111N-031 (reported) | admin | admin | 192.168.42.1 |
| HughesNet HT2000W / HT3000W | check the label | check the label | 192.168.0.1 |
| Android USB tethering | — | — (no login page) | 192.168.42.1 |
The HT2000 pair comes from several hardware databases that agree with each other. The Pace pair is reported by one database, while Sonic’s own help says the Pace password sits on the modem label, so I treat the Pace pair as reported, not confirmed.
Some login sites print root, user, or admin as the default for this address. No brand or model sits behind that claim, and I have never seen it work on an HT2000 or a Pace gateway, so this article does not use it.
Android USB Tethering Uses 192.168.42.1 Too
Android USB tethering uses the 192.168.42.0/24 range, and 192.168.42.1 is the address the tethered connection takes. I check this case first whenever someone types the address on a phone, because it explains the blank page.
There is no admin page and no password here. The settings live in the phone itself, under Settings and then Hotspot and tethering. Wi-Fi hotspot is the sibling address 192.168.43.1, and it has no login page either. If your computer shows 192.168.42.1 as its gateway while tethered, the address is working as it should, and there is nothing to log in to.
192.168.42.1 Not Opening?
I start with the device itself, because that is where most failures at this address begin.
- Make sure your device is connected to the right network, not to mobile data or a different Wi-Fi network.
- If you are tethered to an Android phone, there is no login page. Open the phone’s hotspot settings instead.
- Try a blank username with admin first on the HT2000. Admin and admin belongs to the Pace 4111N, not to the HughesNet unit.
- Check that Caps Lock is off, and type the password exactly as it is. Passwords are case-sensitive.
- Try the other address for your device. Newer HughesNet units answer at 192.168.0.1, and older Pace firmware answers at 192.168.1.254.
- Restart the modem: unplug it, wait 30 seconds, and plug it back in.
If you still cannot log in because the password was changed and forgotten, reset the router to factory settings: press the reset button on the back of the unit with a paper clip and hold it for about 10 seconds, then let go.
A reset erases every setting, and the unit will ask you to set it up again. If the login page will not open at all, check that you are using the right gateway address with our router IP finder. Most home routers answer at 192.168.1.1, not at 192.168.42.1.
Common mistakes and typos
A single wrong digit sends you to a different device or nowhere at all.
- 192.168: only two parts. The browser needs all four numbers.
- 192.168.42: a missing last part. Add the final 1.
- 192.168.42.: a trailing dot with nothing after it.
- 192.168.42.l: the letter l typed instead of the digit 1. This is the most common typo of all.
- 192.168.421: the last dot missing. A different address entirely.
- 192.168.42.I: a capital i instead of the digit 1.
Type the address exactly, with dots and no spaces. If the page still will not load, the address is probably not your gateway.
192.168.42.1 problems users report, and what fixed them
Which HT2000W address does what
A HughesNet community expert listed the HT2000W’s three addresses: modem at 192.168.0.1, router at 192.168.42.1 and guest WiFi at 192.168.43.1. See HughesNet Community thread.
WiFi Settings login does nothing
A customer clicking WiFi Settings in the System Control Center landed on 192.168.42.1/login.htm and got no response. Community replies suggested disabling browser extensions and refreshing. See HughesNet Community thread.
Own router behind the HT2000W
A D-Link owner could not reach the HughesNet pages because his router also used 192.168.0.1 on the LAN. The fix was moving the D-Link to a different subnet. See HughesNet Community thread.
Thinking about pressing reset
HughesNet community experts warn not to use the modem reset button unless a HughesNet rep tells you to. See HughesNet Community thread.










