newsreader wrote:

"Martin" <ml_news@ddnospamddml1dd.co.uk.dd> wrote in message
news:6VH9b.1057$DM5.10254@newsfep4-glfd.server.ntli.net...

newsreader wrote:

[snip]

What else has changed in any way?

Damnifiknow.  Probably some Windows Updates from MicroSloth 
but nothing else common to both affected systems.  This setup 
has been running fine for months with virtually no changes.  

Ummmmm ... did you mean "Windoze Update$ from Micro$loth"?  <g> 

[snip]

Thoughts anyone?

[snip]

Some more data points:
S@h (NT CLI 3.03) has no problem connecting directly with 
Berkeley if I remove the proxy info for SETI Queue.  

On the SETIspy Client setup, uncheck "Hide Client".  In 
addition, click "Configure" and then under "Client control", 
uncheck both "Hide client after (re)start" and "Restore client 
minimized".  You might also have to add "-verbose" to the 
"Client parameter(s)" field.  Click "OK" and then click 
"(Re)start" on the "Client" frame.  

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

SETI Queue shows no evidence of connection attempts from 
the affected machines in its logs.  

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

[snip]

Good luck,

Thanks!
Bob

-- 
Martin G. Diehl

Reality -- That which remains after you stop thinking 
about it.  

All replies and comments accepted and considered.  
Adoption of your suggestions are at my sole discretion.  
Award criteria are unpublished and are considered to 
be a trade secret.  As such, awards for your responses 
cannot be guaranteed.  Incoming flames may be stored 
for use during severe winters or may be circulated for 
deep analysis, peer review, and/or literary criticism.