Not sure why its doing this, Its coming up with a message like my current PC had at the weekend.

[09:30:00] + Attempting to get work packet

[09:30:00] - Connecting to assignment server

[09:30:00] Couldn't send HTTP request to server (wininet)

[09:30:00] + Could not connect to Assignment Server

[09:30:00] Couldn't send HTTP request to server (wininet)

[09:30:00] + Could not connect to Assignment Server 2

[09:30:00] + Couldn't get work instructions.

[09:30:00] - Error: Attempt #14 to get work failed, and no other work to do.

Waiting before retry.

[10:18:11] + Attempting to get work packet

[10:18:11] - Connecting to assignment server

[10:18:11] Couldn't send HTTP request to server (wininet)

[10:18:11] + Could not connect to Assignment Server

[10:18:11] Couldn't send HTTP request to server (wininet)

[10:18:11] + Could not connect to Assignment Server 2

[10:18:11] + Couldn't get work instructions.

[10:18:11] - Error: Attempt #15 to get work failed, and no other work to do.

Waiting before retry.

Now my current PC can send and download WU details / data as long as the internet connection exists. My AMD64 is connected to the same network, using the same Belkin USB wireless dongle, yet it spent 6 hours trying to connect to download a new WU (sent its completed unit details fine....)

Once I saw it doing this, I restarted the PC and it downloaded new work fine, and went merrily on its way folding.... But I've lost 6 hours CPU time. Why the hell did it not manage to connect to the assignment server if it had successfully only just connected to send off its details, :confused:

Anything obvious I can check?

got a third party firewall on there? set your FAH machine ID to a different number to the other boxes? can you ping the FAH servers?

can't think of anything else obvious...

No firewall that I know of. Its a virgin XP Pro install. Only difference between the 2 systems is the O.S. Might see if something is in there. Lets me surf the net fine. Might turn off every safe setting I can.

The Windows XP firewall maybe? Has a nasty habit of turning itself on even when you say no!

Well, my PC here is set to "medium" security and accept all cookies. Shall flick the mouse over tuther machine and check its internet settings. Just odd it could send its work unit, but not download a new one.

:confused:

OK.... flicked mouse to other tower (only got one ) and I went into the internet and it wouldn't even find google.... I hit refresh nope, hit detect network...nope. This was all with the wireless on and connected. So, I used the recent hits dropdown and selected another site...and it went straight in. Went back to google even after that too. This is so random... Wassup with it? :(

Dns

ok... better answer time :P

click start/run and type cmd

then on the black dosbox type:

ipconfig /all

do this on both boxes and check that the dns server, dhcp server and gateway are the same on both machines.

ain't the xp firewall i don't think: only blocks incoming and i think that FAH uses port 80 which isn't blocked if you're able to surf the web.

what's your network setup? are you using wireless on the boxes? no interference anywhere? check your dns is right and if you're on ADSL try using TCP Optimizer to adjust the MTU - this has caused me a load of DNS-error-like problems in the past when incorrectly set...

ric

OK, Col. Any chance of telling me how to change all this. It is different on the new machine (slightly) but I thought it would change everything the same when it did auto detect settings in LAN

DHCP and autoconfig enabled are both YES, but my good machine has a preset I.P address of 192.168 etc, but the AMD64 has autoconfig IP of 169.254 etc... The subnet mask is different as well, and there's no default gateway on the AMD64 but there is on the XP2200+ :confused:

The numbers on the XP2200+ remind me of my old Netgear settings though, which the AMD64 has never been linked to. If that helps.

an IP in the range 169.254 means that it's not picked up an address via DHCP, it's the Windows default range when it can't find one. Reboot your router?

if you're having DHCP issues you might want to hard code the IPs (e.g. one on 192.168.0.x and one on 192.168.0.y, gateway set to IP of router, subnet set to 255.255.255.0, DNS set to whatever your ISP's DNS servers are) to troubleshoot. i put my home "servers" on statics as it makes life easier finding them on the network, and let laptops and portable devices get their address via DHCP...

Well, somehow got it sorted. Still not 100%^ sure what I did. Anyone who has one of these Belkin dongles will know the software it uses. Mine said it was connected to the Livebox, but in the profile setting I asked it to connect again and it said "connected" again in a bubble pointing to the taskbar, and all the I.Ps had been assigned by DHCP again, to match my other machine.

Now WHY I have to go into the Belkin software and tell it this is beyond me. I would have assumed this machine would start up and connect to the router via DHCP from the off, but it would appear not. It looks like I'll have to check theI.P assigned every time I reboot it....

J, do a ipconfig -release

then ipconfig -renew

that renews the IP address. is the name you've given in windows. You can change that to "LAN" or something simple in start -> settings -> network connections.

I assume this is wireless, you may have 2 issues.

1) I found the belkin software pants and got much better results after removing all the belkin software and just installing the drivers, then letting windows XP handle the wireless side of things.

2) Someone else near you also has the same wireless router as you, but with security turned off, and you connected to it the first time round. They may also not have internet access on the router, hence the connection problem to fah.

1) is more likely.

2) is doubtful as I'm in quite a remote area and no other router has popped up, especially one the same as my current one.

Hoping what I did last night to 1) will remain. I could really do with a mouse so I can monitor that system easier than leaning behind my current desk, unplugging the mouse and sticking it in the back of the 64.

Any closer to sorting it mate?

Well, yeah - Sorted it on the AMD64, then my XP2200+ did it yesterday. Got that one sent off too, with a reboot. And that one WAS DHCP assigned fine, but still it wasn't connecting... :confused:

I'm sort of hoping the two Belkin adaptors aren't fighting against one another? Its a though.

I think sometimes the FAH servers do not receive the requests to receive data properly(or are down i guess)... as this has happened a few times recently