• Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!

IP conflicts

WHS (including the bits I haven't quoted).

A friend of mine gave me a useful tip a few years ago: rather than staying with the default 192.168.1.x DHCP/NAT range, move your router's DHCP to somewhere else - say, 192.168.23.x, where the 23 can be any value from 1 to 255.

That way you are very unlikely to end up with DHCP conflicts when something that also has DHCP enabled connects to your network. Everything uses 1 as the default, which makes 192.168.1.x potentially a crowded neighbourhood.

Good tip thanks.

I've always nailed mine down to fixed IPs when possible. For the last bit of the address I had a naming scheme, so that my Winders boxes were numbered 11, 12..., Linux boxes 21, 22... and so on. This made it easier to remember which addresses were running which OS and helped when sifting though logs.
 
I've had that before on my Netgear router, and I think it's when it's struggling to reconnect the ADSL. I imagine the "limited connectivity" message is because the ethernet connection was dropped, then tried to reconnect but DHCP didn't work. It's not specific to wireless.

BTW I have a ******** firmware for some time. I haven't had the aforementioned problem for a long while, so maybe it was the firmware that fixed it.

Without wanting to sound rude here, but I wouldn't advertise what Router manufacturer and firmware you are using on a forum that can be read by the masses. It's something that hackers love to see. Just a thought.
 
Without wanting to sound rude here, but I wouldn't advertise what Router manufacturer and firmware you are using on a forum that can be read by the masses. It's something that hackers love to see. Just a thought.

I'm using a dual tier of Checkpoint UTM's and Cisco ASA's in case any hackers are reading this ...
 

Advertisers

Back
Top