loganj@yvax.byu.edu (10/16/90)
CAP/UAB+ poblem: Can't see to get atlook (CAP) to work right on our DS3100. CAP/UAB+ installed per README.FIRST. UAB+ seems to start up okay with either of the following entries in "bridge_desc": bert.cs.byu.edu [elap,se:0] mkip [0] or bert.cs.byu.edu [ethertalk,se:0] none [0] Must I use the second entry if we're not running KIP on the Kenetics Box? I think that UAB is working okay. When I run it with diagnostics I see that it recognizes all of our AppleTalk zones with messages like: uab: 9:07:51 10/15/90 insert for CS APPLETALK [7,0] uab: 9:07:51 10/15/90 ZIPPED: from 0.1.184 network 0.128 for zone CS APPLETALK And it produces the following "atalk.local" file when "mkip" is specified in "bridge_desc": 0.1 1 CAMPUS ETHERNET 0.1 1 127.0.0.1 But, that "127.0.0.1" doesn't seem right to me. The host system (bert) is a DecStation 3100, and it's ip number is "128.187.2.20". Do I need to modify this file for CAP? The Kenetics box (3.0) that we're using is NOT running KIP, and it's setting are as follows: Gateway name: 080880BB80DC80BB020F Appletalk side: Zone name: CS APPLETALK Net # 128 Node 220 Ethernet side: Zone name: CAMPUS ETHERNET Net # 1 I think that the last 8 digits of the Gateway name are the IP number on the ethernet side, which is 128.187.2.15. I was expecting to see part of that number in the "atalk.local" file produced by UAB. The previous 8 digits are the IP number on the Appletalk side (128.187.128.220). Anyone know what the first 4 digits are? When I run atlook it only shows the following two lines but it doesn't see any of our LaserWriter printers: abInit: [ddp: 0.01, 1] starting Looking for =:=@* ... Any suggestions? I can supply plenty of diagnostic output from UAB if that would be helpful. Thanks and Regards, jim logan loganj@yvax.byu.edu loganj@byuvax.bitnet