[RESOLVED] Type 200 is now ASCII when accessing FTP?

[drag0n_45]

Hello all,
I have an FTP server I just set up for my company with a plethora of usernames and passwords for access using a D-Link NAS device in RAID 1. I can get the exact model if need be.

When one of the clients, using Windows Vista, attempts to access the FTP, he receieves the aforementioned error. I have no idea what this means and google isn't telling me much. Does anyone have a clue?

[Hack]

Go back to your user and ask for the exact wording of the error message.

When I did: "Type 200 is now ASCII when accessing FTP" - with the quotes, Google came back and told me there were no matches found and that tells me that what has been communicated to you is an approximation of what the error actually says.

[drag0n_45]

I actually got a screenshot. 200 is now ASCII is what it said. I think it has to do with active mode FTP vs. passive. I've had the user change the mode to active and ti worked.

[dbasnett]

it is not an error. it means that the server was sent the command ascii

it is letting you know that the mode was changed. i believe the default is binary.

[drag0n_45]

That makes sense. However, I found that using the Windows FTP client when the mode was changed to ASCII that no files would display and the login would fail. No idea why this is as I don't know the nitty gritty of the FTP protocol. I have a D-LINK DNS-323 (i think...or 232) NAS device as the FTP server...

[Lord Orwell]

you can only transmit plain text files in ascii mode. binary transmissions of any type will fail.

[drag0n_45]

I understand that - but why would one computer get this message using passive FTP and another computer not? I don't understand exactly what CAUSES this problem (beyond the server requesting this connection type).

[Lord Orwell]

I understand that - but why would one computer get this message using passive FTP and another computer not? I don't understand exactly what CAUSES this problem (beyond the server requesting this connection type).

the client requests the connection type. If you're running different clients perhaps one of them has a different default. I seem to remember unix defaulting to text.

[drag0n_45]

Nope. I'm running Windows XP on all three tested machines. Mix between Home and Pro. Only one requested that it be changed to ASCII. I changed the connection type to active, which seemed to solve the problem, but passive mode works on all the other machines. Would there be something in a router that could change this, or do you know of any setting in Windows that could do that?

[dbasnett]

it would really help to see exactly how the ftp session is being initiated.

[drag0n_45]

What can I do to help you with that? The FTP server is a NAS RAID device, and the FTP client is windows. Do you know of any way to log Windows FTP sessions?

[dbasnett]

i started ftp from the command prompt
ftp> status
Not connected.
Type: ascii; Verbose: On ; Bell: Off ; Prompting: On ; Globbing: On
Debugging: Off ; Hash mark printing: Off .
ftp>
it looks like my default is ascii.

[drag0n_45]

that works. Although, is the windows FTP client the same as the command prompt FTP program? (do they use the same settings etc?)

[Lord Orwell]

i am pretty sure they are the same. The ftp command prompt program is actually a win 32 app.

[drag0n_45]

Hmm. Odd. I get the same response as dbasnett. (The fact that the FTP mode is ASCII.) However, I haven't tried to command on the offending computer yet. I would be lead to believe, though, that regardless of what mode the FTP client on his computer is using, the fact that it reverts to ASCII would make his FTP client operate with the same functionality as mine. It doesn't though - it just displays no files after that message is received.