Please help with goofy client problem

[Cowering]

I'm running win2kpro on a celeron 700.. takes about 2.5 hours to do a block.. but i've been waiting for 4 hours for my current block to complete (k=21181, n=2281148) . The client is showing 00s remaining (for at least an hour), and 0% usage on cpu in task manager (system idle process is 99%).

I've exited and stop/started and it just won't complete the block.

Any clues?

[Cowering]

i changed this client from sb.pns.net:1717 to sbp.pns.net:22 and restarted and it reported the completed block to the server immediately.

Hope my other clients don't all start doing this!

[dmbrubac]

I'm glad that worked for you Cowering. I've had the hang up problem on a client too, and that was was with sbp..... It only happened once and I don't know why.

I wouldn't expect a huge rash of hangups.

[Cowering]

My bigger problem is that i'm trying to automate rolling SB to about 200 machines and I won't have time to go fix the clients if they start to randomly shutdown.

Maybe the next version of the client can try multiple ports/ips until one of them works.

[jjjjL]

that's really bizarre that switching the port would fix it. especially from 1717 --> 22.

those two ips both point to the exact same machine... it's just a datapipe running on the server.

as soon as traffic gets to sbp.pns.net 22 it is routed internally on the server to sb.pns.net 1717.

the socket timeouts could be better. i'll keep it in mind for the next client.

-Louie

[Cowering]

great.. can the windows client use port 80 to talk to sb.pns.net? that would fix up quite a few firewall problems a few of my users are having.


Any ETA on the new windows client? i have 7 machines running sb on a simple linux router/NAT provider and the linux box has page after page of sockets still open on port 1717 (reported via netstat). I hope i never run out of resources to create a new socket.

[jjjjL]

port 80 on sbp.pns.net should work

-Louie