Your best friend for file transfer.
Fetch
can't connect to ATT personal pages server (3 posts)
- Started 17 years ago by krissel
- Latest reply 17 years ago from krissel
-
krissel Member
-
Scott McGuire Administrator
Hi,
We're sorry, but Fetch does not support FTP with SSL at this time, and AT&T's servers do not accept anything but FTP with SSL when you're not connecting from their network, so you will not be able to connect to AT&T's servers with Fetch.
You wouldn't have run into this problem on dialup because you were connecting pretty much directly to AT&T's servers; but when you're coming in from another Internet provider, they require FTP with SSL.
Adding support for FTP with SSL is on our to-do list for the future.
The only workaround is to connect to AT&T using dialup, or to use a different FTP client, like Interarchy.
You should be able to connect to most other servers without a problem - very few require FTP with SSL to the exclusion of anything else.
Sorry not to have a better answer for you,
Scott McGuire
Fetch Softworks -
krissel Member
Thanks for the quick reply.
At least I know it's not something I'm doing wrong. I've used Fetch happily for many, many years and feel kind of like a traitor using another application but I guess I don't have a choice in this case.
Am looking forward to Fetch's having this ability in the future.
Thanks again. :)
- Page 1
While on dialup I used ATT worldnet personal pages on their server. I've since gone to cable but kept a basic account with ATT. I can access the ATT server OK via dialup but can't via FTP cable despite following all their instructions to do so.
Using passive FTP gets me a message that I need to use a secure method. But when I choose SFTP after a minute of trying I get Fetch's message "could not be opened because the connection to the SFTP server could not be establishe or was lost." Additonally it advises that I should verify that I have the correct hostname, etc.
I do.
I've tried unchecking the send ADAT and MACB commands and tried MD5 but none of those made any diffence. I also tried port 21 but no luck there either.
I can use Fetch (5.05) to access other servers in other places without difficulty.
Here's the kicker, I downloaded Interarchy and it connected immediately without my even specifying it use SFTP. It apparently does so when available using SSL(AUTH TLS).
Here is the transcript from the failed connection with Fetch:
220-
220-Welcome to the AT&T WorldNet (sm) Personal Web Pages FTP server 204.127.135.68
220-You are accessing it from host 68.192.174.110
220-at Thu Jun 15 03:26:45 2006 GMT
220-
220-This is the "Access from Anywhere" PWP FTP server, and is available
220-from the general internet. However, you MUST use an SSL enabled
220-FTP client. A list of such clients can be found at:
220-
220- http://home.att.net/ftp_anywhere.html
220-
220-For more tips on how to configure your FTP or Web Publishing
220-software to work with Personal Web Pages@att.net, please follow
220-the instructions on these web pages:
220-
220- http://www.wurd.com/pwp_ftpindex.php
220- or
220- http://www.wurd.com/pwp_editors.php
220-
220- ****IMPORTANT****
220-
220-Any access to and use of this FTP server, authorized or
220-unauthorized, is governed by and constitutes your acceptance of
220-the terms and conditions imposed on the following web page:
220-
220- http://home.att.net/pwp_gia_terms.html
220-
220-Use your EMAIL-ID at the login prompt (the portion before the "@").
220-Use your EMAIL PASSWORD at the password prompt.
220-
220-
220 PWPFTPD 2.02 (6feb2002) Server (AT&T WorldNet (sm) Personal Web Pages FTP GIA server) [204.127.135.68]
Here's the successful from Interarchy:
Send Version Control query to www.interarchy.com
GET /sivc/interarchy?A&U&08018000&C0904501&wvYlnxcJ&C0A80064&00001039 HTTP/1.0
Accept: */*
Host: www.interarchy.com
User-Agent: Interarchy/8.0.1
Pragma: no-cache
Cache-Control: no-cache
HTTP/1.1 200 OK
Date: Thu, 15 Jun 2006 03:31:46 GMT
Server: Apache/1.3.36 (Unix) mod_perl/1.29
Vary: negotiate
TCN: choice
Cache-Control: no-cache
Expires: Tue, 13 Jun 2006 03:31:46 GMT
Pragma: no-cache
Content-Length: 298
Connection: close
Content-Type: text/plain
ReleaseVersion: 08018000
ReleaseURL: http://s3.amazonaws.com/stairways/interarchy-801.dmg
TestVersion: 08018000
TestURL: http://s3.amazonaws.com/stairways/interarchy-801.dmg
InfoURL: http://www.interarchy.com/
BusyStatus: 6AHT817VKTPWV1DA59
AutoQueryIntervalM: 10080
BusyStatus: G1HGKN8VW9DA9E08L2
220-
220-Welcome to the AT&T WorldNet (sm) Personal Web Pages FTP server 204.127.135.68
220-You are accessing it from host 68.192.174.110
220-at Thu Jun 15 03:37:01 2006 GMT
220-
220-This is the "Access from Anywhere" PWP FTP server, and is available
220-from the general internet. However, you MUST use an SSL enabled
220-FTP client. A list of such clients can be found at:
220-
220- http://home.att.net/ftp_anywhere.html
220-
220-For more tips on how to configure your FTP or Web Publishing
220-software to work with Personal Web Pages@att.net, please follow
220-the instructions on these web pages:
220-
220- http://www.wurd.com/pwp_ftpindex.php
220- or
220- http://www.wurd.com/pwp_editors.php
220-
220- ****IMPORTANT****
220-
220-Any access to and use of this FTP server, authorized or
220-unauthorized, is governed by and constitutes your acceptance of
220-the terms and conditions imposed on the following web page:
220-
220- http://home.att.net/pwp_gia_terms.html
220-
220-Use your EMAIL-ID at the login prompt (the portion before the "@").
220-Use your EMAIL PASSWORD at the password prompt.
220-
220-
220 PWPFTPD 2.02 (6feb2002) Server (AT&T WorldNet (sm) Personal Web Pages FTP GIA server) [204.127.135.68]
AUTH TLS
234 AUTH TLS successful
SSL Certificate verify failed: unable to get local issuer certificate (20)
Certificate error 20
§PBSZ 0
§200 PBSZ 0 successful
§PROT P
§200 Protection set to Private
§USER krissel
§331 Password required for krissel.
§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 "/krissel".
§230- 2. The new initial (home) directory is just "/"
§230- 3. We have upgraded the servers. Please reconfigure
§230- your software!
§230-
§230 User krissel logged in.
§PWD
§257 "/" is current directory.
§TYPE A
§200 Type set to A.
§PASV
§227 Entering Passive Mode (204,127,135,68,14,110).
§LIST
§150 Opening ASCII mode data connection for file list
§226-Transfer complete.
Can you help?
Posted 17 years ago #