171.65.103.160

[martiou]

Hello,

Server 171.65.103.160 rejects connexion since "Wed Aug 18 01:00:10 PDT 2010".
What is the problem with this server ?

I have 5 clients at work and I can have WUs only from this server.

1 client is on Windows XP 32 bits, client version 6.23, 990Mb available, CPU AMD 3000+.
4 clients are on Linux 32 bits, client version 6.02, between 700Mb and 1000Mb available, CPU Celeron or Pentium.

Port 8080 is blocked and I can't do anything to change it.

Actually 2 clients can't send results and can't get new WUs and 2 new clients will be in the same state tomorrow.

Clients are configured to get big WU with advmethods=yes.
I tried to change size of WU to small and normal, with advmethods=yes and advmethods=no, with less memory but it changed nothing.

When I look at the server status page, I think I can get WU from servers like 171.64.65.111, 171.64.65.60 and 171.64.65.62 but I have nothing.

So what can I do ?

[martiou]

Finally, server 171.65.103.160 accepts connexion now.
I successfully sent these 2 WUs and get 2 new WUs.

Thanks if somebody resolve the problem.

But I always have a question.

Why can't I get WU from other servers like 171.64.65.111, 171.64.65.60 and 171.64.65.62 ?

[7im]

171.64.65.111 is out of work units.
171.64.65.60 has WUs, but is set offline (blue "iced" port status)
171.64.65.62 is sending out a lot of work at the moment.

171.65.103.160 looks to have a higher "weighting" or priority assigned to it at the moment, so your client is sent there first. Eventually, if it can't get work, it should get "bounced" to one of the other work servers, like x.x.65.62

Sometimes, clients seem to get "stuck" getting work from one server. Adding or removing the -advmethods flag will sometimes unstick the client.