Repies under Louis> > -------------------------------------------------------- > C:\>ipconfig > > Windows 2000 IP Configuration > > Ethernet adapter Local Area Connection: > > Connection-specific DNS Suffix . : > Autoconfiguration IP Address. . . : 169.254.79.149
And here is where the other problem is. That is *not* an internal (as in LAN internal) IP address. That is an IP address that is (or should be) visible on the internet. Now, all the other reasons this is bad aside, you won't be able to contact the linux box because the linux box and the windows box are on different networks. Louis> the address is automatically allocated by the card. There is no specific reason for this number. I can chnage this from the TCP/IP tab and use a static IP in the range 192.168.0.x. I think this would mean that I have to change it on the slave Windows PC as well. Right. Also another concern. Does changing this have anything to do with my dial up TCP/IP settings ? I don't want to break my internet connection. I'm not entirely sure why you have your computer configured this way, but one solution is to use manual configuration for the IP address of your windows machine's ethernet card and set it to an address on the same subnet as your linux computer. Something like 192.168.0.43 with a subnet mask of 255.255.255.0. Of course without knowing why it was set this way to begin with, there is every chance you'll break something else. Louis> I will give it a go now. If it creates problems with the Windows Network and my ISP, I will put it back to automatically assigning one. > >> > >> > > >> > I'm pretty sure I did netconf as quoted below. > >> > > >> > Would upgrading to a more recent Linux distribution package solves > >> > this problem ? > >> > >> good question. One to which I don't have a specific answer. > >> I will say that Redhat 8.0 (and the 8.1 beta, from looking > >> over people's shoulders at work) is a huge leap forward. I > >> would be surprised if you installed redhat 8.0 and your card > >> didn't work, but I don't actually know, and to be fair I'm > >> surprised you are having as much trouble as you are. A few > >> pointers if you do decide to: > > I am considering upgrading at some stage but I'm sure Red Hat 7.2 > Should not have that many problems. It detected the ethernet card. fair enough. Once you get it up and running there are utilities you can get to update parts of the distro, or all of it, by downloading the relevant bits from the internet. apt-get and up2date are the two common ones on redhat. Louis> I went to the shops to try and get RH Linux 8.0 but the shops here don't have it. I'll wait when I have a change to go to Dymocks in the city. A thing I noted with a command you gave. When I ran the command ifconfig eth0 192.168.0.23 up This takes precedence to the data I worte down from "netconf". From netconf the Ip address I used was "192.168.0.100". It still shows this but the ifconfig on eth0 shows it to be "192.168.0.23". If I do this with the manual command what about netconf stuff ? Also to re-enabled iptables and the other stop commands you gave, I presume I just replace stop with start. I am chaning the IP address from Windows, and use a static one, and see what happens. Hopefully this won't break anything. I get back on this. For the firewall stuff I ran the command "gnome-lokkit" and set eth0 as a Trusted Device. eth0 was not a trusted device before, so my ping was not even started for some reason. Louis. -- SLUG - Sydney Linux User's Group - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug
