RE: appletalk stuff [7:69961]

2003-06-03 Thread Priscilla Oppenheimer
It's funny that we are seeing this message after seeing all those complaints
about the CCDP recert exam including AppleTalk! :-)

=?WINDOWS-1255?Q?=F7=E5=F8=EF__=EC=E1 wrote:
 
 Does anyone have an idea on that:
 we use 7200 in the center of a big bay-networks routers
 we use ipx , ip and appletalk
 ip , ipx works fine in FR/PPP links and OSPF etc..
 apple talk zones and routing are shown ok on the macintosh
 machines

All zones are showing up on the Macs? That's a good sign. 

Routing wouldn't show up on the Macs, but do all routes show up on the
routers?

Most AppleTalk problems are related to routing, not finding services. To
avoid problems with split horizon, be sure to use Frame Relay subinterfaces.

 there is appletalk services advertised on PPP links

AppleTalk services are never advertised. Users look for them.

 but they are not advertised on FR links
 routing is RTMP , zones are ok on FR links
 just the macintosh servers does not show up on FR !!

Do you mean that servers don't show up when users who are across the Frame
Relay network try to find them? That is indeed strange.

 no access-lists of any kind

Hmmm. It does seem like an access list problem, though

It also sounds like it could be a duplicate network number. If this is a new
or updated design, it's pretty common to mistakenly reuse an AppleTalk cable
range, or have overlapping ranges. Other than misconfigured access lists,
that's the only time I've ever seen such a strange result as what you're
seeing, if I understand what you're seeing (zones and routes OK, but users
can't find services).

If it's been upgraded to AppleTalk over IP and Mac OS X, then it's a whole
other story. I think Mac OS X uses Service Location Protocol, which is
multicast based and requires IGMP and an IP multicast routing protocol to be
working correctly.

Is this a new problem? What changed? What version of Mac OS are the users
using? Is this pure AppleTalk or AppleTalk over TCP/IP?

I might be willing to help if you could send more info on what's happening,
version numbers, config, etc.

Priscilla


 
 




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7i=70027t=69961
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]


Re: appletalk stuff [7:69961]

2003-06-03 Thread Scott Nelson
Also, are you doing it via one arm routing or do you have separate
interfaces in each vlan?
( fa0/0 in vlan or lan x, fa0/1 in vlan or lan y, etc., etc. )

http://www.cisco.com/warp/public/779/smbiz/service/knowledge/wan/subifs.htm

You should definitely use sub-interfaces though..  ( Reference above )

Scotty



Priscilla Oppenheimer  wrote in message
news:[EMAIL PROTECTED]
 It's funny that we are seeing this message after seeing all those
complaints
 about the CCDP recert exam including AppleTalk! :-)

 =?WINDOWS-1255?Q?=F7=E5=F8=EF__=EC=E1 wrote:
 
  Does anyone have an idea on that:
  we use 7200 in the center of a big bay-networks routers
  we use ipx , ip and appletalk
  ip , ipx works fine in FR/PPP links and OSPF etc..
  apple talk zones and routing are shown ok on the macintosh
  machines

 All zones are showing up on the Macs? That's a good sign.

 Routing wouldn't show up on the Macs, but do all routes show up on the
 routers?

 Most AppleTalk problems are related to routing, not finding services. To
 avoid problems with split horizon, be sure to use Frame Relay
subinterfaces.

  there is appletalk services advertised on PPP links

 AppleTalk services are never advertised. Users look for them.

  but they are not advertised on FR links
  routing is RTMP , zones are ok on FR links
  just the macintosh servers does not show up on FR !!

 Do you mean that servers don't show up when users who are across the Frame
 Relay network try to find them? That is indeed strange.

  no access-lists of any kind

 Hmmm. It does seem like an access list problem, though

 It also sounds like it could be a duplicate network number. If this is a
new
 or updated design, it's pretty common to mistakenly reuse an AppleTalk
cable
 range, or have overlapping ranges. Other than misconfigured access lists,
 that's the only time I've ever seen such a strange result as what you're
 seeing, if I understand what you're seeing (zones and routes OK, but users
 can't find services).

 If it's been upgraded to AppleTalk over IP and Mac OS X, then it's a whole
 other story. I think Mac OS X uses Service Location Protocol, which is
 multicast based and requires IGMP and an IP multicast routing protocol to
be
 working correctly.

 Is this a new problem? What changed? What version of Mac OS are the users
 using? Is this pure AppleTalk or AppleTalk over TCP/IP?

 I might be willing to help if you could send more info on what's
happening,
 version numbers, config, etc.

 Priscilla




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7i=70044t=69961
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]