Apologies for bringing this up again but we are still trying to get to the bottom of why our clubs sailwave users can no longer upload results directly from sailwave. A quick question I have been asked to ask is whether the sailwave “publish results” command sends the files from the users IP address, or does it go via a sailwave IP address? We are wondering if our hosts have blocked some computer addresses for some reason and if so need to understand the route the files take I think.
···
From: sailwave@yahoogroups.com [mailto:sailwave@yahoogroups.com]
Sent: 13 June 2016 17:04
To: sailwave@yahoogroups.com
Subject: RE: [sailwave] Uploading via ftp
Colin,
Thanks that works too.
http://sailwave.com/results/2016_3rd_race_spring.htm
Regards,
Chris Gandy
From: sailwave@yahoogroups.com [mailto:sailwave@yahoogroups.com]
Sent: 13 June 2016 17:01
To: Sailwave User Group
Subject: Re: [sailwave] Uploading via ftp
hi chris, sounds like it. another test is to try and publish to the sailwave website - it uses ftp also - just with burned-in info.
Cheers,
Colin J
http://op12no2.me
On Mon, Jun 13, 2016 at 4:56 PM, Christopher Gandy chrisgandy@me.com [sailwave] sailwave@yahoogroups.com wrote:
Colin,
I tried flipping the slashes but still nothing. I then tried deleting all the details for my club ftp site and replaced with my work one. Uploaded to work fine from sailwave directly which would, I assume, rule out that it’s a sailwave/my computer/my firewall issue.
I then re-entered my club ftp details in sailwave as they were before and now cannot even establish a connection, so I assume it is most likely a problem at club end as Jon suggested originally.
Regards,
Chris
From: sailwave@yahoogroups.com [mailto:sailwave@yahoogroups.com]
Sent: 13 June 2016 16:45
To: Sailwave User Group
Subject: Re: [sailwave] Uploading via ftp
It’s just a thought but I think ftp is slash dependent - i.e. folder\file for windows and folder/file for linux.
try publishing to the ftp root?
Cheers,
Colin J
http://op12no2.me
On Mon, Jun 13, 2016 at 4:37 PM, Christopher Gandy chrisgandy@me.com [sailwave] sailwave@yahoogroups.com wrote:
Duncan,
If I ask sailwave to publish to a file instead of via ftp I can then send the file via my ftp client (FileZilla) to the same directory sailwave is pointed at on the clubs website using the exact same username and password with no errors.
Chris
On 13 Jun 2016, at 16:00, ‘Duncan Hill (Flickr)’ flickr@cricalix.net [sailwave] sailwave@yahoogroups.com wrote:
On 2016-06-13 15:53, Christopher Gandy chrisgandy@me.com [sailwave] wrote:
Martin,
Thanks. I don’t have Mcafee firewall, only the Windows one and can’t see a setting similar to open to all devices in there.
Will keep trying, it’s really frustrating as I don’t think I’ve changed anything and with the other club member having similar experiences I’d hoped it was at the clubs website end as Jon alluded to but they don’t think it is.
A simple test is to change clients. There used to be a CLI implementation in Windows - Start > Run > command, then in the black console box type ftp. However, if you prefer a non-text-only interface, check out https://winscp.net/eng/docs/free_ftp_client_for_windows . I think it gives fairly detailed troubleshooting logs about what failed when it can’t connect (but I can’t check right now, since I’m on a Mac). WinSCP has a pretty extensive set of documentation about what kind of error messages it prints out when it has problems.
If two people and three clients are having issues, then as Jon has said, that’s more likely the other end; I’d ask the folks who admin the server to test with the account you’re using, and make sure it works with the same client (ie, WinSCP). Trade screenshots of configuration options etc.
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2016.0.7639 / Virus Database: 4598/12392 - Release Date: 06/09/16
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2016.0.7639 / Virus Database: 4598/12392 - Release Date: 06/09/16
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2016.0.7639 / Virus Database: 4598/12392 - Release Date: 06/09/16