Does anyone know what the server and port for the "default WinInet" setting in Seti Q are?

[dxkj]

Im trying to figure out what the server address and port that Seti Q uses when you select default Wininet as the connection type. Anyone know?

 

[Confused]

It will be a direct connection to Berkeley, using shserver2.ssl.berkeley.edu and port 80



Confused

 

[dxkj]

Ok thanks


Now to figure out why the firewall allows that address, but not my IP address set to port 80 Queue.

 

[Confused]

Try a WinSockProxy rather than WinInetProxy


Confused

 

[dxkj]

Is a username and password usually required for a socks proxy? I think I tried it before without either and it ended up not working.

 

[Rattledagger]

Actually, according to the documentation, "default WinInet" is the proxy-settings to Internet Explorer.

As for socks, you don't need a username/password.

 

[dxkj]

Ok its not working with socks. Do I need to change a setting on my SEti Queue to say that it is a socks server?


ERROR "Can't connect to SOCKS server"

 

[dxkj]

Originally posted by: Confused
It will be a direct connection to Berkeley, using shserver2.ssl.berkeley.edu and port 80



Confused

I've tried connecting to that and it doesnt work, by typing in that exact address. and port 80. So that leads me to believe that isnt the exact server I connect to? Either that or something weird is going on.

 

[dmcowen674]

Originally posted by: Confused
It will be a direct connection to Berkeley, using shserver2.ssl.berkeley.edu and port 80



Confused

Try setting it to Winsock proxy using the above.

 

[Smoke]

The situation here is there exists an installed SetiQueue behind a firewall. The SetiQueue works. It is serving other computers behind the same firewall.

The SetiQueue can upload and download WUs from Berkeley.

BUT, no one outside of the firewall can SEE the SetiQueue.

Assume: You have no control over the permissions for the firewall.

Question: How can this be? Is there a work-around to SEE this SetiQueue from outside of the firewall?

 

[soni]

Greg !
The Firewall blocks the port that the clients connects to (default 5517), so outside (though the firewal) clients wont connect, but the setiqueue uses port 80, and thats allowed from inside out. (Outside will usually see the webserver)..

 

[Smoke]

Originally posted by: soni
Greg !
The Firewall blocks the port that the clients connects to (default 5517), so outside (though the firewal) clients wont connect, but the setiqueue uses port 80, and thats allowed from inside out. (Outside will usually see the webserver)..

So what's the fix ... if there is one? The way for "us", outside of the firewall, to see this SetiQueue?

 

[Confused]

I don't believe there will be a fix for external people to see inside...that's what the firewall is there for. Unless you have access to the firewall and can open up the port for incoming traffic, and direct it to the right PC, then that will not be possible.


Confused

 

[Smoke]

Thanks Garry, that is what I've been thinking all along. There is no fix unless you actually "hacked" the firewall which is not what we are after in this situation.

So now we wait for permission from the "higher ups". Let's keep our fingers crossed.

 

[Confused]

Greg, YGPM


Garry

 

[dxkj]

Being able to see the setiQ from outside isnt really concerning me, its not being able to connect to a setiQ on the outside from the inside that is confusing me.


SetiQ Inside can conncet to berkley and service the other machines inside, but it cant conncet to my Shale SetiQ outside even when set to port 80. Thats the part that doesnt make sense to me.


PS thanks guys for helping me understand this better.