🚀 go-pugleaf

"Richard John Cavell" <rjcavell@student.unimelb.edu.au> wrote in message
news:Pine.OSF.4.10.10201252357460.19972-100000@cassius.its.unimelb.edu.au...
> Okay.
>
> I have two quite similar computers, both Pentium 2s, 128 Meg RAM.  One has
> Windows 2000 and is meant to be a server of sorts.  The other has Windows
> 98 and is meant to be a slave/client.
>
> The win2k machine has a 3Com LAN card installed.  This is connected by 2
> feet of cable to the win98 machine's intel LAN card.  The drivers for the
> cards are setup correctly.
>
> On Win2k, I have a LAN icon with a red cross, which means that it is not
> working.  I mouse over it and it says 'Local Area Connection Network cable
> unplugged'.  The machine has Client for Microsoft networks, and TCP/IP
> installed and checked.
>
> On my Win98 machine, I have Client for Microsoft Networks and TCP/IP
> installed.
>
> On the Win98 machine, when I open Network Neighbourhood and double-click
> 'entire network', it gives me:
>
> Unable to browse the network.  The network is not accessible.  For more
> information, look in help.
>
> On my Win2k machine, My Network places simply has nothing in it.
>
> On both machines, they are configured to be in workgroup called
> 'WORKGROUP', no domain.  They have separate names.
>
> The cable certainly is plugged in.  It's possible that the cable is
> faulty, but I doubt it since it's worked in the past.
>
> Any ideas?
>
Firstly it sounds like your NIC/Cable isn't set up correctly.  What kind of
cable are you using?   Cat5's if you're plugging point to point you need a
crossover cable, Coaxial need 50Ohm terminators.  (Cat5's have telephone
looking plugs (RJ45), coax ones look a bit like your TV antenna (BNC)).  You
probably think the cable worked  because in the past because (Cat5) it was
connected to a hub, it (Coax) was on a larger network with terminator plugs
on the end.

Then once you get the cable working [No ugly network cable unplugged icon]
and it doesn't work :- try setting the IP address for both computers to be
on 192.168.0.x or any other local sub (eg 10.0.0.x) but on the same ones.

Then you'd probably get the $IPC problem, but we'd come back to that one.

Cheers,
John who is not awake on a Saturday morning to do more work...argh