Whats wrong with the F@H work server ? I have two computers that have been trying to get a unit for 1/2 hour now ???

[Markfw]

Title says it all. I am loosing time in folding !!!!!

 

[Insidious]

Is it working now? (fine here)

 

[Markfw]

OK. I'm about ready to quit F@H altogether. Almost every computer I have waits for hours before it gets a work unit. I get "attempt #xx to get work failed, no other work to do" and these computers have been fine for months.

 

[trevinom]

don't quit, we need all the help we can get. I have had situations in the past where it takes a few days for units to get assinged and sent in. It will work itself out, hang in there.

 

[ProviaFan]

I had trouble with that when I was using a Windows 2003 server with RRAS for NAT duties... It was a DNS problem on my end, for sure, but I temporarily fixed it by manually putting in my ISP's DNS server IP addresses in the connection properties of all my LAN systems (instead of using the NAT box's IP and forwarding DNS). The problem was permanently fixed - I don't know how - when I moved to a Linux-based NAT system. 😉

FWIW, I haven't been having any problems on my end recently, but will keep an eye out for them...

 

[trevinom]

I was hooking up to my WAP using it's DHCP. All of my clients were running either Windows XP or Windows 98 and using the built in DHCP client. I started having 'duplicate ip address' problems with the windows 98 clients which was causing the Windows XP clients to have problems too. I started assigning fixed addresses to all the Windows XP clients and upgraded all 98 clients to XP and assigned them fixed IP adddresses as well. I dont' have the problem anymore.
I also upgraded all F@H clients to the 5.02 version and set them up to run as services.