Simply call serverName = Resolve(serverName) before calling Ftp.Connect method: public static string Resolve(string serverName) In the meantime, use the following Resolve method as a workaround. We will consider changing this behavior (which means Rebex FTP/SSL would behave like FileZilla). The order of resolved addresses is different each time, but the result is cached, which means Rebex FTP/SSL actually uses the same address each time until the cached DNS record expires. Rebex FTP/SSL uses the first address in the list. I'm not sure what are doing or if Rebex should be able to cope.įTP server at resolves into multiple addresses: c:\>nslookup If I hard code the 65.49.XX.57 address then it connects okay. When using Rebex, it tries to connect to 65.49.XX.56 and fails, but doesn't move on to the next address. It looks like it got the IP address from the DNS (65.49.XX.56) but it failed to connect to this server, so it moved on to the next. FTP is for Signature and Premium accounts only. Response: 220 - Username is your email address used for web interface. Status: Connection established, waiting for welcome message. Status: Connection attempt failed with "ECONNREFUSED - Connection refused by server", trying next address. I used FileZilla to connect to the same server and it logged this (I have added some XXX parts to hide some details). We are using a FTPS server from Rebex can connect to it most of the time but every now and then it fails.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |