RRXuF8ysuwvpMn7w";   
   er.org";	posting-account="U2FsdGVkX19il7Y4/EcJTjBw0Qkvbrcf"   
   Gecko/20101207 Thunderbird/3.1.7   
   .os2.networking.tcp-ip:196   
   From: Peter Flass    
      
   On 3/26/2011 1:31 AM, Pierre Jelenc wrote:   
   > Jonathan de Boyne Pollard  writes:   
   >>   
   >> Perhaps your DHCP server cannot tell them apart.  Do they erroneously   
   >> have the same MAC addresses and names or something?   
   >   
   > No, they are completely different.   
   >   
   >> Perhaps you misconfigured your DHCP server.  Did you erroneously tell it   
   >> to map two clients to a single static IP address?   
   >   
   > I did not configure anything, I just unplugged the Mac laptop, which had   
   > worked fine for years, and plugged in the Linux machine, then rebooted   
   > everything (including the router, eventually.)   
   >   
   >> If your router is your DHCP server, its WWW configuration interface   
   >> (which you should be able to access from the machine whose network   
   >> connectivity is working, after all) will tell you what MAC addresses   
   >> each of its DHCP clients has.   
   >   
   > I don't see anything like that in the configuration pages. I go to   
   > http://192.168.1.1/ where I log in, and I get this menu (submenus   
   > expanded):   
   > Wizard Setup   
   > Advanced Configurations   
   >      Router Password Change   
   >      Internet Security   
   >      NAT Applications   
   >      Remote Management   
   >      LAN Setup   
   >      Wireless Setup   
   >      WAN Setup   
   >      IPSec Setup   
   > Maintenance   
   >      System Status   
   >      DSL Statistics   
   >      LAN Statistics   
   >      Wireless Statistics   
   >      WAN Statistics   
   >      Diagnostics   
   >      Firmware Upgrade   
   >      Factory Reset   
   >      Restart   
   > Logout   
   >   
   > Nowhere is there any listing of hardware or assigned IP addresses.   
   >   
   > I tried to assign a fixed address with "ifconfig lan0 192.168.1.106" in   
   > tcpexit.cmd so as to leave 105 free, but that ends in failure as well: the   
   > 106 address is assigned, but the net is still inaccessible (whether or not   
   > the Linux box is plugged in.)   
   >   
   > Pierre   
      
   Probably something under LAN setup.  You should be able to configure    
   DHCP (or not) and/or DDNS.  What address/options did you assign when you    
   did the OS/2 TCP/IP configuration?   
      
   You should run an ethernet monitor in promiscuous mode on Linux and log    
   all the packets.  This should point you in the right direction.  I    
   assume this LAN is only these two or three machines, so you're not    
   talking huge volumes of traffic.   
      
   --- Internet Rex 2.31   
    * Origin: A noiseless patient Spider (1:261/20.999)