Can't download!

[HiddenKnowledge]

Could you send me your login credentials in a pm?
Thanks in advance.

You can do that in WHM, you know.

Just sign in to his account on WHM, just add a user and try it. :P

I think you can also login to his FTP account, online by going to his cPanel.

You can do all of that without knowing his login credentials. :)

---

Is it possible that your ISP is blocking those ports for any reason? Are you behind a firewall?

Less likely. It's odd for a host to block FTP. Maybe blocking the ability for him to accept FTP incoming connections, but we use FTP all over - so I think he should be able to connect.

Maybe a firewall is blocking it.

Just seems odd. Haven't really heard of this issue. I thought FTP:21 was a safe protocol.

I decided to ask his login details, because I found this was the best way to be sure it wasn't a problem on his account. And about the firewall blocking port 21, yes it is odd, but a incorrect setup firewall/weird isp might block it.

[Arthur]

Oh yeah. I forgot to mention that Net2FTP works fine, even though a local client doesn't.

[RichardGv]

• Try if your FileZilla could connect to 72.55.147.241
  
• If not, do this command under your console and post the output:
  
  Code:

  tracepath 72.55.147.241
# If the command above does not exist
traceroute 72.55.147.241
# If the command still does not exist
/usr/sbin/tracepath 72.55.147.241

[nobody]

For Windows:
Please open the command prompt (Start menu -> RUN -> enter "cmd" and press run).

For Linux:
Open a terminal window (however your GUI handles this)

Enter:

ftp
open 72.55.147.241
(then answer prompted questions)

The above should look [about] like this:

ftp> open 72.55.147.241
Connected to 72.55.147.241.
220---------- Welcome to Pure-FTPd [privsep] [TLS] ----------
220-You are user number 18 of 300 allowed.
220-Local time is now 06:54. Server port: 21.
220-This is a private system - No anonymous login
220-IPv6 connections are also welcome on this server.
220 You will be disconnected after 15 minutes of inactivity.
User (yourdomainname.com:(none)): [your cpanel username]
331 User cpanelusername OK. Password required
Password: [your cpanel password]
230 OK. Current restricted directory is /
ftp>

*use the IP address as this will not use DNS at all (to rule out any DNS issue here).

Please then send a screen shot or copy and paste any/all output here. This will test the most basic ability to connect to FTP.

If you do not get any of the output and "ftp>" appears again, please provide a traceroute as stated above by richard. (ps. for windows the command is tracert)

[Arthur]

Thanks for reminding me about the ftp command. Saved a lot of time testing. Actually, I'm running OS X, and am quite familiar with terminal.
ftp on 72.55.147.241 worked perfectly fine. When I asked it for acg.n1fty.com, I got a timeout.
traceroute on acg.n1fty.com got an unknown host error, but traceroute on 72.55.147.241 worked fine.

I guess that proves it is indeed a DNS error of some kind...
And that I can use that ip instead of my url for ftp...

[nobody]

I am glad you are now able to connect to FTP.

To help us debug the DNS issue, could you please provide the output of the dig/nslookup command from terminal of the domain n1fty.com and acg.n1fty.com?

[Arthur]

> dig n1fty.com

; <<>> DiG 9.6.0-APPLE-P2 <<>> n1fty.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 13680
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;n1fty.com. IN A

;; Query time: 79 msec
;; SERVER: 209.18.47.61#53(209.18.47.61)
;; WHEN: Wed Feb 1 17:39:25 2012
;; MSG SIZE rcvd: 27

> dig acg.n1fty.com

; <<>> DiG 9.6.0-APPLE-P2 <<>> acg.n1fty.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 7653
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;acg.n1fty.com. IN A

;; Query time: 81 msec
;; SERVER: 209.18.47.61#53(209.18.47.61)
;; WHEN: Wed Feb 1 17:39:33 2012
;; MSG SIZE rcvd: 31

> nslookup n1fty.com
;; Got SERVFAIL reply from 209.18.47.61, trying next server
Server: 209.18.47.61
Address: 209.18.47.61#53

** server can't find n1fty.com: NXDOMAIN

> nslookup acg.n1fty.com
;; Got SERVFAIL reply from 209.18.47.61, trying next server
Server: 209.18.47.61
Address: 209.18.47.61#53

** server can't find acg.n1fty.com: NXDOMAIN

[nobody]

It appears your ISP blocks the DNS. Otherwise everyone else would have the same problem you are having with DNS.

Try to use google DNS or opendns.


8.8.8.8 and 8.8.4.4 (for google's dns servers)

Then try again and see if the problem is solved.