SETIQUEUE problems

[BofRA]

Ok I am trying to point my work queue to my home queue. The work queue keeps coming up with cannot conect to berkeley. Why is it not connecting with my home queue?

I put in the work queue my home ip as proxy with the port number. I can connect to the html pages of my home queue so I know that is not the problem. Are there any special settings I have to set to do this?

Oh yeah here is the link to my home queue: http://68.106.180.243:81/default.htm

 

[Confused]

It could be the firewall.

I have the same problem here at work. I can browse to the HTTP pages of the queue, but my work SetiQueue says "cannot connect to berkeley" as well


Garry

 

[TofBnT]

I wish you could get that fixed, it would make things so much easier.

 

[bunker]

In the "Connection Type" drop-down, select "WinINet Proxy"
Enter your home IP in the "Proxy Server" field
Enter 5517 in the "Port # field (or whatever port you're using at home)
press "Ok"
drink a cold :beer:

I think that first line could be the problem. It defaults to WinSock Direct

 

[B52GUNR]

I know to get my work queue running I had to create a SSH tunnel to my FreeBSD box whch forwarded to the Starfire Queue I use. I couldn't get any other combination of proxy settings to work.

 

[Tarca]

Gee Bunker where have I seen that info before LOL

 

[bunker]

Originally posted by: Tarca
Gee Bunker where have I seen that info before LOL

Hee hee

I was gonna give Eric credit in my post but I can't remember his AT name as he's hardly ever posted here!

 

[Thoreau]

To the OP of this thread...

set the IP and subnet to 0.0.0.0/0.0.0.0 (Settings -> Queue Server)

I had this same issue (kinda) in my home network which has the SETIQueue box sitting in a DMZ (network ID 10.10.0.0) and two of its clients on another network ID (192.168.2.0). Basically, the http server in SETI Queue accepts and listens on all interfaces/IPs by default. The queue server itself is manually bound to a specific IP, which the above fix resolves.

 

[Confused]

Thoreau,

I feel that it is not that. My queue is set up like this (as it is a public queue), but it's only my work clients that won't connect, and with the same error message.


Garry

 

[BofRA]

Thoreau,

I will try that on Monday. But I think it has to do with Windows Proxy 2.0

Thanks all for the help. I will just have to keep sneakernetting.