Yes turn off the proxy server part and put a check in the no proxy box
in SetiDriver. That way the machine will connect to Berkeley on its
own and no more dupes.
The more important question is why do you have 2 SetiQueues and why
are they sending data to each other?
I use setiQueue on one machine and point the other machines to it, I
have 15, and they all get their workunits from the one SetiQueue. It
then connects to Berkeley when it is supposed to according to the
configuration I setup.

On Tue, 13 Jan 2004 14:56:31 GMT, "==Blitz==" <bliz@bliz-nospam.com>
wrote:

Hi, I have been using SETI CLI 3.3, SETI Driver 1.6.3.5, and setiqueue
3.3.02b on two pcs for over a year. Recently, the primary setiqueue started
rejecting the results  from the second setiqueue. The message in the primary
setiqueue is "Duplicate result from PC2 ignored". This message is presented
on any result from PC2, however, PC2 is able to download results and process
WUs.

The results are building on PC2 but I am unable to transmit them. Is there
an answer for this problem?

Thanks