!!!UPDATE!!!: Looks like the 60GHz is not a close as we thought. :(

[IJump]

I am a network administrator. I have about 450 computers. I can't get all of them runing Seti, but I can at least get some of them running part of the time. 60 C1GHz and 90 lesser machines wouldn't be too shabby if you know what I mean.

So here is the question:

I run MS Proxy server with mandatory authentication and can't get the clients to connect through the proxy server, regardless of how I try the authentication. Command line or GUI client, neither have worked for me. I have looked on the net for answers, but have not found any. Right now I have 3 computers (mine and family computers) and two on the way (Ones I am building). That would be small fries compared to what I could bring in at work.

LMK any ideas and I am willing to try just about anything.

 

[Domination]

Where's all of our network guru's? We have a TeAm member with a need... not to mention a boat load of computers

 

[Shuxclams]

Set up a SETIQ on your PC, have all the clients point to your SETIQ, use the LAN Installer so you have control over them. The LAN Installer is what IndyJaws is using on his LAN. Now if your PC can get to the internet, then so will the SETIQ when it fetches and flushes, so that in a ball would be how I would do it.











SHUX

 

[IsOs]

I don't use MSProxy so my idea will not really touch MSProxy. Since your computers are all network and using TCP/IP protocol, I would setup a SETI Q in the machine that runs MSProxy. I think that machine has a direct internet connection. Then I would run SETI Driver on the other machines and point it to the computer that runs SETI Q. This way, you don't have to change anything in your MSProxy.

Does MSProxy have a section where you define port forwarding? If so, another solution is to setup port 5001 and mapped it to orangekid.teamandtech.com:5001. Then set your other machines to have SETI client point to MSProxy's IP port 5001.

Tell me more about the machine that runs your MSProxy. What is your internet connection? How is Internet Explorer configured in that machine?

 

[FyndhornKroog]

You beat me to it Shuxclams. That is the way I would do it also....

 

[Sukhoi]

I believe Windogg used to have a program that would get through a bunch of firewalls..

 

[IJump]

I had SetiQ on my machione at one point and could never get it to connect. I will look into that again and be getting back if I need help or with results.

 

[Logix]

Good luck, man.

That would be a great addition to the TeAm!

 

[m2kewl]

<< I had SetiQ on my machione at one point and could never get it to connect. I will look into that again and be getting back if I need help or with results. >>



Like others have said, easiest is to use SETIQ. If you have access to the proxy server, check out the logs after you have set up the clients and SETIQ and see where it's being dropped and which port #. You can then enable those ports. Hope that helps!

Good luck and it'll be great to have you onboard!!!

 

[IJump]

Been onboard the TeAm for a while (two years or so), started doing RC5. If people remember my output for TACube, then they know hwat I have to bring to Seti, except that I have upgrade some since then.

 

[IndyJaws]

<< I had SetiQ on my machione at one point and could never get it to connect. I will look into that again and be getting back if I need help or with results. >>



As Yogi Berra would say - "Deja vu all over again!"

Don't worry, IJump. Between Shux and everyone else here, someone will fix your problem!

 

[micron]

I'm not sure if it would work, but in Seti Queue under the proxy config, there is an area for user name and password. Could you set the clients to the queue, and then the queue to your MS Proxy and login via username and password? Just a thought.

 

[Smoke]

He mentioned he couldn't get SetiQueue to work on his first try. There is that issue that the 1st WU has to be crunched and sent in by the SetiQueue before it starts doing its job. Up until then, you will probably be thinking that it is not working.

Someone with a little more experience setting up the SetiQueue needs to clarify this. I remember it caused me much grief and I deleted SetiQueue several times in frustration before I finally got it to run properly. One of the issues was that 1st WU.

 

[RaySun2Be]

Could he run SETI on a PC outside of the network using SETIDRIVER, and NOT have it transmit the WUs, then bring those completed WUs into work, and submit them through the SETIQ? Would that trick SETIQ into working properly?

 

[J.Zorg]

I don´t know what kind of Proxy MS Proxy is but i found a faq concerning MS Proxy connection Problems on the seti@home site.
Is it some kind of Socks proxy??

Link1
Link2

 

[Poof]

One of the issues was that 1st WU.

Yeah and after having gone through that frustration just last week myself (having not gone through it in awhile), I *think* I know what might have needed to be done to get the client recognized that first time. For some reason in my case, it had to do with setting the "-proxy" parameter on the client, to point to the Setiqueue hostname, NOT the IP. You would think that using the IP should guarantee that it would get there, but that didn't seem to be the case that very first time (regardless of whether I had the hosts file on the queue machine populated or not). Apparently Setiqueue (and I know SETI) does a "gethostbyname" on the client and can't seem to get it if you specify a numeric IP as a proxy parameter... But if I specify the hostname that first time, it connects right away. Later, I can use either the numeric IP or hostname as the proxy parameter, and it works just fine.

 

[micron]

<< One of the issues was that 1st WU.

Yeah and after having gone through that frustration just last week myself (having not gone through it in awhile), I *think* I know what might have needed to be done to get the client recognized that first time. For some reason in my case, it had to do with setting the "-proxy" parameter on the client, to point to the Setiqueue hostname, NOT the IP. You would think that using the IP should guarantee that it would get there, but that didn't seem to be the case that very first time (regardless of whether I had the hosts file on the queue machine populated or not). Apparently Setiqueue (and I know SETI) does a "gethostbyname" on the client and can't seem to get it if you specify a numeric IP as a proxy parameter... But if I specify the hostname that first time, it connects right away. Later, I can use either the numeric IP or hostname as the proxy parameter, and it works just fine. >>

A regular IP address always works for me.

 

[Poof]

A regular IP address always works for me.

I would think it should... But it wouldn't do it that very first time. It would try to connect to the queue and then sit there and complain about not being able to connect. It happened last week with my Duron and happened earlier with my sparc. It even happened for me when I first started up an instance as a processor trade with Sukhoi and I had it trying to connect to OK's server. And in each case, for that first time only, I had to put the queue hostname in for the proxy setting in order to have the client even be able to connect to the queue.

Then once the client was registered in the queue (and the client's hostname was recorded by it), I could use the IP from then on.

Sigh...

 

[zeruty]

I can't help any, but here's a bump for attention.

 

[IJump]

I think we are getting closer, thanks for the help so far, and keep the suggestions coming. We will whip this thing eventually, and whip DSLR in the process.

 

[Corsairpro]

bump for 60GHz!!

 

[BreakApart]

Howdy Fellow MSProxy-from-hell user!

First things-first, what version proxy are you using? 2.0? How are your client machines getting through the proxy? There are (3) protocols they could be using, or a combo depending on usage. Network Admin should know this... lol
Do you have any Win98 or Win2000 client machines? Are ANY of them using the WSPclient-(winsockproxy client) software to connect to the net? or are you forcing the users to log through the proxy everytime they wish to use the internet?

Well this should get us started...

 

[Shuxclams]

Does your local/personal work PC get to the internet? Can you download This and start it? If so then when it starts CTRL+C and then retype in the commandline "setiathome -proxy 127.0.0.1:5517" Let it run until it completes the Wu, if the local proxy gets the Wu and then goes to the internet and grabs more then we should be in business.












SHUX

 

[Ken g6]

If nothing else works, using the pre-1.0 SetiQ, you could download WUs to a temporary queue outside, and sneakernet them into a queue inside the proxy server. I don't know, but it might work with the current SetiQ too.

But only do this if you're desperate.

 

[Assimilator1]

Bump

Can someone point Windog to this thread?
(thanks Sukhoi ,I couldn't remember the name!)