I have one classic client unable to get work. It is trying these two addresses, one of which I do not even see in the server list.
129.74.85.48
169.230.26.30
Neither will show OK in a browser yet 169.230.26.30 seems to operating normally at the Server Status page.
<<<EDIT>>> No sooner than I post and it gets some work from 169.230.26.30
129.74.85.48 Unable to connect
Moderators: Site Moderators, FAHC Science Team
-
Leoslocks
- Posts: 120
- Joined: Fri Jan 25, 2008 3:20 am
- Hardware configuration: Q6600 | P35-DQ6 | Crucial 2 x 1 GB ram | VisionTek 3870
GPU2 Version 6.20| CPU three 6.20 Clients
129.74.85.48 Unable to connect
Last edited by Leoslocks on Tue Oct 13, 2009 8:45 pm, edited 1 time in total.
-
Leoslocks
- Posts: 120
- Joined: Fri Jan 25, 2008 3:20 am
- Hardware configuration: Q6600 | P35-DQ6 | Crucial 2 x 1 GB ram | VisionTek 3870
GPU2 Version 6.20| CPU three 6.20 Clients
Re: 169.230.26.30 Unable to connect
The client worked one 47 point Amber WU and is back at the same stall situation.
The main server is 129.74.85.48
This server is not listed on the Server Status page. Neither server IP shows OK in a browser window.
The main server is 129.74.85.48
This server is not listed on the Server Status page. Neither server IP shows OK in a browser window.
-
Pette Broad
- Posts: 128
- Joined: Mon Dec 03, 2007 9:38 pm
- Hardware configuration: CPU folding on only one machine a laptop
GPU Hardware..
3 x 460
1 X 260
4 X 250
+ 1 X 9800GT (3 days a week) - Location: Chester U.K
Re: 169.230.26.30 Unable to connect
That server is to all intents and purposes empty. It only has work when a unit is returned which then creates the next unit. So it's just a matter of luck if you get a unit on your first attempt. The good thing is that relative to other units the Ambers on this server don't take long so work is being created pretty often 
Pete
Pete