Title: | DEChub/HUBwatch/PROBEwatch CONFERENCE |
Notice: | Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7 |
Moderator: | NETCAD::COLELLA DT |
Created: | Wed Nov 13 1991 |
Last Modified: | Fri Jun 06 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 4455 |
Total number of notes: | 16761 |
Hello, I need a clarification about the DECswitch 900 EF and RAW 802.3 protocol. A customer has the following config: a novell fileserver with an FDDI interface a laptop novell client on the Ethernet a DECHUB900 V3.1.0 with a DECswitch 900EF V1.4.0 the switch is connected to the FDDI ring and so is the NOVELL server. on one of the Rj45 Ports they have connected the laptop. They can connect to the NOVELL server from the Laptop if they use frameformat 802.2 in the NET.CFG on the laptop. They can't connect if they use frameformat 802.3 on the laptop. According to the customer the "RAW 802.3" switch on the bridge does not help ? What's the deal ? Thanks OTTO
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
2253.1 | NETCAD::ANIL | Wed May 10 1995 21:38 | 15 | ||
The same encapsulation must be used on all IPX end stations within an IPX network. My guess is that the Novell server on the FDDI is using 802.2 format. If it were using SNAP format, and the Ethernet lapto were doing Ethernet v2, then things would also work. Finally, if the Ethernet laptop is using raw 802.3 (Not recommended) and the FDDI server is using SNAP, then it would work. As you can see, there are 2 FDDI formats and 3 Ethernet formats. Novell decided not to repeat the "raw" mistake on the FDDI. Your best bet is to use 802.2 throughout; OR Ethernet v2 on Ethernet and SNAP on FDDI. Basically, while it may be possible to use a router to convert encapsulations between IP networks, *within* one (inside the same bridged/switched domain) the same encapsulation must be used. Anil |