"Michael D. Ober" <obermd-@-alum-mit-edu-nospam> wrote

These messages are coming from the CLI itself.  Make sure SETI

Driver's

proxy settings are correct for the campus lan.  (It sounds like they

should

be clear)  Also, try pinging "shserver2.ssl.berkeley.edu" from the

windows

command line.  This is the data server's name.

Mike Ober.

Thanks, but I got it to work through an not-blocked port...