8ca7caf3   
   XPost: comp.arch.embedded   
   From: none@none.invalid   
      
   On Mon, 31 Jan 2011 10:12:19 -0800 (PST), Didi  wrote:   
      
   >On Jan 31, 7:59 pm, Tauno Voipio    
   >wrote:   
   >> ....   
   >> You're probably asking for more than the XP is able to fill in.   
   >>   
   >> To route packets from the ISP's net to a local subnet and back   
   >> needs NAT (Network Address Translation), which is Internet Connection   
   >> Sharing in windowspeak.   
   >   
   >No-no, I am not asking for that. I just want the packets originating   
   >from the windows machine to go to the DPS machine on the same wire,   
   >I am not expecting windows to route incoming IP traffic to the DPS   
   >machine, nor to do NAT for the DPS machine and route its IP traffic   
   >out to the Internet. I am just after a local connection without   
   >disconnecting the wintel machine from the Internet. What I do now   
   >is manually set the windows IP address to 192.168.100.something   
   >and access the 192.168.100.something_else machine; I did not have   
   >to do that until recently but my ISP began to give me via dhcp   
   >addresses from _different_subnets_ over the same cable modem   
   >(yes, they are morons and I wish I had options), and lately   
   >began limiting the number of addresses they give me (used to   
   >give me 5 with no problem for years - before a takeover   
   >took place...).   
      
   Is adding a NAT router an option? The router would pick up the ISP's   
   DHCP info while your Windows and DPS machines would both be on the   
   same local non-routable network.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)