![]() My network requires 100.1 because of a bunch of other rules and Windows Server setup. Looking for advice, since it worked fine with Bell, but the Rogers gateway in bridge mode seems to hardcode 100.1. ![]() Should I just keep the Rogers modem in gateway mode and change its LAN address to 100.1 and remove my own router from the equation altogether? ![]() What happens if I put the Rogers gateway back into gateway mode but disable its DHCP? Would it stop taking 100.1 and then I can plug the router back in for my port forwards? The best thing for you to do is set the gateway to 192.168.100.2, you should be able to set the gateway on Windows server to 192.168.100.2. Is there any way to get the router to use 192.168.100.1 again? It keeps changing itself to something else because of the conflict upon Rogers modem reboot, which screws up everything and even disables internet on the network (Windows Server looking for 100.1). If you reset your modem or put it back to the default 192.168.0.1, you can still get to the diagnostic page at 192.168.100.1. When I switched to Rogers internet, the gateway steals 192.168.100.1 in bridge mode and kicks off the router due to IP conflict. When I had Bell Internet, it all worked properly with the modem in bridge mode and the router setup as described. I disable DHCP on my router, assign it 192.168.100.1, and forward some ports (such as surveillance cameras, etc). I have a network that is set up using a Windows Server domain as my DHCP using. Bringing this post back from the dead (well, only 4 months old anyway).
0 Comments
Leave a Reply. |