"Martin G. Diehl" <mdiehl@nac.net> wrote in message
news:3F69EC8C.D266E71@nac.net...

newsreader wrote:
Look for error messages from the S@H CLI window.

Been there, done that.  The only error message is the one included in the
first post.  The clients simply don't see the queue server as if they
weren't connected.  The browser sees it,  port scans see it, but the S@h
clients don't.

In each machine's firewall settings, you may have to identify
those IP addresses on your LAN as trusted.

Not it.  There have been no changes to the firewalls (where present).

They're working now with the domain address listed for the proxy instead of
the explicit IP in SETI Driver but there are other machines both on and off
the LAN still chugging along happily using the same setup but with the IP in
the proxy just like the two problem machines had before...  Go figure.

"If it works, don't fix it."