Page 1 of 1

FTP: Unable to connect to Verizon

Posted: 17 Mar 2010, 20:45
by therube
(While we're talking FTP...)

FTP: Unable to connect to Verizon


Seems I am unable to connect to Verizon (DSL) FTP services?
Format should be ftp://username:password@ftpmysite.verizon.net
And that works with LeechFTP & in my browser, but can't seem to get it right with Salamander?

Error Message:

Code: Select all

Unable to get IP address of server "ftpmysite.versizon.net".

Error: (11004) The requested name is valid and was found in the database,
but it does not have the correct associated data being resolved for.
Verizon: FTP Server Information

(I have also found ftp://yourvzlogin:yourvspassword@members.verizon.net/ & that too works, but again not in Salamander?)

MSDN: WSANO_DATA 11004

Code: Select all

Valid name, no data record of requested type.

    The requested name is valid and was found in the database, but it does not have the correct associated data being resolved for. The usual example for this is a host name-to-address translation attempt (using gethostbyname or WSAAsyncGetHostByName) which uses the DNS (Domain Name Server). An MX record is returned but no A record—indicating the host itself exists, but is not directly reachable.
So is it something like a mickey-mouse "FTP" that they're providing, something "virtual", that it is barfing on?

Re: FTP: Unable to connect to Verizon

Posted: 17 Mar 2010, 22:36
by Petr Solin
There is typo: ftpmysite.versizon.net. Isn't it the problem? ;-)

I can connect to this FTP site, it prompts for username and password, I don't have account there, so it's all I can test for now. Let me know if it works (only problem was that typo) or send me FTP log to see what's happening next (after successful login).

Re: FTP: Unable to connect to Verizon

Posted: 18 Mar 2010, 01:32
by therube
Oh, hangs his head in shame :oops:.

Just put Salamander on the computer that I"m on now, & got right in.
I'll verify in the morning, but I'm sure you're right - typo!

Re: FTP: Unable to connect to Verizon

Posted: 18 Mar 2010, 16:34
by therube
Nope. Not a typo.
Simply not proper access in my firewall.

Must have been when I installed 3.53_beta, that I didn't give it access at the time, & so it remained.

Still, I should have known that too!