here's an excerpt from the book i read which helped me solve my problem: :mrgreen:
Two Mother Hens fighting
Man, you ain’t seen nuthin’ ’till you’ve seen two fighting Mother Hens. Many cable/DSL/satellite modems these days get attached directly to broadband routers. In fact, that may be the most common configuration: It’s cheap, effective, flexible . . . and sometimes infuriating. Many cable/DSL/satellite modems are set up as DHCP servers — Mother Hens — that expect to dole out IP addresses to each computer on the network.
Many cable/DSL/satellite modems assign themselves an IP address of 192.168.1.1, and then hand out IP addresses starting in that range. Unfortunately, many broadband routers are also set up as Mother Hens.
They, too, expect to hand out IP addresses. Many of them assign themselves an IP address of 192.168.1.1, and expect to hand out IP addresses starting in that range.
What’s wrong with this picture?
Well, if you power up your modem, and it assigns itself an address of 192.168.1.1, and then you power up your broadband router, and it assigns itself an address of 192.168.1.1, you suddenly have an enormously unstable situation. And when the unsuspecting PCs come up for air, seeking a Mother Hen to assign them an IP address, the feathers start flying.
Here’s my favorite solution.
Start your router, and then start a PC attached to the router. Follow the manufacturer’s instructions to get into the router from the PC (usually you crank up Internet Explorer and type http://192.168.1.1).
Then change the router’s starting IP address to, say, 192.168.2.1. Make sure you update and reboot the router. While it’s possible to go diving into the DHCP server settings on the router or on the modem, there’s really no need. By setting the starting IP address on the router to something different from the starting IP address on the modem, you move each of the Mother Hens into their own, separate hen house. End of fighting. All is right in the world.




Reply With Quote