Can't send work units for weeks now
Moderators: Site Moderators, FAHC Science Team
Re: Can't send work units for weeks now
Added a rule to what? As I said I get that response with no firewall at all.
Thanks for the idea,
PME
Thanks for the idea,
PME
eberlyml, team centos #48721
Re: Can't send work units for weeks now
There are rules for inbound and outbound traffic. Which ports is allowed and not. Maybe you didn't allow any traffic on ports above 1024 and 8080 is higher than that.
Maybe your Windows Firewall is disabled but not in the router. The router can have a firewall as well with port forwarding rules. The log indicate that you cannot connect to the servers on port 8080 and the rare few cases where it sent units is with alternate server ports 80, which doesn't always happen.
Maybe your Windows Firewall is disabled but not in the router. The router can have a firewall as well with port forwarding rules. The log indicate that you cannot connect to the servers on port 8080 and the rare few cases where it sent units is with alternate server ports 80, which doesn't always happen.
Re: Can't send work units for weeks now
I am very sure that _all_ firewalls were disabled or out of the mix physically for at least two of my attempts to send the finished units back with exactly the same results.
If you'll look back at the very first post in this thread in my logs you will see it tries first on :8080 and then on:80 for each attempt on both the work server and then the collection server.
I certainly appreciate the ideas though,
PME
If you'll look back at the very first post in this thread in my logs you will see it tries first on :8080 and then on:80 for each attempt on both the work server and then the collection server.
I certainly appreciate the ideas though,
PME
eberlyml, team centos #48721
Re: Can't send work units for weeks now
Ok, all right... I know you said that but I'm rehashing the idea in case you forgot something. Can you do a tracert on the failing adresses to see if it's a problem within your network or outside ?eberlyml wrote:I am very sure that _all_ firewalls were disabled or out of the mix physically for at least two of my attempts to send the finished units back with exactly the same results.
If you'll look back at the very first post in this thread in my logs you will see it tries first on :8080 and then on:80 for each attempt on both the work server and then the collection server.
I certainly appreciate the ideas though,
PME
Re: Can't send work units for weeks now
Tracert looks ok, though I'm no expert. And I can connect to all the servers/both ports in my browser with an 'OK'
I've got a 5113 wu finishing up soon here, if it doesn't send in it will make about 9 work units that I've lost since this problem began in the beginning of January.
I have spent a lot of time in the last week trying to figure this out to no avail. I'm getting tired of messing with it and unless someone else has any ideas I will finally bring this folder off line. It has been folding fine for quite a while and I am not aware of anything that would have changed. Not a big points machine anyway, but it is usually on so I figured why not let it fold.
Thanks everyone for trying,
PME
I've got a 5113 wu finishing up soon here, if it doesn't send in it will make about 9 work units that I've lost since this problem began in the beginning of January.
I have spent a lot of time in the last week trying to figure this out to no avail. I'm getting tired of messing with it and unless someone else has any ideas I will finally bring this folder off line. It has been folding fine for quite a while and I am not aware of anything that would have changed. Not a big points machine anyway, but it is usually on so I figured why not let it fold.
Thanks everyone for trying,
PME
eberlyml, team centos #48721
-
- Posts: 289
- Joined: Sun Dec 02, 2007 4:31 am
- Location: Carrizo Plain National Monument, California
- Contact:
Re: Can't send work units for weeks now
Having a look at the online manual, it does say about needing to update for Vista, what OS have you? Also disabling the firewall, does not turn it completely off.
Re: Can't send work units for weeks now
Are you referring to the protocol check? I did finally find that setting with the command line and disabled it, but no difference. I think that is what produces the 'FIREWALL icmp check (1 of 2): Protocol: ICMP' I referred to earlier. It stopped when I disabled the imcpcheck in the modem, but made no difference for sending the units in.John_Weatherman wrote:Having a look at the online manual, it does say about needing to update for Vista, what OS have you?
Running XP Pro here.
Also disabling the firewall, does not turn it completely off.
as always, thanks!
PME
eberlyml, team centos #48721
-
- Posts: 1024
- Joined: Sun Dec 02, 2007 12:43 pm
Re: Can't send work units for weeks now
I think we should focus on this message. I don't know ICMP and I don't understand why you're getting the message, but it seems pretty likely that if you can figure out how to disable the feature that is prohibiting the communications, you'll probably be able to upload. There's no doubt that 128.59.74.4 is one of the FAH servers.eberlyml wrote:Now, one thing I have found. A little while ago I enabled logging on my dsl modem to see if it had anything to say about my problems. the security logs are showing this
:FIREWALL icmp check (1 of 2): Protocol: ICMP Src ip: 128.59.74.4 Dst ip: xx.xx.my.ip Type: Destination Unreachable Code: Communication with Destination Host is Administratively Prohibited
This happens every time I restart the fah client and it tries to send the finished work units.
Re: Can't send work units for weeks now
Well, that's what I thought. But I did figure out how to disable that check in the modem, and that message stopped but still no go on sending in work units.
Thanks again,
PME
Thanks again,
PME
eberlyml, team centos #48721
-
- Posts: 10179
- Joined: Thu Nov 29, 2007 4:30 pm
- Hardware configuration: Intel i7-4770K @ 4.5 GHz, 16 GB DDR3-2133 Corsair Vengence (black/red), EVGA GTX 760 @ 1200 MHz, on an Asus Maximus VI Hero MB (black/red), in a blacked out Antec P280 Tower, with a Xigmatek Night Hawk (black) HSF, Seasonic 760w Platinum (black case, sleeves, wires), 4 SilenX 120mm Case fans with silicon fan gaskets and silicon mounts (all black), a 512GB Samsung SSD (black), and a 2TB Black Western Digital HD (silver/black).
- Location: Arizona
- Contact:
Re: Can't send work units for weeks now
Reset the modem back to factory defaults, update to the latest firmware, and see what happens. Then start adding in your custom settings one at a time to see what breaks the upload.
How to provide enough information to get helpful support
Tell me and I forget. Teach me and I remember. Involve me and I learn.
Tell me and I forget. Teach me and I remember. Involve me and I learn.
Re: Can't send work units for weeks now
Sorry, should have been more specific. I meant firewall permission.eberlyml wrote:Do I need to do something with permissions on the core? (not much of a Windows guy here).
I'm not so sure that the firewall isn't still blocking inbound connections and simply isn't telling you it's doing so. Unfortunately physically removing the firewall is not an option if it's integrated with the modem. Personally I would follow 7im's advice. Other options would be to put the computer (temporarily) in the DMZ if the router offers that feature. Another would be forwarding port 80 and 8080 to the machine running F@H.eberlyml wrote:Well, that's what I thought. But I did figure out how to disable that check in the modem, and that message stopped but still no go on sending in work units.
Hope you get it sorted,
Amaruk
Re: Can't send work units for weeks now
Follow up:
This morning, without any further changes at all, one (finished on Feb 1) of the three work units being held in queue on this machine was successfully sent in. Don't know what that means, but it indicates there may be problems elsewhere.
PME
This morning, without any further changes at all, one (finished on Feb 1) of the three work units being held in queue on this machine was successfully sent in. Don't know what that means, but it indicates there may be problems elsewhere.
PME
eberlyml, team centos #48721