Quote:
Originally Posted by heero_yuy
I'm sure Seph and the General have thought of this but I've used several routers on and off when diagnosing things and they don't all use the same local address ranges: One uses 192.168.254.xxx (SMC barricade), another uses 192.168.1.xxx (Solwise 3G wifi), current one uses 192.168.11.xxx (Buffalo airstation)
Replace xxx with 1 to access the routers setup pages in your browser.
What I've seen is that the PC and my laptop (different OS versions) even after power down and re-boot don't always re-request the DHCP, just go on trying to use the old one.
I fix it by using CLI instructions
ipconfig /release_all
and then
ipconfig /renew_all
Worth a try. (It may be having the same effect as repairing the connection but I like the CLI instructions better.)
Those same ipconfig instructions avoid rebooting the PC when changing from direct connection to the modem and connection to a router.
|
Cisco/Linksys use 192.168.100.0/24 as the default subnet with a default gateway of 192.168.1.1. The "repair connection" tool does what the ipconfig /release renew does plus more