I need some computer help.

So we just moved off base and we are now just far enough out of town that no one offers cable internet. Pretty much our only choice was Hughesnet. They hooked us up yesterday, and when I plug straight into the modem I can get online but the wifi router (TP-Link AC1750) we used on base will not play nice with this new modem.

I'm not very computer smart but with some googling I was able to find that both the router and modem are using the same IP witch I think is at least on of my problems.

If I plug into the router I can access its settings page change its IP but it just kicks out an error when I tried that. I can get on the wifi network with the PC and our phones just cant get online through the router.

Can anybody out there help?

Are you sure that the modem that you were issued by hughesnet isn't also a router?

The only connections the hughesnet thing has is input cable, power, 1 LAN port,and 1 usb. It doesn't say anything about being a router, but then it also doesn't say modem on it.

Most routers offer an initial set-up wizard. Do that again. There are some more features in many routers that get around ISP restrictions that are seldom used today, such as MAC address cloning, but I'd start with re-doing the set-up wizard.

When you plug the computer into the modem, take note of the IP address it gives you, specifically the address range (so 192.168.x.x)

Open a command prompt (run cmd or search for cmd) and type "ipconfig" and hit return.

Note the IP address, DNS and gateway addresses you receive from the modem.

The gateway address is likely the address of the modem.

Then plug the computer directly into the router. Once you get a connection, note the IP address and Gateway again.

The gateway address is likely the address of the router.

Now, go to the management website for the router (usually the gateway address, I.e. http://192.168.0.1 or similar), login and change the router's address to one that is different from the modem.

So instead of 192.168.0.1 for example change it to 192.168.0.2 or .3 so it isn't the same as the address for the modem, but is within the range provided by the modem.

Add the DNS Addresses provided by the Modem.

Once that is done, you'll want to change the router's DHCP range to start around .10 to avoid the range where the modem and router will be hard configured.

Save the changes, power off the the router and plug it into the modem.

Power the router back on and wait for your computer to get a new address.

Verify you have internet connectivity and that you can still access the router's management website.

OK, so I have reset and rerun the setup for the router a few times and still have no luck.
According to the paperwork from hugesnet my IP should b 192.168.0.1, but with the pc plugged into the modem running 'ipconfig' kicks out 100.120.225.146 and a default gateway of fe80::280:aeff:fe15:cbb3%2 --- 100.120.225.145
If I plug just into the router I get 192.168.0.100 with a default gateway of 192.168.0.1, and if I plug the pc into the router and then into the modem I get the same numbers as just the router.
In all three configurations the lines next to all DNS spots are empty.
Should I try reseting the router and inputting 100.120.225.148 ?
I swear I'm better at turning wrenches then fixing computer stuff.

So what we need to establish here is that the WAN (modem to router) connection and the LAN (router to PC) connections are going to be on different IP ranges. With the router plugged into the modem, you should be able to access it at 192.168.0.1 from a PC. Looking at Status and scrolling down to the WAN section, it should show 100.120.225.146 or a smiliar number, indicating that it's getting an IP from the modem.

As far as lack of DNS servers go, you might have that turned on in the router. Try setting it up like this:

Here is a very basic troubleshooting question: Is the ethernet cable (between the Hughes modem and the wireless router) plugged into the router port labeled LAN?

To the herd.. Do they still make "crossover" ethernet cables and might the cable type contribute to what's happening?

In reply to red_stapler:

It works!!!! I put the settings for the DNS stuff and it now works. I was even able to change the network name and password, and it still works. I'm so proud of myself for doing something a kid could have figured out.

Thanks GRM.

Also I had tried multiple sets of cables just in case that was the issue.

Awesome, glad I could help! Cramming for net+ pays off again!