38d7b329   
   XPost: comp.arch.embedded   
   From: andrews@sdf.lonestar.org   
      
   On 2011-01-31, Didi  wrote:   
   >   
   > It is an option of desperation, of course, but adding another box   
   > only because windows cannot do the correct lookup in its ARP table   
   > is what it is... :-) . Actually I could make the DPS machine   
   > behave as a router and all that - will do it before too long - but   
   > there should be a way devices on the same wire to communicate with   
   > each other...   
   >   
   > Then I prefer that window machine to be with a real IP address,   
   > it keeps a listening VNC viewer to accept support connections   
   > from customers etc. Port forwarding will do most if not all   
   > of what my current needs are but I still cannot accept that   
   > a purely software issue - a very simple to solve one - will   
   > force me to add hardware etc.   
      
   It can do most of what you want by playing with the routing tables.   
   At an administrative command prompt:   
      
   route add  mask  0.0.0.0 if    
      
   I would hope IP address and network mask are self explanatory.   
   The interface number is an internal Windows thing - perhaps the   
   easiest way to find it is with a "route print", and the interface   
   number will be the leftmost number by the physical NIC.  For example,   
   on the Windows machine here:   
      
      
      
   C:\Users\Administrator>route print   
   ===========================================================================   
   Interface List   
    11...00 25 22 82 0e 1f ......NVIDIA nForce Networking Controller   
     1...........................Software Loopback Interface 1   
    12...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter   
    13...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface   
   ===========================================================================   
      
      
      
      
   The "11" by the NVidia controller is the correct number here, yours   
   may well vary.  After the "route add" you should be able to ping the   
   device in question, assuming that _it_ is configured to recognise   
   the Windows machine (still using its original IP address) as being   
   on the local network.  Simply setting an entry in the ARP cache   
   probably won't work - who uses proxy ARP anymore?  However if the   
   ping is unsuccessful an "arp -a" may help with diagnosis - if there   
   is an entry then the route and ARP are working so presumably the   
   ping got through and the problem is at the other end.   
      
   --   
   Andrew Smallshaw   
   andrews@sdf.lonestar.org   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)