Yann Ouellet wrote:
>
Your quoting is broken... fixed.
> Pierre Fortin wrote:
> > Do you even have basic connectivity...? Can you ping 192.168.0.1? I know
> > nothing of ICS; but does it really support forwarding of DNS (docs could be
> > wrong, or you may need another option)? Or, should you tell your Linux box
> > the
> > ISP DNS addresses?
> >
> > If the ping works, try setting the ISP DNS addresses. If not, fix that
> > first.
> >
> > HTH,
> > Pierre
>
> I tried the ping a few minutes ago and don'T have the "basic connectivity so
> i started reading the network HOWTO to setup my network so that i can see my
> windows server'S shared files...
OK... from your previous msgs, you have this:
----z---modem/WinME/eth(192.168.1.1)==[10[0]baseT]==(192.168.1.2)eth/[Linux|Win]
If this works under all Win, then physical connectivity is fine. If not, are
you sure the link is up? Are you using a hub/switch or cross-over cable? For
completeness, a straight cable won't work (need 2 + hub/switch).
You're wasting your time with the shared file stuff until you have basic
connectivity working. If your h/w is setup correctly, try in this order:
/sbin/ifconfig
and confirm the interface is up and configured as expected.
ping -r 192.168.1.1
This will bypass the route table which may be missing or wrong. You should see
the link lights flicker. If not, some other research will be required. If you
"see" the Linux packets on the wire, focus on the WinME setup.
/sbin/route
should give at least the first 2 entries:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 * 255.255.255.0 U 0 0 0 eth0
127.0.0.0 * 255.0.0.0 U 0 0 0 lo
default gateway 0.0.0.0 UG 0 0 0 eth0
If the default is missing... in your case, issue:
route add default 192.168.1.0 netmask 255.255.255.0 gw 192.168.1.1
and also fix /etc/sysconfig/network
Now, if:
ping 192.168.1.1
still fails, then focus on the WinME setup; sorry, I can't (won't :) help with
that.
Pierre
