Just post the trace from System.Net.FtpClient. See the Debug.cs example on how to add TraceListener objects for logging the transaction. Other things are logged such as the encoding System.Net.FtpClient is using, for example. I just want to look through it to see if there is any clue as to what might be happening. I'm basically running blind, I can't help fix it if I don't know what exactly is broken with System.Net.FtpClient and Synology's FTP daemon.
↧
New Post: Issue downloading file with special characters in the filename
↧
Commented Unassigned: UTF8 Filenames with EnableThreadSafeDataConnections [382]
Hi,
First of all thanks for the create FtpClient library!
I had some troubles with filenames containing foreign utf8 characters. After connecting to the server (the server supports the UTF8 capability) i was able to receive the listing and all characters were correct. But i was not able to call ftpClient.OpenRead because an exception was thrown saying the file does not exits.
After some investigations i found out the the FtpCLient creates a new connection to the server for every download. The problem is that the new connection does not send the "OPTS UTF8 ON" command and therefore the download of files with foreign characters does not work.
I have set the EnableThreadSafeDataConnections property to false. Now the download of the file uses the same connection that was used to get the listing. This connection has sent the "OPTS UTF8 ON" command and the download works fine.
So i think it is a bug that new connections that are created for downloads do not send the "OPTS UTF8 ON" command.
Bernhard
Comments: Thanks, I had another report this morning about the problem. Will look into it today.
First of all thanks for the create FtpClient library!
I had some troubles with filenames containing foreign utf8 characters. After connecting to the server (the server supports the UTF8 capability) i was able to receive the listing and all characters were correct. But i was not able to call ftpClient.OpenRead because an exception was thrown saying the file does not exits.
After some investigations i found out the the FtpCLient creates a new connection to the server for every download. The problem is that the new connection does not send the "OPTS UTF8 ON" command and therefore the download of files with foreign characters does not work.
I have set the EnableThreadSafeDataConnections property to false. Now the download of the file uses the same connection that was used to get the listing. This connection has sent the "OPTS UTF8 ON" command and the download works fine.
So i think it is a bug that new connections that are created for downloads do not send the "OPTS UTF8 ON" command.
Bernhard
Comments: Thanks, I had another report this morning about the problem. Will look into it today.
↧
↧
New Post: Issue downloading file with special characters in the filename
Trace:
220 FTP1 FTP server ready.
USER admin
331 Password required for admin.
PASS <omitted>
230 User admin logged in.
FEAT
211- Extensions supported:
AUTH TLS
PBSZ
PROT
SIZE
MDTM
MFMT
REST STREAM
UTF8
211 End.
OPTS UTF8 ON
200 OK, UTF-8 enabled
Text encoding: System.Text.UTF8Encoding
Disposing FtpClient object...
Disposing FtpClient object...
Disposing FtpClient object...
220 FTP1 FTP server ready.
USER admin
331 Password required for admin.
PASS <omitted>
230 User admin logged in.
FEAT
211- Extensions supported:
AUTH TLS
PBSZ
PROT
SIZE
MDTM
MFMT
REST STREAM
UTF8
211 End.
OPTS UTF8 ON
200 OK, UTF-8 enabled
Text encoding: System.Text.UTF8Encoding
PWD
257 "/" is current directory.
CWD TEST_TEST
250 CWD command successful.
CWD /
250 CWD command successful.
PWD
257 "/" is current directory.
CWD /TEST_TEST/Test
250 CWD command successful.
CWD /
250 CWD command successful.
PWD
257 "/" is current directory.
TYPE I
200 Type set to I.
PASV
227 Entering Passive Mode (10,233,15,12,217,4)
LIST /TEST_TEST/Test
150 Opening BINARY mode data connection for 'file list'.
-rw-rw-rw- 1 admin users 24 Jun 17 14:37 æøå.txt
226 Transfer complete.
Disposing FtpSocketStream...
Ignoring modified date because MDTM feature is present. If you aren't already, pass FtpListOption.Modify or FtpListOption.SizeModify to GetListing() to retrieve the modification time.
æøå.txt
PWD
257 "/" is current directory.
CWD /TEST_TEST/Test2
250 CWD command successful.
CWD /
250 CWD command successful.
PWD
257 "/" is current directory.
TYPE I
200 Type set to I.
PASV
227 Entering Passive Mode (10,233,15,12,217,5)
LIST /TEST_TEST/Test2
150 Opening BINARY mode data connection for 'file list'.
226 Transfer complete.
Disposing FtpSocketStream...
220 FTP1 FTP server ready.
USER admin
331 Password required for admin.
PASS <omitted>
230 User admin logged in.
FEAT
211- Extensions supported:
AUTH TLS
PBSZ
PROT
SIZE
MDTM
MFMT
REST STREAM
UTF8
211 End.
OPTS UTF8 ON
200 OK, UTF-8 enabled
Text encoding: System.Text.UTF8Encoding
220 FTP1 FTP server ready.
USER admin
331 Password required for admin.
PASS <omitted>
230 User admin logged in.
Text encoding: System.Text.UTF8Encoding
PWD
257 "/" is current directory.
CWD /
250 CWD command successful.
TYPE I
200 Type set to I.
SIZE /TEST_TEST/Test/æøå.txt
550 /TEST_TEST/Test2/æøå.txt: No such file or directory.
PASV
227 Entering Passive Mode (10,233,15,12,217,10)
RETR /TEST_TEST/Test/æøå.txt
550 /TEST_TEST/Test/æøå.txt: No such file or directory.
QUIT
221 Goodbye. You uploaded 0 bytes and downloaded 0 bytes.
Disposing FtpClient object...
Disposing FtpSocketStream...
↧
New Post: Issue downloading file with special characters in the filename
Thanks, someone just opened a new ticket with the same problem and their description matches what I see in the transaction log, UTF8 isn't being configured on cloned connections (default behavior, EnableThreadSafeDataChannels = true). I'm about to work on it now. Will let you know when it's fixed.
↧
Source code checked in, #630f66e9436aeb1e55612bd50605096c60209ec5
Addressed problem where cloned connections didn't execute OPTS UTF8 ON. This shouldn't be a problem because UTF8 is supposed to be enabled by default but there are conflicting drafts about this behavior so some servers require it to be explicitly enabled.
↧
↧
Released: System.Net.FtpClient (Jun 17, 2014)
System.Net.FtpClient is now available via
nuget.
Be sure to read the Documentation page for important information about using this library. It's a quick read and will be worth its weight in gold with regards to effectively using this project in your own!
For developers already using this project, check the commit comments for an update on what's changed and fixed.
07/22/2013
Added exception handling in key places to improve reliability by avoiding uncatchable exceptions while cleaning up from a previous exception.
08/05/2013
Added new IsDisposed property. Connect() method checks and throws ObjectDisposedException if true.
Added locking to FtpClient.Dispose() to allow a transaction to finish before cleanup.
10/04/2013
Merged Daniel Arnold's fix in FtpSocketStream.
Added new UngracefullDisconnect property that allows you to close the control connection without sending QUIT to the server. Use this if the control connection socket is closed/reset by the server pre-maturely when calling Disconnect().
Added new ErrorMessage property to FtpReply that concatenates informational messages along with the final response message together in an effort to provide more meaningful error messages in cases such as this IIS reply which previously would trigger an FtpCommandException with the Message "End"; not helpful.
550-Access is denied.
Win32 Error: Access is denied.
Error details: File system denied the access.
550 End
The above error would now be formatted as so:
Access is denied; Win32 Error: Access is denied.; Error details: File system denied the access.; End
Which is immensly more helpful than just "End".
Fixed issues where FtpListItem parsers collection was not initialized until first directory listing. This prevented people from adding their own parsers ahead of time.
11/12/2013
Addressed issue with sequencing or PBSZ/PROT commands for data channels, they are now executed after the user has been authenticated instead of before.
01/07/2013
Readjusted path cleanup code to remove wild card/glob patterns from the path name when passed to GetListing()
Improved globbing/wildcard cleanup. If the last segment of the path in a file listing contains a glob/wildcard pattern that segment is excluded from the full path in the FtpListItem objects returned. Globs anywhere else in the path are ignored, as there is no straight forward way to expand the full path correctly.
Added comments to async examples to point out potential problem with using statement in typical use cases for the Begin* methods. Added disposed check internally when calling End* methods to see if the connection object has been disposed yet. If it has and you call an End* method, an ObjectDisposed() exception is thrown. This scenario signifies a programming error.
Merged Yuriy Gromchenko changes to address null reference exception in GetListing() method.
03/28/2014
Serveral bug fixes and reliability improvements. See the commit notes for more information.
06/04/2014
Several bug fixes and a few enhancements to logging. See commit notes for more details.
06/17/2014
Fixed UTF8 problem with cloned connections that affected some servers that don't enable UTF8 by default when supported.
Be sure to read the Documentation page for important information about using this library. It's a quick read and will be worth its weight in gold with regards to effectively using this project in your own!
For developers already using this project, check the commit comments for an update on what's changed and fixed.
07/22/2013
Added exception handling in key places to improve reliability by avoiding uncatchable exceptions while cleaning up from a previous exception.
08/05/2013
Added new IsDisposed property. Connect() method checks and throws ObjectDisposedException if true.
Added locking to FtpClient.Dispose() to allow a transaction to finish before cleanup.
10/04/2013
Merged Daniel Arnold's fix in FtpSocketStream.
Added new UngracefullDisconnect property that allows you to close the control connection without sending QUIT to the server. Use this if the control connection socket is closed/reset by the server pre-maturely when calling Disconnect().
Added new ErrorMessage property to FtpReply that concatenates informational messages along with the final response message together in an effort to provide more meaningful error messages in cases such as this IIS reply which previously would trigger an FtpCommandException with the Message "End"; not helpful.
550-Access is denied.
Win32 Error: Access is denied.
Error details: File system denied the access.
550 End
The above error would now be formatted as so:
Access is denied; Win32 Error: Access is denied.; Error details: File system denied the access.; End
Which is immensly more helpful than just "End".
Fixed issues where FtpListItem parsers collection was not initialized until first directory listing. This prevented people from adding their own parsers ahead of time.
11/12/2013
Addressed issue with sequencing or PBSZ/PROT commands for data channels, they are now executed after the user has been authenticated instead of before.
01/07/2013
Readjusted path cleanup code to remove wild card/glob patterns from the path name when passed to GetListing()
Improved globbing/wildcard cleanup. If the last segment of the path in a file listing contains a glob/wildcard pattern that segment is excluded from the full path in the FtpListItem objects returned. Globs anywhere else in the path are ignored, as there is no straight forward way to expand the full path correctly.
Added comments to async examples to point out potential problem with using statement in typical use cases for the Begin* methods. Added disposed check internally when calling End* methods to see if the connection object has been disposed yet. If it has and you call an End* method, an ObjectDisposed() exception is thrown. This scenario signifies a programming error.
Merged Yuriy Gromchenko changes to address null reference exception in GetListing() method.
03/28/2014
Serveral bug fixes and reliability improvements. See the commit notes for more information.
06/04/2014
Several bug fixes and a few enhancements to logging. See commit notes for more details.
06/17/2014
Fixed UTF8 problem with cloned connections that affected some servers that don't enable UTF8 by default when supported.
↧
Updated Release: System.Net.FtpClient (Jun 17, 2014)
System.Net.FtpClient is now available via nuget.
Be sure to read the Documentation page for important information about using this library. It's a quick read and will be worth its weight in gold with regards to effectively using this project in your own!
For developers already using this project, check the commit comments for an update on what's changed and fixed.
07/22/2013
Added exception handling in key places to improve reliability by avoiding uncatchable exceptions while cleaning up from a previous exception.
08/05/2013
Added new IsDisposed property. Connect() method checks and throws ObjectDisposedException if true.
Added locking to FtpClient.Dispose() to allow a transaction to finish before cleanup.
10/04/2013
Merged Daniel Arnold's fix in FtpSocketStream.
Added new UngracefullDisconnect property that allows you to close the control connection without sending QUIT to the server. Use this if the control connection socket is closed/reset by the server pre-maturely when calling Disconnect().
Added new ErrorMessage property to FtpReply that concatenates informational messages along with the final response message together in an effort to provide more meaningful error messages in cases such as this IIS reply which previously would trigger an FtpCommandException with the Message "End"; not helpful.
550-Access is denied.
Win32 Error: Access is denied.
Error details: File system denied the access.
550 End
The above error would now be formatted as so:
Access is denied; Win32 Error: Access is denied.; Error details: File system denied the access.; End
Which is immensly more helpful than just "End".
Fixed issues where FtpListItem parsers collection was not initialized until first directory listing. This prevented people from adding their own parsers ahead of time.
11/12/2013
Addressed issue with sequencing or PBSZ/PROT commands for data channels, they are now executed after the user has been authenticated instead of before.
01/07/2013
Readjusted path cleanup code to remove wild card/glob patterns from the path name when passed to GetListing()
Improved globbing/wildcard cleanup. If the last segment of the path in a file listing contains a glob/wildcard pattern that segment is excluded from the full path in the FtpListItem objects returned. Globs anywhere else in the path are ignored, as there is no straight forward way to expand the full path correctly.
Added comments to async examples to point out potential problem with using statement in typical use cases for the Begin* methods. Added disposed check internally when calling End* methods to see if the connection object has been disposed yet. If it has and you call an End* method, an ObjectDisposed() exception is thrown. This scenario signifies a programming error.
Merged Yuriy Gromchenko changes to address null reference exception in GetListing() method.
03/28/2014
Serveral bug fixes and reliability improvements. See the commit notes for more information.
06/04/2014
Several bug fixes and a few enhancements to logging. See commit notes for more details.
06/17/2014
Fixed UTF8 problem with cloned connections that affected some servers that don't enable UTF8 by default when supported.
Be sure to read the Documentation page for important information about using this library. It's a quick read and will be worth its weight in gold with regards to effectively using this project in your own!
For developers already using this project, check the commit comments for an update on what's changed and fixed.
07/22/2013
Added exception handling in key places to improve reliability by avoiding uncatchable exceptions while cleaning up from a previous exception.
08/05/2013
Added new IsDisposed property. Connect() method checks and throws ObjectDisposedException if true.
Added locking to FtpClient.Dispose() to allow a transaction to finish before cleanup.
10/04/2013
Merged Daniel Arnold's fix in FtpSocketStream.
Added new UngracefullDisconnect property that allows you to close the control connection without sending QUIT to the server. Use this if the control connection socket is closed/reset by the server pre-maturely when calling Disconnect().
Added new ErrorMessage property to FtpReply that concatenates informational messages along with the final response message together in an effort to provide more meaningful error messages in cases such as this IIS reply which previously would trigger an FtpCommandException with the Message "End"; not helpful.
550-Access is denied.
Win32 Error: Access is denied.
Error details: File system denied the access.
550 End
The above error would now be formatted as so:
Access is denied; Win32 Error: Access is denied.; Error details: File system denied the access.; End
Which is immensly more helpful than just "End".
Fixed issues where FtpListItem parsers collection was not initialized until first directory listing. This prevented people from adding their own parsers ahead of time.
11/12/2013
Addressed issue with sequencing or PBSZ/PROT commands for data channels, they are now executed after the user has been authenticated instead of before.
01/07/2013
Readjusted path cleanup code to remove wild card/glob patterns from the path name when passed to GetListing()
Improved globbing/wildcard cleanup. If the last segment of the path in a file listing contains a glob/wildcard pattern that segment is excluded from the full path in the FtpListItem objects returned. Globs anywhere else in the path are ignored, as there is no straight forward way to expand the full path correctly.
Added comments to async examples to point out potential problem with using statement in typical use cases for the Begin* methods. Added disposed check internally when calling End* methods to see if the connection object has been disposed yet. If it has and you call an End* method, an ObjectDisposed() exception is thrown. This scenario signifies a programming error.
Merged Yuriy Gromchenko changes to address null reference exception in GetListing() method.
03/28/2014
Serveral bug fixes and reliability improvements. See the commit notes for more information.
06/04/2014
Several bug fixes and a few enhancements to logging. See commit notes for more details.
06/17/2014
Fixed UTF8 problem with cloned connections that affected some servers that don't enable UTF8 by default when supported.
↧
Closed Unassigned: UTF8 Filenames with EnableThreadSafeDataConnections [382]
Hi,
First of all thanks for the create FtpClient library!
I had some troubles with filenames containing foreign utf8 characters. After connecting to the server (the server supports the UTF8 capability) i was able to receive the listing and all characters were correct. But i was not able to call ftpClient.OpenRead because an exception was thrown saying the file does not exits.
After some investigations i found out the the FtpCLient creates a new connection to the server for every download. The problem is that the new connection does not send the "OPTS UTF8 ON" command and therefore the download of files with foreign characters does not work.
I have set the EnableThreadSafeDataConnections property to false. Now the download of the file uses the same connection that was used to get the listing. This connection has sent the "OPTS UTF8 ON" command and the download works fine.
So i think it is a bug that new connections that are created for downloads do not send the "OPTS UTF8 ON" command.
Bernhard
Comments: Should be fixed in the latest releases
First of all thanks for the create FtpClient library!
I had some troubles with filenames containing foreign utf8 characters. After connecting to the server (the server supports the UTF8 capability) i was able to receive the listing and all characters were correct. But i was not able to call ftpClient.OpenRead because an exception was thrown saying the file does not exits.
After some investigations i found out the the FtpCLient creates a new connection to the server for every download. The problem is that the new connection does not send the "OPTS UTF8 ON" command and therefore the download of files with foreign characters does not work.
I have set the EnableThreadSafeDataConnections property to false. Now the download of the file uses the same connection that was used to get the listing. This connection has sent the "OPTS UTF8 ON" command and the download works fine.
So i think it is a bug that new connections that are created for downloads do not send the "OPTS UTF8 ON" command.
Bernhard
Comments: Should be fixed in the latest releases
↧
New Post: Issue downloading file with special characters in the filename
The latest releases send the OPTS UTF8 ON command for cloned connections now. Please give it a run and let me know the results.
↧
↧
Commented Unassigned: UTF8 Filenames with EnableThreadSafeDataConnections [382]
Hi,
First of all thanks for the create FtpClient library!
I had some troubles with filenames containing foreign utf8 characters. After connecting to the server (the server supports the UTF8 capability) i was able to receive the listing and all characters were correct. But i was not able to call ftpClient.OpenRead because an exception was thrown saying the file does not exits.
After some investigations i found out the the FtpCLient creates a new connection to the server for every download. The problem is that the new connection does not send the "OPTS UTF8 ON" command and therefore the download of files with foreign characters does not work.
I have set the EnableThreadSafeDataConnections property to false. Now the download of the file uses the same connection that was used to get the listing. This connection has sent the "OPTS UTF8 ON" command and the download works fine.
So i think it is a bug that new connections that are created for downloads do not send the "OPTS UTF8 ON" command.
Bernhard
Comments: Thanks for the quick fix!
First of all thanks for the create FtpClient library!
I had some troubles with filenames containing foreign utf8 characters. After connecting to the server (the server supports the UTF8 capability) i was able to receive the listing and all characters were correct. But i was not able to call ftpClient.OpenRead because an exception was thrown saying the file does not exits.
After some investigations i found out the the FtpCLient creates a new connection to the server for every download. The problem is that the new connection does not send the "OPTS UTF8 ON" command and therefore the download of files with foreign characters does not work.
I have set the EnableThreadSafeDataConnections property to false. Now the download of the file uses the same connection that was used to get the listing. This connection has sent the "OPTS UTF8 ON" command and the download works fine.
So i think it is a bug that new connections that are created for downloads do not send the "OPTS UTF8 ON" command.
Bernhard
Comments: Thanks for the quick fix!
↧
New Post: Issue downloading file with special characters in the filename
Seems to be working fine now.
Thanks a lot. :)
Thanks a lot. :)
↧
New Post: Issue downloading file with special characters in the filename
Great, glad we got it sorted out.
↧
Created Unassigned: Error Message: Timed out trying to connect! [383]
Everything works on the local machine. When i try to deploy that to the server, i got the message and trace below:
My FTP Code:
FtpClient conn = new FtpClient();
conn.StaleDataCheck = false;
conn.Host = url;
conn.Credentials = new NetworkCredential(userName, passWord);
conn.SetWorkingDirectory(directory);
Error Message:
Timed out trying to connect!
Error Trace:
at System.Net.FtpClient.FtpSocketStream.Connect(String host, Int32 port, FtpIpVersion ipVersions)
in c:\Users\Joseph\Desktop\netftp\System.Net.FtpClient\FtpSocketStream.cs:line 605
at System.Net.FtpClient.FtpClient.Connect()
in c:\Users\Joseph\Desktop\netftp\System.Net.FtpClient\FtpClient.cs:line 802
at System.Net.FtpClient.FtpClient.Execute(String command)
in c:\Users\Joseph\Desktop\netftp\System.Net.FtpClient\FtpClient.cs:line 726
at System.Net.FtpClient.FtpClient.Execute(String command, Object[] args)
in c:\Users\Joseph\Desktop\netftp\System.Net.FtpClient\FtpClient.cs:line 684
at System.Net.FtpClient.FtpClient.SetWorkingDirectory(String path) in c:\Users\Joseph\Desktop\netftp\System.Net.FtpClient\FtpClient.cs:line 2321
My FTP Code:
FtpClient conn = new FtpClient();
conn.StaleDataCheck = false;
conn.Host = url;
conn.Credentials = new NetworkCredential(userName, passWord);
conn.SetWorkingDirectory(directory);
Error Message:
Timed out trying to connect!
Error Trace:
at System.Net.FtpClient.FtpSocketStream.Connect(String host, Int32 port, FtpIpVersion ipVersions)
in c:\Users\Joseph\Desktop\netftp\System.Net.FtpClient\FtpSocketStream.cs:line 605
at System.Net.FtpClient.FtpClient.Connect()
in c:\Users\Joseph\Desktop\netftp\System.Net.FtpClient\FtpClient.cs:line 802
at System.Net.FtpClient.FtpClient.Execute(String command)
in c:\Users\Joseph\Desktop\netftp\System.Net.FtpClient\FtpClient.cs:line 726
at System.Net.FtpClient.FtpClient.Execute(String command, Object[] args)
in c:\Users\Joseph\Desktop\netftp\System.Net.FtpClient\FtpClient.cs:line 684
at System.Net.FtpClient.FtpClient.SetWorkingDirectory(String path) in c:\Users\Joseph\Desktop\netftp\System.Net.FtpClient\FtpClient.cs:line 2321
↧
↧
New Post: Error Message: Timed out trying to connect!
FTP connection works on the local machine. When i try to deploy that to the server, i got the message and trace below:
My FTP Code:
FtpClient conn = new FtpClient();
conn.StaleDataCheck = false;
conn.Host = url;
conn.Credentials = new NetworkCredential(userName, passWord);
conn.SetWorkingDirectory(directory);
Error Message:
Timed out trying to connect!
Error Trace:
at System.Net.FtpClient.FtpSocketStream.Connect(String host, Int32 port, FtpIpVersion ipVersions)
in c:\Users\Joseph\Desktop\netftp\System.Net.FtpClient\FtpSocketStream.cs:line 605
at System.Net.FtpClient.FtpClient.Connect()
in c:\Users\Joseph\Desktop\netftp\System.Net.FtpClient\FtpClient.cs:line 802
at System.Net.FtpClient.FtpClient.Execute(String command)
in c:\Users\Joseph\Desktop\netftp\System.Net.FtpClient\FtpClient.cs:line 726
at System.Net.FtpClient.FtpClient.Execute(String command, Object[] args)
in c:\Users\Joseph\Desktop\netftp\System.Net.FtpClient\FtpClient.cs:line 684
at System.Net.FtpClient.FtpClient.SetWorkingDirectory(String path) in c:\Users\Joseph\Desktop\netftp\System.Net.FtpClient\FtpClient.cs:line 2321
My FTP Code:
FtpClient conn = new FtpClient();
conn.StaleDataCheck = false;
conn.Host = url;
conn.Credentials = new NetworkCredential(userName, passWord);
conn.SetWorkingDirectory(directory);
Error Message:
Timed out trying to connect!
Error Trace:
at System.Net.FtpClient.FtpSocketStream.Connect(String host, Int32 port, FtpIpVersion ipVersions)
in c:\Users\Joseph\Desktop\netftp\System.Net.FtpClient\FtpSocketStream.cs:line 605
at System.Net.FtpClient.FtpClient.Connect()
in c:\Users\Joseph\Desktop\netftp\System.Net.FtpClient\FtpClient.cs:line 802
at System.Net.FtpClient.FtpClient.Execute(String command)
in c:\Users\Joseph\Desktop\netftp\System.Net.FtpClient\FtpClient.cs:line 726
at System.Net.FtpClient.FtpClient.Execute(String command, Object[] args)
in c:\Users\Joseph\Desktop\netftp\System.Net.FtpClient\FtpClient.cs:line 684
at System.Net.FtpClient.FtpClient.SetWorkingDirectory(String path) in c:\Users\Joseph\Desktop\netftp\System.Net.FtpClient\FtpClient.cs:line 2321
↧
New Post: Error Message: Timed out trying to connect!
Post a transaction log, and by the way the Host property doesn't not accept URL's or URI's. It's the hostname only.
↧
New Post: Error Message: Timed out trying to connect!
The URI is fine. That parameter brings the URI. Like i said, it works on the local machine. What is the transaction log in this case? I know it is a stupid question, but i usually catch the error message and trace. Never did a transaction log.
↧
New Post: Error Message: Timed out trying to connect!
The URI is fine. That parameter brings the URI. Like i said, it works on the local machine. What is the transaction log in this case? I know it is a stupid question, but i usually catch the error message and trace. Never did a transaction log.
↧
↧
New Post: Error Message: Timed out trying to connect!
Sorry about the duplication of the reply. My screen didn't show that reply at the first place.
↧
New Post: Error Message: Timed out trying to connect!
Check the docs and the Debug.cs example. Also you're not understanding what I'm saying about URL's, URI's. This does not work:
ftpClient.Host = "ftp://foobar.com";
ftpClient.Host = new Uri("ftp://foobar.com");ftpClient.Host = "foobar.com";↧
New Post: Separate trace listener per instance?
My program uses two instances of FtpClient, and I have set up a TextWriterTraceListener to log the interactions with the server.
Both instances log to the same file, but I would like each instance of FtpClient to log to a different file - is this possible?
Steve
Both instances log to the same file, but I would like each instance of FtpClient to log to a different file - is this possible?
Steve
↧