gogan@bbs.acs.unc.edu (Jim Gogan) (02/14/91)
Is anyone aware of any problems associated with loading multiple frame formats on a single Ethernet adapter in a NetWare 386 3.1 server? I would like to support both Novell's version of 802.3 (default) and Type 2 Ethernet (with type=8137) using the same adapter to handle the routing between some folks that can't switch over and those that have. According to the documentation (as well as practice prior to yesterday), it can be done with the following commands: LOAD NE2000 port=320 int=2 frame=ETHERNET_802.3 BIND IPX to NE2000 net=20705 LOAD NE2000 port=320 int=2 frame=ETHERNET_II name=type2 BIND IPX to type2 net=61325 No problem entering these commands to the 386 console; uses NE2000 module re-entrantly. HOWEVER.................................. yesterday when we configured a cisco router to route Novell IPX (along with IP) (between an Ethernet and a T1 line) --- using "novell encapsulation novell-ether" (the default) and Novell network address 20705 (see above) on the Ethernet interface --- when it used the above 386 server for routing, all the Ethernet based servers reported router configuration errors (thinking that somebody out there with 20705 should be 61325). If we down the cisco, the errors stop. ALSO, if I unbind the Ethernet Type 2 frame from the 386 server above, the errors stop. As I say, we had no Novell router configuration errors on other servers till we brought the cisco into this configuration, and yet the problem only exists with the dual frame types on the 386 server adapter. Anyone else seen this? Any thoughts? Are there any known problems with the multiple frame formats on a single adapter in 386 3.1 (which would be too bad, 'cause that's a nice feature, especially for some protocols that might need SNAP!). -- Jim Gogan (gogan@samba.acs.unc.edu) Networking Systems University of North Carolina at Chapel Hill