WIECEK%wharton@UPENN.EDU (Sophie L. Wiecek) (02/05/90)
Hi all, Thanks for all your help with my network problem. A couple of you wrote about experiences where disconnecting a second logical LAN eventually causes the first to fail intermittently. Well, I re-connected my Western Digital LAN B (to just one workstation) and that took care of things -- now both A and B are running fine. Here's a question, though -- at one point in this mess I accidentally connected my 3Com Etherlink segment to the WD card in the server -- and when I tried to connect, using the 3Com IPX, it worked! Is this usual? I was pretty confused. (I've since put everything in order, of course.) Thanks Again... Sophie Wiecek The Wharton School -- U of PA
ACM@NAUVAX.BITNET (Anthony C. McCracken) (02/07/90)
Sophie, this seems perfectly normal to me. Ethernet is Ethernet, the
cable doesn't care what brand of card sent the packet. For example, not too
long ago, I ran a LAN that had two servers on the same cable. One was running
an NP600a the other was running A 3Com 3C505a. The workstations were running
NI5010s, NI5210s, 3C501s and WD8000 series adapters. As long as each
workstations shell was configured for the proper board, everything worked just
fine. Every workstation could see both servers. What really strikes me as odd
though, is the idea of putting in two boards in one server and ECONFIGing one
of them. Then putting both boards on the same cable. Now any workstation on
the ethernet whether or not they are ECONFIGed themselves, can see the server.
I find that odd, but it does work.
TonyJRD@USU.BITNET (Joe Doupnik) (02/07/90)
Two Ethernet boards in one server, one ECONFIG'd the other not.
No problem. Even if the same network is specified the server is doing
the bridging. Wierd, not advised, etc, but it works (did it here to bridge
IEEE 802.3 to ECONFIG'd Ethernet systems a while ago). Outsmarting a not
overly bright but picky internal bridge.
Joe D.