Xref: utzoo comp.dcom.sys.cisco:1317 comp.protocols.appletalk:6091 comp.dcom.lans:8384 Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!Firewall!genesis!kdenning From: kdenning@genesis.Naitc.Com (Karl Denninger) Newsgroups: comp.dcom.sys.cisco,comp.protocols.appletalk,comp.dcom.lans Subject: CISCO Brouters and Appletalk Phase II Message-ID: <1991Jun15.193153.18320@Firewall.Nielsen.Com> Date: 15 Jun 91 19:31:53 GMT Sender: news@Firewall.Nielsen.Com (Usenet News) Organization: AC Nielsen Co., Bannockburn IL Lines: 51 Nntp-Posting-Host: genesis.naitc.com Hello! Has anyone seen this? We have a CISCO MGS with firmware 8.1(14) and bridging support. We're trying to move some Macs onto their own cable, and having problems. With the bridging turned on, and multi-cast support enabled for bridging, I can see and use the printers in the printer zones. Zones come up in the chooser normally. The printers are behind two MAC Routers (they're on Localtalk), while the servers are on Ethernet on one of the other segments. When I try to select the server zone, I can't see any of the Appletalk servers! Our sniffer says the server is seeing the inquiry packets and replying -- but the MAC never sees the reply. The CISCO says that no packets are being forwarded to the interface which has the MAC on it! If I plug the MAC into the other side for a moment, the servers appear. Then, if I replug into the OTHER side (the CISCOized side) they stay in the chooser, and can be selected! That is, once I have communications with the servers it does not appear that I lose it even if I switch back to the other side of the router! Very, very strange. The CISCO is routing XNS and IP, and bridging the rest. The config looks like: Interface Ethernet 0 ip ... bridge-group 1 Interface Ethernet 2 ip .... bridge-group 1 ..... bridge 1 protocol dec bridge 1 multicast-source ..... I tried IEEE bridging without change... Any ideas? I'm running out fast! :-) -- Karl Denninger - AC Nielsen, Bannockburn IL (708) 317-3285 kdenning@nis.naitc.com "The most dangerous command on any computer is the carriage return." Disclaimer: The opinions here are solely mine and may or may not reflect those of the company.