Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!aplcen!samsung!zaphod.mps.ohio-state.edu!wuarchive!kuhub.cc.ukans.edu!zeus.unomaha.edu!network
From: network@zeus.unomaha.edu
Newsgroups: comp.dcom.lans
Subject: IPX packets going through one server to get to another
Message-ID: <2868.271e3313@zeus.unomaha.edu>
Date: 19 Oct 90 04:56:18 GMT
Lines: 22


   We have multiple Novell file servers on the campus, nearly all v2.15
and all individualy bridged from our Ethernet backbone. 
   I did some packet tracing with our network analyzer and found that when
a station on one bridged network logged in to a server on another bridged
Novell network, that they would pass ALL of their IPX traffic via a third
file server which is also bridged from the backbone.  It would be a different
'third' file server at different times.
   The packets had their final destination within the packet, but their
destination address in the packet header was allways the 'third' file server.

   Of course this is bad.  Traffic goes all over the place to get to
it's destination.  Other traffic is bridging fine.  We use Cabletron
bridges.  Is there something with Netware IPX that causes this?
Has anyone else seen this problem?  Don't you wish Novell had
decent support ;-)

Steven Lendt
Network Manager
University of Nebraska at Omaha

Internet: NETWORK@ZEUS.UNOMAHA.EDU          Bitnet: NETWORK@UNOMA1