Some specs first:
Server: RH7.3
Client: Any Mac with Network Browser (sys 9 etc)

The problem:
Can't connect to atalk service via IP remote, can only get to it through 'localhost' in the echo'd apletalk services on the same hub. This server will be moved out to a far out remote location, where it won't show up on the local network anymore, so getting to atalk through the IP is going to be required.

I bet this has to do with the firewall on RH, but I have added the proper ports for atalk, so I can't figure out why it isnt allowing it :\

This is the ipchains listout:
Chain input (policy ACCEPT):
target prot opt source destination ports
ACCEPT udp ------ ns1.uswest.net anywhere domain -> 1025:65535
ACCEPT udp ------ phnxpop1.phnx.uswest.net anywhere domain -> 1025:65535
ACCEPT udp ------ 192.168.3.1 anywhere domain -> 1025:65535
ACCEPT tcp -y---- anywhere anywhere any -> http
ACCEPT tcp -y---- anywhere anywhere any -> https
ACCEPT udp ------ anywhere anywhere any -> https
ACCEPT tcp -y---- anywhere anywhere any -> ftp
ACCEPT tcp -y---- anywhere anywhere any -> ssh
ACCEPT tcp -y---- anywhere anywhere any -> at-rtmp
ACCEPT tcp -y---- anywhere anywhere any -> at-nbp
ACCEPT tcp -y---- anywhere anywhere any -> at-echo
ACCEPT tcp -y---- anywhere anywhere any -> at-zis
ACCEPT udp ------ anywhere anywhere bootps:bootpc -> bootps:bootpc
ACCEPT udp ------ anywhere anywhere bootps:bootpc -> bootps:bootpc
ACCEPT all ------ anywhere anywhere n/a
REJECT tcp -y---- anywhere anywhere any -> 0:1023
REJECT tcp -y---- anywhere anywhere any -> nfs
REJECT udp ------ anywhere anywhere any -> 0:1023
REJECT udp ------ anywhere anywhere any -> nfs
REJECT tcp -y---- anywhere anywhere any -> x11:6009
REJECT tcp -y---- anywhere anywhere any -> xfs
Chain forward (policy ACCEPT):
Chain output (policy ACCEPT):


The ipchains is saved, and pulls up on reboot, so those ports should be allowed to be used.

Am I missing something? is there some obscure undocumented port that is preventing remote ip atalk connections? Nothing in the atalk config files have any sort of settings to prevent remote connections.

I CAN connect and do all the atalk things to a home directory, but only through the local network, by clicking on the server in the displayed "AppleTalk" network. That as I said, will be useless when the machine is moved off this hub and into a hosting facility ... grrr.

Please help, if anyone knows... I am stumped at this point.

After starting at endless logs on startup, I noticed an IP line with a :548 on the end of it in the atalkd startup area...

sooooo... I added port 548 to the ipchains, and now it all works!

Ok, so, ignore my previous post, I was just being blind. After digging into the "/etc/services" file, sure enough ... port 548 is the listen on IP port for appletalk file services. Don't know why i didnt see it before. I really hate answering my own questions ... makes me look really stupid... I'm not! Really!