Network is unreachable, please help

I have Fedora Core 1 installed. It is connected to a switch (hub). I
know the hardware (NIC and cable) is properly connected because the PC
(running Windows 98SE) was on the network last week.

I verified the success of the driver install for the eth0. I looked
at the bootup messages which shows

eth0: VIA VT6105 Rhine-III at 0xf800, xx:xx:xx:xx:xx:xx (correct MAC
address omitted)

eth0: MII PHY found at address 1, status 0x786d advertising 05e1 Link
45el

I ran lsmod and this shows two entrys...

via-rhine 14384 1
mii 3736 0 [via-rhine]

I ran ifconfig and this shows the correct HWaddr under eth0. And the
following...

lo Link encap: Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:59 error:0 dropped:0 overruns:0 frame:0
TX packets:59 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:7071 (6.9 Kb) TX bytes:7071 (6.9 Kb)

Then I tried to ping one of the two other machines on the local
network.

ping 192.168.0.1
connect: Network is unreachable

Last week, the Windows98SE showed an IP address of 192.168.0.3.

I tried running
redhat-config-network
and this shows a static IP address of 192.168.0.1 (which is actually
the IP address of one of the Win98 machines already on the network!).
Use DHCP [ ] is not checked. I tried checking DHCP, but this did
not help.

I much appreciate your help/suggestions, as I'm no network guru !!!

Thanks and Happy Groundhog Day!

Phisherman <nobody@noone.com> wrote:
> I have Fedora Core 1 installed. It is connected to a switch (hub). I
> know the hardware (NIC and cable) is properly connected because the PC
> (running Windows 98SE) was on the network last week.
>
> I verified the success of the driver install for the eth0. I looked
> at the bootup messages which shows
>
> eth0: VIA VT6105 Rhine-III at 0xf800, xx:xx:xx:xx:xx:xx (correct MAC
> address omitted)
>
> eth0: MII PHY found at address 1, status 0x786d advertising 05e1 Link
> 45el
>
> I ran lsmod and this shows two entrys...
>
> via-rhine 14384 1
> mii 3736 0 [via-rhine]
>
> I ran ifconfig and this shows the correct HWaddr under eth0. And the
> following...

But it didn't show eth0, which means the interface is not up. Try using
"ifup eth0", and if that doesn't work, you need to configure the
interface.

> I tried running
> redhat-config-network
> and this shows a static IP address of 192.168.0.1 (which is actually
> the IP address of one of the Win98 machines already on the network!).

Each IP address must be different and unique on the network.

> Use DHCP [ ] is not checked. I tried checking DHCP, but this did
> not help.

Did you have a DHCP server?

If it still doesn't work, post the output of "ifconfig eth0". Don't
bother blanking anything out, it doesn't add anything to this
conversation and can hide problems.

--
Cameron Kerr
cameron.kerr@paradise.net.nz : http://nzgeeks.org/cameron/
Empowered by Perl!

There is no DHCP server on the local network. Not sure if I need to
tell Linux the Workgroup name of the network to see the other (Windows
98SE) machines onthe network, nor do I know how to do this? When I
ran redhat-config-network and changed the static IP address from
192.168.0.1 to 192.168.0.3, it seems like this IP addr won't "stick,"
then still reports 192.168.0.1. And, I assume I don't need to
reboot Linux for this to take effect. By running
redhat-config-network, is this "configuring the interface?"
Thanks

Here's some additional information that may/may not help...

[root@Blue root]# ifup eth0
Error, some other host already uses address 192.168.0.1.
[root@Blue root]# ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:50:FB:E7:CA:62
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:15 errors:0 dropped:0 overruns:0 frame:0
TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2897 (2.8 Kb) TX bytes:84 (84.0 b)
Interrupt:15 Base address:0xf800

[root@Blue root]# cat /etc/modules.conf
alias scsi_hostadapter aic7xxx
alias eth0 via-rhine
alias synth0 awe_wave
alias sound-slot-1 sb
post-install sound-slot-1 /bin/aumix-minimal -f /etc/.aumixrc -L
>/dev/null 2>&1 || :
pre-remove sound-slot-1 /bin/aumix-minimal -f /etc/.aumixrc -S
>/dev/null 2>&1 || :


On 2 Feb 2004 15:32:10 +1300, Cameron Kerr
<cameron.kerr@paradise.net.nz> wrote:

>Phisherman <nobody@noone.com> wrote:
>> I have Fedora Core 1 installed. It is connected to a switch (hub). I
>> know the hardware (NIC and cable) is properly connected because the PC
>> (running Windows 98SE) was on the network last week.
>>
>> I verified the success of the driver install for the eth0. I looked
>> at the bootup messages which shows
>>
>> eth0: VIA VT6105 Rhine-III at 0xf800, xx:xx:xx:xx:xx:xx (correct MAC
>> address omitted)
>>
>> eth0: MII PHY found at address 1, status 0x786d advertising 05e1 Link
>> 45el
>>
>> I ran lsmod and this shows two entrys...
>>
>> via-rhine 14384 1
>> mii 3736 0 [via-rhine]
>>
>> I ran ifconfig and this shows the correct HWaddr under eth0. And the
>> following...
>
>But it didn't show eth0, which means the interface is not up. Try using
>"ifup eth0", and if that doesn't work, you need to configure the
>interface.
>
>> I tried running
>> redhat-config-network
>> and this shows a static IP address of 192.168.0.1 (which is actually
>> the IP address of one of the Win98 machines already on the network!).
>
>Each IP address must be different and unique on the network.
>
>> Use DHCP [ ] is not checked. I tried checking DHCP, but this did
>> not help.
>
>Did you have a DHCP server?
>
>If it still doesn't work, post the output of "ifconfig eth0". Don't
>bother blanking anything out, it doesn't add anything to this
>conversation and can hide problems.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

"Phisherman" <nobody@noone.com> wrote in message
news:3uss1057ellblgknq4ft3m58lc39mqr20k@4ax.com...
> There is no DHCP server on the local network.

you either need to set different static addresses on each card, or
configure a DHCP server to hand them out for you.
in your case, keep 192.168.0 as the first three numbers on the card,
but make sure that each machine, and each network card on each
machine, has a different number in the last octet of the address.
e.g. 192.168.0.1, 192.168.0.2, 192.168.0.3, with a netmask of
255.255.255.0. also, make sure you have more than one machine on
before you ping its address otherwise you won't get a reply! you can
always test if IP is bound to the card properly by pinging the
computer's address locally.

Not sure if I need to
> tell Linux the Workgroup name of the network to see the other
> (Windows 98SE) machines onthe network, nor do I know how to do
> this? When I ran redhat-config-network and changed the static IP
> address from
> 192.168.0.1 to 192.168.0.3, it seems like this IP addr won't
> "stick," then still reports 192.168.0.1. And, I assume I don't
> need to
> reboot Linux for this to take effect. By running
> redhat-config-network, is this "configuring the interface?"
> Thanks

type
ifconfig eth0 192.168.0.2 (or another uniqie address as explained
above) netmask 255.255.255.0

then type
ifconfig eth0

what do you see?
>
> Here's some additional information that may/may not help...
>
> [root@Blue root]# ifup eth0
> Error, some other host already uses address 192.168.0.1.
> [root@Blue root]# ifconfig eth0
> eth0 Link encap:Ethernet HWaddr 00:50:FB:E7:CA:62
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:15 errors:0 dropped:0 overruns:0 frame:0
> TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:2897 (2.8 Kb) TX bytes:84 (84.0 b)
> Interrupt:15 Base address:0xf800
>
> [root@Blue root]# cat /etc/modules.conf
> alias scsi_hostadapter aic7xxx
> alias eth0 via-rhine
> alias synth0 awe_wave
> alias sound-slot-1 sb
> post-install sound-slot-1 /bin/aumix-minimal -f /etc/.aumixrc -L
> >/dev/null 2>&1 || :
> pre-remove sound-slot-1 /bin/aumix-minimal -f /etc/.aumixrc -S
> >/dev/null 2>&1 || :
>
>
> On 2 Feb 2004 15:32:10 +1300, Cameron Kerr
> <cameron.kerr@paradise.net.nz> wrote:
>
> >Phisherman <nobody@noone.com> wrote:
> >> I have Fedora Core 1 installed. It is connected to a switch
> >> (hub). I know the hardware (NIC and cable) is properly
> >> connected because the PC (running Windows 98SE) was on the
> >> network last week.
> >>
> >> I verified the success of the driver install for the eth0. I
> >> looked at the bootup messages which shows
> >>
> >> eth0: VIA VT6105 Rhine-III at 0xf800, xx:xx:xx:xx:xx:xx
> >> (correct MAC address omitted)
> >>
> >> eth0: MII PHY found at address 1, status 0x786d advertising 05e1
> >> Link 45el
> >>
> >> I ran lsmod and this shows two entrys...
> >>
> >> via-rhine 14384 1
> >> mii 3736 0 [via-rhine]
> >>
> >> I ran ifconfig and this shows the correct HWaddr under eth0.
> >> And the following...
> >
> >But it didn't show eth0, which means the interface is not up. Try
> >using "ifup eth0", and if that doesn't work, you need to configure
> >the interface.
> >
> >> I tried running
> >> redhat-config-network
> >> and this shows a static IP address of 192.168.0.1 (which is
> >> actually the IP address of one of the Win98 machines already on
> >> the network!).
> >
> >Each IP address must be different and unique on the network.
> >
> >> Use DHCP [ ] is not checked. I tried checking DHCP, but this
> >> did not help.
> >
> >Did you have a DHCP server?
> >
> >If it still doesn't work, post the output of "ifconfig eth0".
> >Don't bother blanking anything out, it doesn't add anything to
> >this
> >conversation and can hide problems.

-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0.3

iQA/AwUBQB6eKLcoUT0UavXJEQJPHgCgsjjwlwe65najv0FIY1wKuZ lMnvAAoNEm
TG/tRKtRJanwBNqLFgHmFDnS
=ZN6n
-----END PGP SIGNATURE-----

I edited /etc/sysconfig/network-scripts/ifcfg-eth0 and changed

192.168.0.1
to
192.168.0.3

With this change, I was able to ping the other two (Windows 98SE)
machines on the local network. Plus, I can now ping these two Windows
machines from Fedora! Success!

Basically, I got the idea from
http://www.maths.cam.ac.uk/lapnet/rh7x/
which describes changing this script, which I did using VI, since I'm
not using a GUI.

I still don't "see" the Fedora machine in Network Neighborhood (am I
supposed to?), and still trying to figure out how to do a remote login
to Fedora from either Windows machines.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

"Phisherman" <nobody@noone.com> wrote in message
news:g27t10hth8u0nttfhiinlg5d0bsfcs5uhc@4ax.com...
> I edited /etc/sysconfig/network-scripts/ifcfg-eth0 and changed
>
> 192.168.0.1
> to
> 192.168.0.3

that's good. it has the same effect as configuring them manually like
i suggested in the last email. now it does the same thing through a
script. unique addresses are critical to IP functionality.

>
> I still don't "see" the Fedora machine in Network Neighborhood (am
> I supposed to?),

no. look up Samba. you need fedora to speak SMB as a client. if you
want the windows machines to see fedora, configure it as an SMB
server.

and still trying to figure out how to do a remote login
> to Fedora from either Windows machines.

for a real basic, low security option, try telnet 192.168.0.3 if your
telnet daemon is on.

good luck
oliver

-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0.3

iQA/AwUBQB6oz7coUT0UavXJEQJP3wCZAbIVwqLxeupgy2rxkP8vD/7bF18AoJlh
XKX5k0JzzwEPqsXpSxEo15xe
=7j1s
-----END PGP SIGNATURE-----