Right now I am using the working (3rd) linux box for writing this email (ganda pala ng
KDE2). It is connected to a WAN on a DHCP mode. The hub is uplinked to the WAN.
Anyway, to make the troubleshooting simplier, we set the IPs of hte problematic
workstations to static.
I ping problematic1 from problematic2. Failed. They are using static IPs on the same
subnet mask (192.168.1.x /16). Ayaw talaga! Pero kayang iping yung local IP address
nila o yung loopback.
Somebody told me about the cable and the hub. I checked it out by transferring ports
and cables using hte workstation that is working. All successful.
Here's another development. We tried configuring the internet connection sharing of
mandrake (we revert back to mandrake for the problematic1) using DrakConf. It detected
a firewall (its IP is still static). The static IP does not belong to the production
WAN, is it possible that it detected the firewall (i have no idea)?
Thanks.
On Saturday, March 31, 2001 at 06:22:09 PM, [EMAIL PROTECTED] wrote:
> On Sat, 31 Mar 2001, [EMAIL PROTECTED] wrote:
>
> > The hub and the cables are okay. I mentioned that I have a 3rd Linux
> > box that is working already (connected to the WAN using DHCP).
> >
>
> How did you verify that the 3rd linux box is ok? Who did you ping? The
> two problematic ones? And if you did, did it work?
>
> > I can ping the local address. One of the problematic boxes is a dual
> > boot with win98. So I booted it in win98 then the other one was booted
> > in linux. Both are using static IPs (x.x.x.1 & .2 of the same subnet
> > mask). No luck!
>
> Again, i would venture to say that this is a problem with your wires (if
> not hub, if not, the sockets of your hub, or your NICs). Try doing this
>
> 1. Get a pair of cables that are _known_ to be good, and get a hub
> that is known to be good, and use those to connect the two boxes. Make
> sure the sockets fit the plugs securely (a poorly inserted UTP plug will
> give you erratic connections if ever they connect).
>
> 2. If they still don't connect, yank out the NICs from the PCs with known
> good NICs and install them to the linux boxes. If they are of a different
> brand you may need to reconfigure linux via kudzu.
>
> This way you are sure to isolate the problem if it's the wires, hub, or
> NICs. This is not a linux problem, it's a problem with hardware and
> communications. If your hardware card is not supported by linux, you
> won't even be able to get eth0 up, and all you will have is the loopback
> lo (verify using ifconfig).
>
> If you don't have access to known good hardware, you're out of luck. THe
> first rule of troubleshooting is to isolate each part of the network with
> previously known good parts, and go forward from there.
>
> > Is there a possibility that Redhat was installed with a default
> > firewall in it? I installed using the costumize mode.
>
> no.
>
> >
> > As far as I know, if you have to IPs of the same subnet they should
> > ping each other. Tama ba? Kasi nag-implement na ako ng RH sa opisina,
> > gumana. Di ko talaga mifigure out kung saan ako nagkamali.
> >
> > T
>
> Yes.
>
> For curiosity's sake, could you post to the list a dump of :
>
> 'lsmod'
> 'lspci'
> 'ifconfig'
> 'route -n'
> 'cat /var/log/messages | grep eth0'
>
>
> _
> Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph
> To leave: send "unsubscribe" in the body to [EMAIL PROTECTED]
>
> To subscribe to the Linux Newbies' List: send "subscribe" in the body to
>[EMAIL PROTECTED]
>
>
----
www.edsamail.com
_
Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph
To leave: send "unsubscribe" in the body to [EMAIL PROTECTED]
To subscribe to the Linux Newbies' List: send "subscribe" in the body to
[EMAIL PROTECTED]
