Uploading to AT&T PWP from DSL

[ryanker]

I recently upgraded my AT&T Worldnet connection from dialup to a DSL connection.

When I had the dialup connection, I was able to FTP my Personal Web Pages to upload.att.net (no SSL). Apparently the AT&T machine that the DSL connects me to counts as "another ISP" for the purposes of uploading PWP. THe error I get is "534 Server policy deniesUSER command on insecure connection" in response to sending my user name "USER kerry_and_ryan". The top of the session log does show the right server/port: "Connect socket #206 to 204.127.135.142, port 21...".

AT&T provides some information on FTP-ing PWP with some (not free) FTP clients. (http://www.wurd.com/pwp_faq.php#Q36) I've gone through that documentation and can't see what if anything I'm missing. The URL is still upload.att.net. Port 21.

One thing it might be is the certificates. In the info for CuteFTP Pro, they show the steps needed to creating a new certificate. Do I have to do that with Core FTP (Lite, v1.3, build 1260)?

Have you seen this problem before? Any assistance you could provide would be greatly appreciated.

Ryan

[ryanker]

Ohhhh.... "AUTH SSL". Why no, no I didn't. I just had SSL Listing and SSL Transfers checked. Checking that one extra box does wonders.

Thanks.

Ryan

[ryanker]

Now I have a different problem uploading to AT&T.

I've been able to connect and transfer files a couple times, so I know the settings are basically correct. But I can't get CoreFTP to connect consistently. When I start CoreFTP and select the connection, the log window shows the AUTH SSL, USER and PASS commands being sent. After the PASS command, the server responds with some "230- " lines of text. Sometimes clicking the Break button will cause it start working - sometimes not. The workaround I've come up with is to just keep reconnecting until either the Break button work of the connection actually works. I can usually get it going within three or four tries.

One thing I did notice is that with some connection attempts, the server's response after the PASS command ends in an otherwise empty "230-" line, while other times the last lines is a non-blank one. On the rare occasions where the connect attempt works without the Break button, the last line is "230 User kerry_and_ryan logged in." After this CoreFTP issues a SYST and other command and everything works as expected. Is there some maximum time limit after the PASS command that CoreFTP waits for confirmation of the login before it stops listening? If so, is there a way to lengthen this timeout?

Below are a couple snippets from the log.

Any thoughts?

Thanks,
Ryan McGuire

------------------
Here's the tail end of a log where the connection worked right off:
------------------
USER kerry_and_ryan
331 Password required for kerry_and_ryan.
PASS **********
230-FTP Quick Reminder:
230- If you are using a browser to FTP:
230- 1. Your Home directory listing will appear in your browser window.
230- 2. You can drag-and-drop files into the browser window from any PC
230- window.
230-
230- Note: if your ftp client sets the initial directory:
230- 1. The old initial (home) directory was "/kerry_and_ryan".
230- 2. The new initial (home) directory is just "/"
230- 3. We have upgraded the servers. Please reconfigure
230- your software!
230-
230 User kerry_and_ryan logged in.
SYST
215 UNIX Type: L8
PWD
257 "/" is current directory.
Keep alive off...
PBSZ 0
PWD
200 PBSZ 0 successful
PROT P
257 "/" is current directory.
PASV
200 Protection set to Private
Keep alive off...
Attemping Active mode transfer...
PBSZ 0
200 PBSZ 0 successful
PROT P
200 Protection set to Private
PORT 192,168,1,100,48,118
500 Illegal PORT command.
Error loading directory...
PBSZ 0
200 PBSZ 0 successful
PROT P
200 Protection set to Private
PORT 192,168,1,100,48,119
500 Illegal PORT command.
Attemping PASV mode transfer...
PBSZ 0
200 PBSZ 0 successful
PROT P
200 Protection set to Private
PASV
227 Entering Passive Mode (204,127,135,68,14,168).
LIST -al
Connect socket #152 to 204.127.135.68, port 3752...
150 Opening ASCII mode data connection for file list
226-Transfer complete.
226 Quotas on: using 9310233 of 10485760 bytes
Changed to PASV mode...
Updated site profile...
Transferred 13,005 bytes in 0.710 seconds
------------------


Here's where it usually stops:
------------------
USER kerry_and_ryan
331 Password required for kerry_and_ryan.
PASS **********
230-FTP Quick Reminder:
230- If you are using a browser to FTP:
230- 1. Your Home directory listing will appear in your browser window.
230- 2. You can drag-and-drop files into the browser window from any PC
230- window.
230-
230- Note: if your ftp client sets the initial directory:
230- 1. The old initial (home) directory was "/kerry_and_ryan".
230- 2. The new initial (home) directory is just "/"
230- 3. We have upgraded the servers. Please reconfigure
230- your software!
230-
------------------

[ryanker]

Here's something funny I noticed that might help you track down the problem. When I shrink the log window down to just one line, I can connect a lot more reliably. With a one-line log window I connect successfully probably 70% of the time. When I had it at ten lines or so, I had a batting average of less than 25%.

Just to verify that I didn't just happen to hit the AT&T server at the right time of day just now, I tried eight connections in a row with each of the two log window sizes. At one line, I made 7 out of 8. At ten lines high I got 1 out of 8.

I hope this helps.

Ryan