Post a reply

Before posting, please read how to report bug or request support effectively.

Bug reports without an attached log file are usually useless.

Options
Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)

Options

Topic review

martin

Re: Microsoft "security" update incompatible with WinSCP???

I have installed the update and as expected it had no impact on WinSCP.
Guest

Re: Microsoft "security" update incompatible with WinSCP???

Yeah, I've got the same problem since installing the latest update. Here's my session log:


. --------------------------------------------------------------------------
. WinSCP Version 3.5.0 (Build 204)
. Login time: Sunday, February 08, 2004 9:05:44 PM
. --------------------------------------------------------------------------
. Session name: xxxxxxx@xanthia.com
. Host name: xanthia.com (Port: 22)
. User name: xxxxxxx (Password: Yes, Key file: No)
. Transfer Protocol: SCP
. SSH protocol version: 2; Compression: No
. Agent forwarding: No; TIS/CryptoCard: No; KI: Yes
. Ciphers: aes,blowfish,3des,WARN,des; Ssh2DES: No
. Ping type: -, Ping interval: 60 sec; Timeout: 15 sec
. SSH Bugs: -,-,-,-,-,-,-,-,
. Proxy: none
. Return code variable: Autodetect; Lookup user groups: Yes
. Shell: default, EOL: 0
. Local directory: default, Remote directory: home, Update: No, Cache: Yes
. Cache directory changes: Yes, Permanent: Yes
. Clear aliases: Yes, Unset nat.vars: Yes, Resolve symlinks: Yes
. Alias LS: No, Ign LS warn: Yes, Scp1 Comp: No
. --------------------------------------------------------------------------
. Looking up host "xanthia.com"
. Connecting to 66.92.150.142 port 22
. Attempt to close connection due to fatal exception:
* Network error: Connection timed out
. Closing connection.
* (ESshFatal) Network error: Connection timed out
martin

Re: Microsoft "security" update incompatible with WinSCP???

I do not think that this has something to do with the security update. However everything is possible :-)

Please post WinSCP session log.
Mike_HI

Microsoft "security" update incompatible with WinSCP???

I have been using WinSCP for over a year and find it to be an invaluabe tool form managing my web site. My operating system is XP-home. Unfortunatly, on Feb 2,04, I added a Microsoft Security updatte, "Security Update for Microsoft Data Access Components (KB832483), and ever since I have not been able to log on to my server with WinSCP2, winSCP3 or winSCP3.5. I get the error message ("Host hasn't answered in 15 seconds"). No matter how many times I "retry", I get the same error message. 1) I have tried logging on using different ISP's, and always get the same error message when using WinSCP. 2) It seems that I actually can connect to my remote server with winSCP but my remote server cannot communicate back, so I get the error message. 3) However, I can connect using winSCP from another computer which uses XP-professional (the security updtae in question was not installed on this other computer). In my opinion, there is some sort of incompatability with this new "mictrosoft security update" and win SCP. Is anyone else having this problem? Can anyone help me. I miss this wonderful program very much. Thanks, Mike