On Fri, 16 Jan 2009 19:09:41 +0000 Chris G cl@isbd.net allegedly wrote:
I have just built (well, re-installed the OS on) a new system and have connected it to my LAN. It's running xubuntu 8.10 and uses the TV as its display device (probably irrelevant).
It all installed fairly smoothly and appeared to work OK except that the networking was a bit 'jerky'.
I then found that I couldn't ssh from the new machine to my desktop machine whereas other machines on the LAN could connect OK. It turned out that this was because the machine had the *same* IP address as my desktop machine. This of course explains the 'jerky' networking too!
However I really can't understand *why* it has decided its IP address is 192.168.1.4.
OK, some details, the router IP is 192.168.1.1 and it's the router that provides DHCP to the network. Most machines have static addresses, in particular my desktop machine (as noted above) is 192.168.1.4. The router is set up to start handing out DHCP addresses starting at 192.168.1.64 and this does work as there is a device (a VOIP server) which gets the address 192.168.1.64.
The 'new' xubuntu system has default network setup, I have given it the name 'lounge' (which is different from all others) and it acquires its IP address and networking setup automatically on startup.
So *how* is it getting 192.168.1.4 as its IP address?
Are you /sure/ the router's DHCP pool starts at .64? If the machine in question is one that you have used before (as it appears to be from your email) then my guess is that the MAC address of the machine is recognised by the router as one that it has handed out an address to in the past and it is configured to hand out the same address to that MAC in all future requests. If your desktop has a fixed IP, then the router won't know about the conflict.
Check your router DHCP config.
Mick ---------------------------------------------------------------------
The text file for RFC 854 contains exactly 854 lines. Do you think there is any cosmic significance in this?
Douglas E Comer - Internetworking with TCP/IP Volume 1
http://www.ietf.org/rfc/rfc854.txt ---------------------------------------------------------------------