Hi Bill,
try adding a localdomain name the hostname in /etc/hosts. A name
like 'localnet.net' will do.
The "redhat7.0" hostname is not required for the localhost which is for
internel pinging to host 'localhost' only.
eg /etc/hosts
127.0.0.1 localhost.localdomain localhost
192.168.1.1 pentium.localnet.net pentium
192.168.1.2 duron.localnet.net duron
Have a look at man #ifconfig and #route.
Type #route in console to check it is up and the commands are like
this.
#ifconfig eth0 192.168.1.1 netmask 255.255.255.0 up
#route add -host 192.168.1.2 eth0
cheers,
Keith.
> /etc/hosts
> 192.168.1.2 duron duron
> 127.0.0.1 redhat7.0 redhat7 localhost.localdomain
> localhost
> 192.168.1.1 pentium pentium
On Tue, 3 Sep 2002, Bill Evans wrote:
> I am aiming to set up a SAMBA network between two computers.
> They are a Duron 800 with 128 MB RAM running Windows98 (1st edition)
> and a Pentium 133 with 32MB RAM running Redhat 7.0.
>
> As a first step I am trying to establish an ethernet connection between the
> two.
> Previously when the Pentium was running Windows98 I had successfully
> networked the two together.
> The NICs and cable have not been altered since then (apart from checking the
> cable connection just now.)
>
> I cannot ping between the two computers.
> Both computers can ping their own local host.
> The Pentium, running Linux, can ping itself at the address 192.168.1.1.
> (using either the address or nickname)
> Perhaps significantly, the Duron, running Windows, cannot ping itself
> (192.168.1.2)
>
> On the Duron:
> Network configuration shows:
> Primary Network Logon is set to Client for Microsoft Networks
> File and printer sharing for MS Networks is installed
> The NIC is listed as PLANET ENW-9503/04 PCI Fast Ethernet NIC
> Both NetBEUI and TCP/IP are installed for this card.
> TCP/IP properties:
> IP Address 192.168.1.2
> Mask 255.255.255.0
>
> I have edited the c:\windows\hosts file to contain the following:
> 127.0.0.1 localhost
> 192.168.1.1 pentium
> 192.168.1.2 duron
>
>
> On the Pentium:
> I have looked around for files I thought might be relevant.
> Here they are: Don't ask where I configured each of these. I have been
> playing around in both the CLI and in Gnome's
> Network Configuration for the last couple of days :)
>
> the NIC, the subject of an earlier thread, is now recognised ok
> /etc/modules.conf
> alias eth0 ne2-pci
> alias parport_lowlevel parport_pc
>
> /etc/HOSTNAME
> pentium
> /etc/hosts.conf
> order hosts,bind
>
>
> (Initially either the localhost or pentium, I forget which, was called
> wb.invalid by default, but I changed it. Given the following DOMAINNAME,
> this might be significant.)
>
> /etc/sysconfig/network
> NETWORKING=yes
> HOSTNAME=pentium
> DOMAINNAME=invalid
> GATEWAY=192.168.1.1
> GATEWAYDEV=eth0
>
> /etc/sysconfig/network-scripts/ifcfg-eth0:0
> DEVICE=eth0:0
> BOOTPROTO=none
>
> /etc/resolv.conf
> nameserver 192.168.1.1
>
> /etc/networks
> this file is empty
>
> Network Configuration.
> Gnome's Network Configuration shows settings as follows:
> Hostname, nameserver, hosts, default gateway, and default gateway
> device all as above.
>
> Interfaces:
> Interface lo
> IP 127.0.0.1
> Proto none
> atboot yes
> active active
>
> Interface eth0
> IP 192.168.1.1
> Proto static
> atboot yes
> active active
>
> Interface eth0:0
> IP
> Proto none
> atboot
> active active
>
> Interface eth0:0 is a mystery to me . Does this get set automatically?
>
> Any help would be appreciated.
> I would guess the problem lies in the Windows machine, given that it
> cannot ping itself.
>
> Bill
>
>
>
>
>
>
