My apologizes for posting a question that has undoubtedly been asked several times before, but I have searched and read through nearly every post I could find on the subject but with no solution to my problem.

I have a laptop with Windows XP Home installed on it (named HAL), and a PC with Fedora 2 installed on it (named QUEEG).

HAL has a wireless network connection (this is how it receives its Internet access), and a LAN connection. QUEEG only has 1 NIC card. HAL and QUEEG are connected to each other via a crossover cable, and they happily share network files thanks to Samba.

What I want know is how to share HAL's internet connection with QUEEG. I have enabled Internet Connection Sharing on HAL's LAN connection, and I have ran the Internet Configuration Wizard on QUEEG - but with no success. Both machines can ping each other by IP and name.

Here is the result of ipconfig on HAL:

I have tried manually setting the IP address of QUEEG to 192.168.0.2 and it's default gateway to 192.168.0.1 (HAL's LAN), but this didn't work. I also tried letting QUEEG obtain an IP automatically from HAL via DHCP but this didn't work either.

Has anyone any suggestions as to what I should try next? I'm faily stumped now as to what to try next, I'm not very familiar with Linux or networking I'm afraid...

Thanks for any suggestions,

First, your setup is not normal. It's usually the linux box that shares the internet. Making a windows computer also function as a router is bad.

Are you sure the Windows computer has ip forwarding turned on? I think you need to do some registry editing: http://www.wown.com/j_helmig/w2kprout.htm

When you execute the route command on the Linux box, what does it say? (Is 192.168.0.1 the default gateway?)

all u need to do is run the ics wizard on winxp and statically assign addys as u have done. then check in /etc/resolv.conf that u have entered ur gateway/dns server as ur nameserver which is the ip addy of your win xp box
for example
nameserver 192.168.0.1 (winxp assigns this addy by default as your lan ip when u run the ics wizard) if this doesn`t work then try assigning by the same method the other addy of 192.168.2.1 but I should imagine the first address will work just fine :-)

On QUEEG run:

on the Windoze machine open up the command prompt (Start/Run/command) and type in:

route print

than you want to find the name of the nic that is connected to QUEEG and at the being of that line there should be a hex value (i.e. 0x1, 0x2), remember that hex value.

Now type in;
route add 198.168.0.2 < THIS COMPUTERS GATEWAY ADDRESS > if < That HEX VALUE >

Now make sure the all the nics are configured and up, you should now have your routes set and it all be working... I am not too sure if the windows route command is right, the Gateway part... But give it a try... It should work thats the only way I could see what you would put there....

Post back with results...

Andrew

---

Andrew nrd.

bobwall:

I just turned on IP forwarding, and it doesn't seem to have made any difference.

When I run the route command on QUEEG I get the following:

So to try and answer your question.. I think the answer is yes as HAL is 192.168.0.1 ( )

mermxx:

My /etc/resolv.conf originally looked like this:

I changed the IP of the name server to both of your suggestions, but neither seemed to have worked.

NLR:

On QUEEG results in this output:

On the Windows machine

Tells me that the hex index of the card is 0x3 (as well as telling a bunch of other stuff).

I tried this, but I'm not exactly sure what I am meant to be inserting here (and I presume 198.168.0.2 is a typo, and that you mean 192.168.0.2). When you say < THIS COMPUTERS GATEWAY ADDRESS > do you mean the router (192.168.2.1) that my wireless card communicates with? If you do then running this:

Results in this output:


Thanks for the help so far guys, hopefully I can this sorted soon - you have certainly given me an angle to work with. I don't have the time now to mess around anymore, I will try again tomorrow. If you need more details on my setup please ask.

Cheers,

Try to ping google.com by ip address instead of name on the client (find out google's ip by doing a ping on another computer). If it works, then I bet that the entry in resolv.conf is supposed to be whatever the name server HAL is using (should be your ISP's name server). Just add the entry to it and restart your network interfaces.

Yes that was a typo... I don't know much about windows route... You could try the computers ip address... The only reason I could think of windows wants is because it wants to know what computer that computers gateway is... I don't understand why though... Try:

route add 192.168.0.2 192.168.0.1 if 0x3

Maybe....

Andrew

bobwall

I tried pinging google by IP and name already and neither worked.

NLR

I just tried that and doesn't seemed to have worked either.


Any other suggestions - I'm stumped.

Here is a page that you can walk though, just to verify that the ISC set up right. MAKE SURE that the windows box with ISC has the IP 168.192.0.1. This is a MUST. That may alone solve the problem.

heres the link: http://www.annoyances.org/exec/show/ics_xp

When you get that down let me know

Andrew

Hmm how odd...

I just started up both machines and suddenly QUEEG could suddenly ping google's IP (but not name). So then I just changed the nameserver in /etc/resolv.conf to my router (192.168.2.1) and now everything works fine!

At last I can finally start using machine properly!

Thanks for the help guys, I'm not sure which solution worked in the end but one of them obviously did. I owe you one

I suspected from the beginning that there was something wrong with your DNS setup.

Good to here that its working!

Andrew

Hi,

My network setup is exactly identical to that of Covenent; however, I my QUEEG can only ping a certain IP addresses only after HAL pings the same address. Any ideas what's wrong?

NOTE: for simplicity sake, you can assume my my computers and default gateway's ip addresses are the same as those of Covenent's.

Many many thanks in advance!