had to put this on the back burner for a while..
when connecting to sesame server from win2k machine server crashes with "segmentation fault"
i CAN run a sesame client locally ( on the server..).
server os redHat 8.
cmd line to start client is:
"sesame -client 10.0.1.15"
using local ip address-server is multi-homed.
thanks--joe

A lot of questions come to mind:

1. What versions of Sesame are running on the two boxes?
2. When does te server come down? Does it happen just as the client connects?
3. What command are you using to start the server?
4. What kind of name services are you using on the server?
5. Have you tried using the names as opposed to the IP addresses?
6. Are there any firewall issues? Are Sesame's ports (usually 20000:20001) being blocked?
7. Can you connect from any other remote computers?
8. Can other processes connect to this server (telnet, ftp, ssh, etc...)?
9. Are there any intervening devices between the two computers other than a hub or switch, such as a router or other device that might have a firewall?
10. Is there a core dump file on the server for Sesame?
11. Are you running X11 on the server? If not, are you starting the server using the -daemon flag?
12. If you are using an /etc/hosts file on the server, is the client's computer name in that file?
13. are there any log file entries from the time of connection on the server? On the client?
14. Can you see the connection taking place in the server's status window?

also---
just  switch, no router/firewall.
can connect via ssh/ftp/httpd--no problem.
ports not blocked AFAIK.
                     pls advise--thank you! joe

Thanks--the update did it!! joe