The router is running a DHCP server. When a server gives a client an IP address, it comes with a lease time. If the computer shows up again on the net within that lease time it will get the same IP. When you plugged in the laptop, the lease time on 101 must have just run out. How to reset leases is specific from server to server. With the dhcpd on suse's CDs you'd just have to remove the dhcp.leases file and restart dhcpd. How to do it on linksys I have no clue. Another question: why is the specific IP important? If it *really* matters (and until I hear a convincing argument I doubt it), and you're on a home connection as the only user, it is usually quite possible to use static IP, if you know the range the router accepts. regards Anders On Thursday 22 November 2001 19:03, Michael Molloy wrote:
I've got Suse 7.1 running on a machine that gets it's IP address dynamically from a Linksys DSL/Cable Router. I need it to be at 192.168.1.101, so I set the router to make that the first available IP address. For a long time, this has worked great.
However, the other day, I plugged my laptop in when the linux box was off, and the laptop got the 101 address and the linux box got 102. Today, I powered everything off, turned the router off, then turned the router back on & started the linux box first. It still came up as 102, not 101.
Can anyone tell me why this is happening & how to fix it?
Thank --Michael