if he has dsl, it would be on a different card to the internal interface...
depending on his setup, if he has two NIC's in his PC, one for the internal net and the other for his DSL link, then they should both have their own IP address. people seem to forget that its the interface that gets the IP, not the machine itself. so whatever interface the DSL comes up as should have that IP, and whatever card does the internal network interface should have its own internal IP as well. if you have your DSL modem plugged into the hub and you are accessing it like that, I suggest you go and get a second NIC, plug it into your gateway machine, and use that with a crossover cable to connect the modem to that PC.. (assuming its an ethernet dsl modem like we have.) that way, you have eth0 with could be your internal network interface card. and eth1, which would be your DSL internet interface.. then you set your gateway device to eth1. I don't use a gateway ip.. in my network settings, I remove the GATEWAY=* entry and add GATEWAYDEV=eth1 (thats in /etc/sysconfig/network ) that way the gateway IP doesn't matter.. works great for me. so in summary. Specify the relevant IP's for each interface, make sure you have seperate interface for Internal and external (internet) connections. bobs your uncle. rgds Frank. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Randy Kramer Sent: Sunday, 24 February 2002 9:04 PM To: [EMAIL PROTECTED] Subject: Re: [newbie] Linux and Win XP Franki wrote: > no, your problem is that your machines are on different subnets.. > > as a test, set your XP machine up to use IP 192.168.0.1 and your linux box > to use 192.168.0.2 and your netmask to both as 255.255.255.0 > > then restart the networking on both, and try pinging,, it will work if your > network cards are working. > I don't really understand why you see the need to do this, what is assigning > the IP for the XP machine? and why isn't it also assigning one for the linux > box? Well I guess he's letting his ISP assign an IP to his Windows box so it will work on his DSL line (or whatever). I get around a similar problem by running NAT, but I'm trying to think of a solution for him. One way would be to run NAT (I think that's the basis of Microsoft Internet sharing or whatever they call it, and then continue to use IPs as you suggested in the second quoted paragraph above). But, I've never set up Microsoft Internet sharing so I don't know how to tell him (the original poster) to do that. Randy Kramer
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
