I had a problem similar to this awhile back. Everything looked like it *should* be
working but it
wasn't. Pinging the local ip was fine but pinging the other box was not. After much
fiddling of
bringing things up & down and many rebootings of the Windows box. We finally left it
set up so
that it *should* work, and then we.....rebooted the linux machine (mdk 7.1). For some
CRAZY
reason, this worked and all of a sudden we were able to ping accross the network. I"m
convinced it
had something to do with the network card and linux not brining it up properly
(despite its
claims).
I don't remember if the hub showed activity during our extensive setup/testing. My
tentative
explanation would only make sense if it didn't show it gonig from the linux-->windows
box, but i
really don't remember.
If i were you i would:
1. Configure everything the way it should be and if it doesn't work reboot both
machines to let
hte changes settle in. (yes, maybe it's enough to change or reload init levels on the
linux box).
Double-check everything (you didn't mis-type an ip address or netmask, did you? If
they're on
different subnets, you do have a gateway set up, right?)
2. Make sure everything on the physical level (cables - crossover vs straightthrough,
hub) and
data-link level (your network cards, etc) is set up properly. Verify things that you
already
"know".
3. Get another box in on hte action. Can you isolate the problem to a particular
machine?
4. Design some kind of a quasi rain dance and make sure it's relevant to your network.
Additional
rites and rituals might (not) help.
Good luck,
j
--- [EMAIL PROTECTED] wrote:
> cables pluged in properly
> they ping themselves but not the other machine
> yes, I had the LAN running but had to reinstall win95 and the lost connection,
> haven't been able to reconnect ever since
> yes, hub has LED but nothing happens when i ping the other machine
>
> Randy Kramer wrote:
>
> > Well, until someone else chips in:
> >
> > Try having each machine ping itself using its assigned IP address (like
> > 192.168.1.1 or whatever).
> >
> > All of your cables plugged in properly?
> >
> > Do you have a crossover RJ-45 cable by any chance that you could use to
> > connect the two machines, replacing the hub temporarily?
> >
> > Have you ever had the network working? Any other machines?
> >
> > Again, post your results, maybe someone else can help.
> >
> > PS: Do you have LEDs on the NIC cards? Do they indicate you have a
> > connection when the cables are plugged in through the hub (or the
> > crossover cable)?
> >
> > Randy Kramer
> >
> > [EMAIL PROTECTED] wrote:
> > >
> > > I tried that and each machine can ping itseld and gets responses, but can't
> > > ping the other machine. In other words, win95 can ping itself but not linux and
> > > linux can ping itself but not win95.
> > >
> > > Randy Kramer wrote:
> > >
> > > > Also, have each machine try pinging itself, in other words:
> > > >
> > > > ping 127.0.0.1
> > > > ping localhost
> > > >
> > > > If those don't work, there is something wrong with the networking
> > > > software on each machine. (I can't help you with the next step, but
> > > > someone can -- post your results.)
> > > >
> > > > Randy Kramer
> > > >
> > > > Dan Swartzendruber wrote:
> > > > >
> > > > > At 09:24 AM 4/3/2001 -0700, [EMAIL PROTECTED] wrote:
> > > > > >i am tryint o reconnect my home LAN but I can't getmy machines to ping
> > > > > >each
> > > > > >other. Everything is fine. IP configuration is right, HUB is working,
> > > > > >cables
> > > > > >are new and connected. Don;t know what the problem may be?
> > > > >
> > > > > what does 'route -n' show? i've had problems in the past with changing IP
> > > > > addresses via linuxconf and having the ifconfig info change, but not the
> > > > > routing table.
>
>
__________________________________________________
Do You Yahoo!?
Get email at your own domain with Yahoo! Mail.
http://personal.mail.yahoo.com/
