|
| The Gateway is as the name implies is the "gateway" to the internet - in other words, it's where your computer has to talk to in order to send and receive info from the world-wide web. GENERALLY, the gateway should be the IP address of the router your device connects to. Also, the SUBNET MASK, must be 255.255.255.0 - unless someone with a pocket-protector in their white-shirt pocket and black-plastic rimmed glasses has set these for something else.
Your home's router should have an option of "set DYNAMICALLY by ISP" for the gateway and subnet mask - those settings are your best bet.
Similarly, each of your computers and "internet-of-things" should be set to automatically/dynamically get their IP configurations from the router.
A quick and easy command-line refresh of these settings is:
ipconfig /all - shows you the IP addresses, Gateways and Subnet mask settings of that particular computer for easy diagnosis.
ipconfig /release - clears all the IP address settings from your computer
ipconfig /renew - tells your computer to talk to the router, get the latest IP information and away you go...
I presume you are using a wireless ISP - a company sending your internet via a micro-wave connection? Your ISP's "modem" should be a small, quick-responding box that re-boots quickly. It probably hooks up to your own wireless router in the house. This router should reboot slower, because it has a lot more software to enable it to do stuff. I have used in the past satellite ISPs whose point of presence in my house was a large, cumbersome unit that took almost 5 minutes to re-boot. Meanwhile my own wireless router had already rebooted, and picked some IP addresses out of the air which didn't work. I would have to re-reboot the personal router so it got accurate IP addresses from the modem. Perhaps this sounds similar to your world?
Another thought - is your wireless router an older model? Do you have a lot of things going through your wireless router? Some older units had a small number of IP addresses it could give out - like maybe 25? 10? Check your router's range of IP addresses it can give out. Make sure you have plenty - newer routers will allow up to 250 or so. If your router has a small number, once you quit using the internet, another thing will want to get onto the internet, and due to a lack of IP addresses, the router will say, "the computer's not active, let's bump it off and re-use that IP address."
Finally, TTL (time to live) setting maybe too short. TTL tells the router how long each individual IP address can remain assigned to a particular device. If your TTL is set for a short duration, like 30 minutes, then when something else wants to go on the internet, your computer's "lease" on the IP settings expires, and the IP configs are no longer available to you. If you don't have a congregation of folks stopping by your place regularly to use your high-speed facilities, you can consider changing the TTL to something like 7 days, and again, make sure your livery-stable of IP numbers is more than sufficient for the number of things that want to connect to the web.
What sometimes is confusing regarding Gateways is the cascading of gateway numbers. Your computer and "internet of things" on your network need a Gateway address of the router they talk to first. That is all they need to know.
Your router needs to know how to get out to the internet from where it's at, so it's Gateway will be the next thing it talks to, which will likely be the modem or point-of-presence from your ISP. Continuing, that modem's gateway will be the router it's talking to back at the ISP's head-end. And the ISP's router's Gateway will be the ISP's point-of-presence for their internet connectivity. YOU CAN NOT SHORT-CUT THIS DAISY-CHAIN - each device must talk to the router it's connected to.
Keep us informed on what fixed your issue. Thanks!!
Edited by YawLes 6/9/2018 13:45
| |
|
Default gatewayproblem
