Path: utzoo!attcan!uunet!fernwood!portal!cup.portal.com!wcc
From: wcc@cup.portal.com (wcc - usa)
Newsgroups: comp.protocols.appletalk
Subject: Re: Running CAP  with K-star 8.0
Message-ID: <31552@cup.portal.com>
Date: 9 Jul 90 00:45:58 GMT
References: <544@synopsys.COM> <545@synopsys.COM>
Organization: The Portal System (TM)
Lines: 44

> After more testing I noticed that if I put 
> 
> at-rtmp         201/udp                         # udp: rtmp
> at-nbp          202/udp                         # udp: nbp
> at-echo         204/udp                         # udp: echo
> at-zip          206/udp                         # udp: zip
  ^^^^^^
Where'd you get this from? It's "at-zis", not "at-zip". Grep the CAP 
sources for "zis" and zip" just to make sure.

Note that it doesn't really matter which socket range you use (the "old"
768-series or the "new" 200-series), but the only essential matter is that
ALL devices using these sockets are using the SAME ones. ALL CAP hosts and
ALL encapsulating gateways.

If you want to use the 200-series, you have to reconfigure the gateway
(kbox?) to use the 200 series as well.

Note it is possible (likely - it happens a lot) that the Sun's "portmapper"
has grabbed the 768-series ports. If you start aufs early enough in your
boot sequence (before portmapper) you can beat it to them. Until the next
time someone changes your rc.local, that is.

> in the YP map more /etc/services atistest would report:

> nbp register error because: couldn't register name - is atis running?

> If services are removed and atis is restarted I get:

> NBP status done: found -536872120
> Okay

Meaning your kbox is running the 768-series.

Tom Evans
wcc@cup.portal.com
Webster Computer Corporation
Suite J, 2109 O'Toole Ave. San Jose, California 95131-1303
Ph (408) 954-8054  FAX (408) 954-1832

Head Office
tom@wcc.oz.au, multigate@wcc.oz.au
1270 Ferntree Gully Rd. Scoresby, Victoria, Australia
Ph 61 3 764-1100  FAX 61 3 764-1179