Webdav connection fails with WinSCP but works with Cyberduck

Advertisement

asprin
Guest

Webdav connection fails with WinSCP but works with Cyberduck

I have a site that I can connect to via Cyberduck (webdav ssl) but the same site when trying to open via WinSCp is failing. I'm getting connection timed out message even though I have kept the connection timeout setting set to 120 seconds (I usually get the timed out message after about 15-20 seconds).

I have already seen https://winscp.net/eng/docs/faq_connection_refused and added WinSCP to firewall settings. Is there any other particular reason why WinSCP is blocking the connection?

I'm on
Windows 7
WinSCP 5.13.2

Thanks,
asprin

Reply with quote

Advertisement

martin
Site Admin
martin avatar
Joined:
Posts:
28,811
Location:
Prague, Czechia

Re: Webdav connection fails with WinSCP but works with Cyberduck

Please attach a full session log file both from WinSCP and Cyberduck.

Reply with quote

asprin
Guest

Hi martin,

Here is the log from WinSCP (with confidential information redacted)

. 2018-07-18 14:58:13.883 --------------------------------------------------------------------------
. 2018-07-18 14:58:13.883 WinSCP Version 5.11 (Build 7715) (OS 6.1.7601 Service Pack 1 - Windows 7 Professional)
. 2018-07-18 14:58:13.883 Configuration: HKCU\Software\Martin Prikryl\WinSCP 2\
. 2018-07-18 14:58:13.883 Log level: Normal
. 2018-07-18 14:58:13.885 Local account: (redacted)
. 2018-07-18 14:58:13.885 Working directory: C:\Program Files (x86)\WinSCP
. 2018-07-18 14:58:13.885 Process ID: 12352
. 2018-07-18 14:58:13.885 Command-line: "C:\Program Files (x86)\WinSCP\WinSCP.exe" 
. 2018-07-18 14:58:13.888 Login time: Wednesday, July 18, 2018 2:58:13 PM
. 2018-07-18 14:58:13.888 --------------------------------------------------------------------------
. 2018-07-18 14:58:13.888 Session name: john@<sitename>.custhelp.com (Site)
. 2018-07-18 14:58:13.888 Host name: <sitename>.custhelp.com (Port: 443)
. 2018-07-18 14:58:13.888 User name: john (Password: Yes, Key file: No, Passphrase: No)
. 2018-07-18 14:58:13.888 Transfer Protocol: WebDAV
. 2018-07-18 14:58:13.888 Proxy: None
. 2018-07-18 14:58:13.888 HTTPS: Yes [Client certificate: No]
. 2018-07-18 14:58:13.888 TLS/SSL versions: TLSv1.0-TLSv1.2
. 2018-07-18 14:58:13.888 Local directory: default, Remote directory: home, Update: Yes, Cache: Yes
. 2018-07-18 14:58:13.888 Cache directory changes: Yes, Permanent: Yes
. 2018-07-18 14:58:13.888 Recycle bin: Delete to: No, Overwritten to: No, Bin path: 
. 2018-07-18 14:58:13.888 DST mode: Unix
. 2018-07-18 14:58:13.888 Compression: No
. 2018-07-18 14:58:13.888 --------------------------------------------------------------------------
. 2018-07-18 14:58:13.928 HTTP session to https://<sitename>.custhelp.com:443 begins.
. 2018-07-18 14:58:13.928 ssl: SNI enabled by default.
. 2018-07-18 14:58:13.930 ah_create, for WWW-Authenticate
. 2018-07-18 14:58:13.930 Sending request headers:
. 2018-07-18 14:58:13.930 OPTIONS / HTTP/1.1

. 2018-07-18 14:58:13.930 User-Agent: WinSCP/5.11 neon/0.30.2

. 2018-07-18 14:58:13.930 Keep-Alive: 

. 2018-07-18 14:58:13.930 Connection: TE, Keep-Alive

. 2018-07-18 14:58:13.930 TE: trailers

. 2018-07-18 14:58:13.930 Host: <sitename>.custhelp.com
. 2018-07-18 14:58:13.930 Sending request-line and headers:
. 2018-07-18 14:58:13.930 Doing DNS lookup on <sitename>.custhelp.com...
. 2018-07-18 14:58:14.033 req: Connecting to xx.xxx.xx.xx:443
. 2018-07-18 14:58:35.058 Request ends, status 0 class 0xx, error line:
. 2018-07-18 14:58:35.058 Could not connect to server: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
. 2018-07-18 14:58:35.058 Request ends.
. 2018-07-18 14:58:35.058 sess: Destroying session.
* 2018-07-18 14:58:35.095 (EFatal) Connection failed.
* 2018-07-18 14:58:35.095 Could not connect to server: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
* 2018-07-18 14:58:35.095 Connection failed.

Reply with quote

asprin
Guest

And this the log from Cyberduck

CONNECT <sitename>.custhelp.com:443 HTTP/1.1
Host: <sitename>.custhelp.com
User-Agent: Cyberduck/6.6.0.28133 (Windows 7/6.1) (x86)
HTTP/1.0 200 Connection established
HEAD / HTTP/1.1
Host: <sitename>.custhelp.com
Connection: Keep-Alive
User-Agent: Cyberduck/6.6.0.28133 (Windows 7/6.1) (x86)
Accept-Encoding: gzip,deflate
HTTP/1.1 200 OK
Date: Wed, 18 Jul 2018 09:41:47 GMT
Server: Apache
RNT-Time: D=253165 t=1531906907968695
RNT-Machine: 0.72
Content-Encoding: gzip
Content-Length: 20
Keep-Alive: timeout=15, max=98
Connection: Keep-Alive
Content-Type: text/html; charset=UTF-8
PROPFIND / HTTP/1.1
Depth: 1
Content-Type: text/xml; charset=utf-8
Content-Length: 242
Host: <sitename>.custhelp.com
Connection: Keep-Alive
User-Agent: Cyberduck/6.6.0.28133 (Windows 7/6.1) (x86)
Accept-Encoding: gzip,deflate
HTTP/1.1 301 Moved Permanently
Date: Wed, 18 Jul 2018 09:41:48 GMT
Server: Apache
Location: /dav/
RNT-Time: D=82762 t=1531906908862034
RNT-Machine: 0.85
Content-Encoding: gzip
Content-Length: 21
Keep-Alive: timeout=15, max=64
Connection: Keep-Alive
Content-Type: text/plain;charset=UTF-8
PROPFIND /dav/ HTTP/1.1
Depth: 1
Content-Type: text/xml; charset=utf-8
Content-Length: 242
Host: <sitename>.custhelp.com
Connection: Keep-Alive
User-Agent: Cyberduck/6.6.0.28133 (Windows 7/6.1) (x86)
Accept-Encoding: gzip,deflate
HTTP/1.1 401 Unauthorized
Date: Wed, 18 Jul 2018 09:41:49 GMT
Server: Apache
WWW-Authenticate: Basic realm="RightNow CX"
RNT-Time: D=298099 t=1531906909162480
RNT-Machine: 0.64
Content-Encoding: gzip
Content-Length: 36
Keep-Alive: timeout=15, max=68
Connection: Keep-Alive
Content-Type: text/html; charset=UTF-8
PROPFIND /dav/ HTTP/1.1
Depth: 1
Content-Type: text/xml; charset=utf-8
Content-Length: 242
Host: <sitename>.custhelp.com
Connection: Keep-Alive
User-Agent: Cyberduck/6.6.0.28133 (Windows 7/6.1) (x86)
Accept-Encoding: gzip,deflate
Authorization: ********
HTTP/1.1 207 Multi-Status
Date: Wed, 18 Jul 2018 09:41:49 GMT
Server: Apache
X-WebDAV-Status: 207 Multi-Status
RNT-Time: D=363655 t=1531906909685657
RNT-Machine: 0.64
Content-Encoding: gzip
Content-Length: 437
Keep-Alive: timeout=15, max=12
Connection: Keep-Alive
Content-Type: text/xml; charset="utf-8"

Reply with quote

martin
Site Admin
martin avatar
Joined:
Posts:
28,811
Location:
Prague, Czechia

Cyberduck normally does not use CONNECT request for WebDAV.
Do know why it does in your session? Is there some proxy configured? Or some special settings?

Reply with quote

Advertisement

Guest

martin wrote:

Cyberduck normally does not use CONNECT request for WebDAV.
Do know why it does in your session? Is there some proxy configured? Or some special settings?

Hi martin,

I'm sorry, I'm oblivious to that information. Is there a way I can find out if proxy is being used?

Reply with quote

asprin
Guest

So this is what my proxy settings look like (see attached file)

I also tried unchecking "Use automatic configuration script" but that didn't solve the problem. Is there a way to configure WinSCP to use CONNECT as well?

proxy.png

Reply with quote

martin
Site Admin
martin avatar
Joined:
Posts:
28,811
Location:
Prague, Czechia

asprin wrote:

I also tried unchecking "Use automatic configuration script" but that didn't solve the problem. Is there a way to configure WinSCP to use CONNECT as well?
If you uncheck that, does it prevent Cyberduck from connecting?

WinSCP cannot use automatic proxy configuration script.
You have to configure proxy manually:
https://winscp.net/eng/docs/ui_login_proxy

Reply with quote

asprin
Guest

martin wrote:

If you uncheck that, does it prevent Cyberduck from connecting?
Yes, it does prevent the connection. It appears that on unchecking it I'm not able to view/open websites too.

I also tried using that URL in the proxy settings of WinSCP


but got the following error (screenshot attached)

Am I doing it the wrong way?

error.png

Reply with quote

Advertisement

martin
Site Admin
martin avatar
Joined:
Posts:
28,811
Location:
Prague, Czechia

I wrote that "WinSCP cannot use automatic proxy configuration script.".

Contact your network administrator to ask what proxy you need to use to connect to <sitename>.custhelp.com.

Reply with quote

asprin
Guest

martin wrote:

I wrote that "WinSCP cannot use automatic proxy configuration script.".

Contact your network administrator to ask what proxy you need to use to connect to <sitename>.custhelp.com.
Yes, I realized later what you meant by that. Anyway, I just now solved it. I got the proxy address from the dat file that script was pointing too. And now WinSCP connects fine too.

Thanks for your help.

Reply with quote

Advertisement

You can post new topics in this forum