Unexpected null reply received

Question

Hello

I have been evaluating this software in consideration of purchasing the 'PRO' edition for a current project I am working on (I NEED SSL capability.) Edtftpnet was working excellently in testing until today, when I tried to FTP a test file to a potential client and received the following error message when beginning an FTP session [code: ftpclient.login(user, password)]:

"Unexpected null reply received".

Any ideas? Is this a sign that the client is behind a firewall/proxy which the 'Pro' edition will handle? Is this an FTP, Proxy, Firewall setting that the client needs to change? Am I doing something wrong? (I have tested it successfully for 4 other clients.)

Also, I am able to successfully connect, 'put', 'get', etc using WS_FTP to the 'problem clients' site.

Any help would be much appreciated.
Thanks
Logic

Answer 1

Hi

Do you have a log file available? And can a command line FTP client (e.g. ftp.exe) connect successfully?

Hello

I have been evaluating this software in consideration of purchasing the 'PRO' edition for a current project I am working on (I NEED SSL capability.) Edtftpnet was working excellently in testing until today, when I tried to FTP a test file to a potential client and received the following error message when beginning an FTP session [code: ftpclient.login(user, password)]:

"Unexpected null reply received".

Any ideas? Is this a sign that the client is behind a firewall/proxy which the 'Pro' edition will handle? Is this an FTP, Proxy, Firewall setting that the client needs to change? Am I doing something wrong? (I have tested it successfully for 4 other clients.)

Also, I am able to successfully connect, 'put', 'get', etc using WS_FTP to the 'problem clients' site.

Any help would be much appreciated.
Thanks
Logic

Answer 2

Some more info for you:

"Unexpected null reply received" means that when the login command was sent, the FTP server didn't reply.

If it happens on login, then it would make no difference if active or passive mode is used.

There must be a firewall or proxy setting being used - check if WS_FTP is using one.

Answer 3

> Do you have a log file available? And can a command
> line FTP client (e.g. ftp.exe) connect successfully?

I do not have a log file available. I *AM* able to connect to the site using FTP.exe.

> There must be a firewall or proxy setting being
> used - check if WS_FTP is using one.

As far as I can tell, WS_FTP does NOT have the 'Firewall' setting set. Would I be able to connect to the site using FTP.exe if there was a firewall or proxy?

The code I am using is as follows (fyi, the exception is thrown at the ftp.User("username") line:

ftp = new FTPClient();
ftp.RemoteHost = "123.123.123.123";
ftp.Connect();
ftp.User("aUser"); //Error here...
ftp.Password("aPassword");

Logic

Answer 4

FYI, I have also used the following code with the same result:

ftp = new FTPClient("123.123.123.123", 21);
ftp.Login("aUser", "aPassword"); // <--Error here

Thanks,
Logic

Answer 5

Hmm, very confusing.

Are you using the latest version of edtFTPnet (1.1.5)? If not please upgrade to make sure we are talking about the same code.

Secondly, can you post the log of how ftp.exe connects. Start ftp.exe with no arguments. Then type 'debug'. Then 'open 123.123.123.123'. Then login as usual - this will show what commands are being sent.

Lastly, can you run demo.bat in the demo directory of the distribution?

demo hostname user password

This just means I know exactly what code you are using

FYI, I have also used the following code with the same result:

ftp = new FTPClient("123.123.123.123", 21);
ftp.Login("aUser", "aPassword"); // <--Error here

Thanks,
Logic

Answer 6

>
> Are you using the latest version of edtFTPnet (1.1.5)?
>

Yes, that was the first thing I did when i got the error (i had been using 1.1.4 which also got the error.)

>
> can you post the log of how ftp.exe connects.
>

C:\WINDOWS\SYSTEM32>ftp.exe
ftp> debug
Debugging On .
ftp> open 123.123.123.123
Connected to 123.123.123.123.
220-Microsoft FTP Service
This transmission is confidential and intended solely for the person or
organization to which it is addressed. It may contain privileged and
confidential information. If you are not the intended recipient, you
should not copy, distribute or take any action in reliance on it.
220
User (123.123.123.123:(none)): myUserLogin
---> USER myUserLogin
331 Password required for myUserLogin.
Password:
---> PASS myPassword
230-This transmission is confidential and intended solely for the person or
organization to which it is addressed. It may contain privileged and
confidential information. If you are not the intended recipient, you
should not copy, distribute or take any action in reliance on it.

230 User myUserLogin logged in.
ftp>

>
> can you run demo.bat in the demo
> directory of the distribution?
>

C:\...\edtftpnet-1.1.5\demo>demo 123.123.123.123 myUserLogin myPassword

C:\...\edtftpnet-1.1.5\demo>set FTPDLL="edtftpnet-1.1.5.dll"

C:\...\edtftpnet-1.1.5\demo>del /F *.dll

C:\...\edtftpnet-1.1.5\demo>del /F *.exe
Could Not Find C:\...\edtftpnet-1.1.5\demo\*.exe

C:\...\edtftpnet-1.1.5\demo>copy /Y ..\bin\*.dll .
..\bin\edtftpnet-1.1.5.dll
..\bin\test-edtftpnet-1.1.5.dll
2 file(s) copied.

C:\...\edtftpnet-1.1.5\demo>copy /Y ..\bin\"edtftpnet-1.1.5.dll" test.dll
1 file(s) copied.

C:\...\edtftpnet-1.1.5\demo>csc /out:rundemo.exe /target:exe /reference:"edtftpnet-1.1.5.dll" Demo.cs
Microsoft (R) Visual C# .NET Compiler version 7.10.6001.4
for Microsoft (R) .NET Framework version 1.1.4322
Copyright (C) Microsoft Corporation 2001-2002. All rights reserved.


C:\...\edtftpnet-1.1.5\demo>rundemo.exe 123.123.123.123 myUserLogin myPassword
INFO [Demo] 19 Mar 2005 12:48:09.316 : Connecting
DEBUG [EnterpriseDT.Net.Ftp.FTPClient] 19 Mar 2005 12:48:09.547 : Connecting to 123.123.123.123:21
DEBUG [EnterpriseDT.Net.Ftp.FTPControlSocket] 19 Mar 2005 12:48:13.232 : 220-Microsoft FTP Service
DEBUG [EnterpriseDT.Net.Ftp.FTPControlSocket] 19 Mar 2005 12:48:13.422 : This transmission is confidential and intended solely for the person or
DEBUG [EnterpriseDT.Net.Ftp.FTPControlSocket] 19 Mar 2005 12:48:13.422 :
DEBUG [EnterpriseDT.Net.Ftp.FTPControlSocket] 19 Mar 2005 12:48:13.422 : organization to which it is addressed. It may contain privileged and
DEBUG [EnterpriseDT.Net.Ftp.FTPControlSocket] 19 Mar 2005 12:48:13.422 :
DEBUG [EnterpriseDT.Net.Ftp.FTPControlSocket] 19 Mar 2005 12:48:13.422 : confidential information. If you are not the intended recipient, you
DEBUG [EnterpriseDT.Net.Ftp.FTPControlSocket] 19 Mar 2005 12:48:13.422 :
DEBUG [EnterpriseDT.Net.Ftp.FTPControlSocket] 19 Mar 2005 12:48:13.422 : should not copy, distribute or take any action in reliance on it.
DEBUG [EnterpriseDT.Net.Ftp.FTPControlSocket] 19 Mar 2005 12:48:13.422 :
DEBUG [EnterpriseDT.Net.Ftp.FTPControlSocket] 19 Mar 2005 12:48:13.422 : 220
INFO [Demo] 19 Mar 2005 12:48:13.422 : Logging in
DEBUG [EnterpriseDT.Net.Ftp.FTPControlSocket] 19 Mar 2005 12:48:13.432 : ---> USER myUserLogin
DEBUG [Demo] 19 Mar 2005 12:48:13.432 : at EnterpriseDT.Net.Ftp.FTPControlSocket.ReadReply()
at EnterpriseDT.Net.Ftp.FTPControlSocket.SendCommand(String command)
at EnterpriseDT.Net.Ftp.FTPClient.Login(String user, String password)
at Demo.Main(String[] args)
C:\...\edtftpnet-1.1.5\demo>

Answer 7

Thanks. I assume ftp.exe and demo.bat are being run on the same client machine?

This is pretty weird. There is no firewall problem - it is connecting without any problem.

Answer 8

We've got an idea - could you send an email to support at enterprisedt dot com and we'll send you a release that might fix the problem?

Answer 9

>
> Thanks. I assume ftp.exe and demo.bat are
> being run on the same client machine?
>

Yes, they are both running on the same box (client machine).

>
> could you send an email to support at
> enterprisedt dot com and we'll send you
> a release that might fix the problem?
>

Sure, what would you like me to say in the email? :^)
Should i just direct them to this topic?

Thanks
Logic

Answer 10

Yes, just title it "Unexpected null reply received" and include the URL to this thread

>
> Thanks. I assume ftp.exe and demo.bat are
> being run on the same client machine?
>

Yes, they are both running on the same box (client machine).

>
> could you send an email to support at
> enterprisedt dot com and we'll send you
> a release that might fix the problem?
>

Sure, what would you like me to say in the email? :^)
Should i just direct them to this topic?

Thanks
Logic