Forum Index \ DriveHQ Customer Support Forum \
Read/Reply : 18558/5
  • cafc_1234
  • (3 posts)

 

Unable to connect to 66.22.9.50:21 

 

Why?

 

 

 

 

 

Filezilla dice questo:

Stato:   Connessione a 66.22.9.50:21...

Errore:  Timeout connessione dopo 20 secondi di inattività

Errore:  Impossibile collegarsi al server

Stato:   In attesa di un nuovo tentativo...

Stato:   Connessione a 66.22.9.50:21...

Errore:  Timeout connessione dopo 20 secondi di inattività

Errore:  Impossibile collegarsi al server

 


8/11/2021 12:20:33 AM

  • DriveHQ_Support
  • (651 posts)
Subject: Re:Unable to connect to 66.22.9.50

I tested it here and it works fine. ( Our FTP servers and web servers are monitored 24x7. We have no reported issues. )

Are you able to access www.DriveHQ.com website? Could you please try proftp.drivehq.com instead of ftp.drivehq.com? The IP address of proftp.drivehq.com is 66.220.9.51

If you are a group member, please contact your group administrator and test with a different FTP account  (sub-account). Check if the problem happens to other sub-users.

We guess there is a network connection problem from your location to our server. If possible, please try from a different location, e.g. from your home, or use Mobile Hotspot. 

 


Reply
8/11/2021 12:41:20 AM

  • cafc_1234
  • (3 posts)
Subject: Re:Unable to connect to 66.22.9.50

 

 

 

this is from my phone

 

 

 


Reply
8/11/2021 1:59:44 AM

  • DriveHQ_Support
  • (651 posts)
Subject: Re:Unable to connect to 66.22.9.50

Our FTP service works fine. It is monitored 24x7. At any time, we have huge number of concurrent users. Please read our first reply. If you still cannot pinpoint the problem, please email/call DriveHQ customer support directly. 

FYI, DriveHQ servers cannot be ping-ed. But it does not affect the service. For example:

Users should have no problem accessing www.DriveHQ.com website.

 

 


Reply
8/11/2021 9:08:51 AM

  • cafc_1234
  • (3 posts)
Subject: Re:Unable to connect to 66.22.9.50

 Hi,

ok, 66.22.9.50 is not pingable. Also 66.220.9.51 is not pingable.

But 66.220.9.51 has the port 21 open, the 66.22.9.50 shows the port 21 closed

why?

 

emailed to the support 2 days agos without any replay

 

 

 


Reply
8/12/2021 1:06:31 AM

  • DriveHQ_Support
  • (651 posts)
Subject: Re:Unable to connect to 66.22.9.50

 Please use the correct IP address 66.220.9.50 (Not 66.22.9.50)


Reply
8/12/2021 1:46:14 AM

Quickly Reply

Please logon and reply, Not DriveHQ Member?


Leading Cloud Surveillance service

Leading Enterprise Cloud IT Service Since 2003