• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

WHS IP/Subnet issue

IndyJaws

Golden Member
I have a Windows Home Server that has been purring along for several years. I use a static IP to allow me to access it remotely. I recently upgraded my router, and now I've lost all connectivity. I assume it was because the default gateway IP had changed.

My former TCP/IP entries with the old router that worked just fine:
IP address: 192.168.1.254
Subnet mask: 255.255.255.0
Default gateway: 192.168.1.1

With my new router (IP as reported by Asus Discovery), I update the default gateway:
IP address: 192.168.1.254
Subnet mask: 255.255.255.0
Default gateway: 192.168.50.1

I get the error message "Warning - The default gateway is not on the same network segment (subnet) that is defined by the IP address and subnet mask. Do you want to save this configuration?"

I'm many years removed from remembering how to properly configure a subnet mask, so asking for help in getting this resolved. I realize this is a noob question, so hopefully someone can show me where I'm messing up. Thanks in advance!
 
Generally speaking, on non-segmented SOHO networks (based on consumer router gear), you want everything to be on ONE subnet. For most home users, that's the number immediately AFTER the 192.168.x.y <- the 'x', with the 'y' being the machine number, and 192.168.x.1 being the gateway and DNS server, again, generally.

If your new ISP router's subnet is 192.168.50.y, then you should configure your server as LAN IP of 192.168.50.254, with a subnet mask of 255.255.255.0, and a Gateway IP of 192.168.50.1. That's if your router's LAN IP is 192.168.50.1.
 
Back
Top