ToddlerNaruto said:
We don't have a separate router, our Gateway is both the modem and the router.
Does this advice of your still apply? I'd love for it to be as simple as switching to Static IP.
Yes -- in a consumer setting, the "router" (in inverted commas) is actually an all-in-one device that includes a router, firewall, ethernet switch, wireless access point, DHCP server, etc.
Not sure if you know all this, but you'll be assigned one
public IP address by your ISP to connect your router/modem to the internet. Your "router" will then assign a
local IP address to every device on your local network, and (effectively) split the one public IP connection across all your local IP addresses.
Usually (by default) you'd run a DHCP server on your "router" which will automatically assign local IP addresses to all your devices. Normally this works well, but I've had a few random problems where the PC disconnects and reconnects intermittently when using DHCP. The other main thing to check would be the cable and connection -- it would be worth trying another cable, and/or plugging the cable into a different ethernet port on your router (or giving it a good wiggle!).
You should be able to set a static local IP address for your PC via your router's web interface. (You can access the web interface by typing the router's local IP address into a web browser -- maybe something like
http://192.168.0.1 or
http://192.168.1.254.)
Amcon said:
Also, static IPs are set on the client, not at the router.
That's not quite true. You
can request a static IP in the network settings on the client, but you can also set the "router" to assign a static IP to the client. Technically the client is still using (its own) DHCP service to request an IP address, but you can set the router to always assigns the same one.
It's easier to manage IP allocations on one device (the DHCP server), rather than on each of the clients, and in my (limited) experience, using server settings has resolved intermittent dropouts in certain cases.