.UK.com and .GB.com domains

I cannot get SmartFTP to connect successfully to either .UK.com or .GB.com domains (eg mydomain.uk.com)

I appreciate that when registering domains ending with .uk.com or .gb.com, you are technically only buying subdomains (as they are not true TLDs). However, they do behave just like any other TLD in all other respects (eg when uploading / downloading via Dreamweaver).

I want to use FTP over SSL, for which I can't use DW, so instead need to use SmartFTP.

But SmartFTP insists on appending further .TLD info to the end of my already valid urls (eg mydomain.uk.com is turned into mydomain.uk.com.co.uk by SmartFTP). I can't find any way to stop this happening.

Can you please address this issue?

Hello ..

SmartFTP does not append anything to the host name you enter. Try to connect with the IP address instead.


Hi Mat

Will look into the IP address suggestion, thanks.

However, I can assure you that extra stuff is being appended to the host names. And if I'm not doing it (which I'm definitely not), that really only leaves SmartFTP.

OK, so slight delay on my side...

However: can't use an IP address.

Also, I can categorically promise you that SmartFTP is still appending .co.uk onto the end of domain.uk.com - every single time I try to connect to that domain. There's no way I can find to stop it or to delete it once it's been added.

Is it possible that the software needs a tweak to recognise .uk.com (and .gb.com) as valid top level domains?

That would seem to be the logical cause of the issue to an idiot layman such as myself.

Mat - this is still a problem, including with version 4.0.1137.0

Would appreciate a fix being sorted out, please.

It's not a problem with SmartFTP but with your dns resolver.

Can you elaborate, please? I've read up quickly on Wikipedia, etc and am still none the wiser.

If I type the domain.uk.com (I use "domain" as a generic replacement for what I'm actually using) directly into a browser address bar, it loads the site correctly. It does so whether I enter:

or http://www.domain.uk.com

Dreamweaver also connects to the domain successfully using exactly the same ftp address (ftp.domain.uk.com) as I am asking SmartTFP to use.

So why is it only SmartFTP that has a problem with resolving the address? Surely the issue is specific to your software?

Whilst this looks like a longwinded rant, I do appreciate your help with this - am just trying to explain how I'm seeing the issue from my side.

SmartFTP uses the standard way/API to resolve the host name. I do not see anything wrong in the code either and we have been using it for more than 10 years now. Try it with another computer in your network, or on a different network. You can also try to change your DNS server to:
Google public dns:
Instructions on how to configure the network settings (DNS server) can be found at: http://code.google.com/speed/public-dns/

If the problem lay with my dns resolver, surely I wouldn't be able to open this site in a web browser or access it with Dreamweaver? Or am I missing something?

Can you please post the log from the remote browser?

I did some tests here:
[00:57:35] SmartFTP v4.0.1137.0
[00:57:35] Resolving host name "ftp.orange.uk.com"
[00:57:35] Connecting to Port: 21
[00:57:36] Connected to ftp.orange.uk.com.
[00:57:36] 220 Microsoft FTP Service
[00:57:36] USER anonymous
[00:57:37] 331 Anonymous access allowed, send identity (e-mail name) as password.

No co.uk is added to the host name I have entered.

Upon entering ftp.domain.uk.com into the remote browser bar, plus login and p/w, then clicking the Go button, the log file says:

[18:52:19] SmartFTP v4.0.1137.0
[18:52:19] Resolving host name "ftp.domain.uk.com.co.uk"
[18:52:19] Unable to resolve host name.
[18:52:19] Active Help: https://www.smartftp.com/support/kb/81
[18:52:19] Connect failed. Waiting to retry (30s)...
[18:52:33] Aborted by user.

Go to the menu: File->New Remote Browser. Then enter the host, username and password. Click OK to connect.

Please try this first:
Go to the menu: File->New Remote Browser. Then enter the host, username and password. Click OK to connect.

Oooh - progress!

That worked. Up to a point. But this time because of some issue with IP addresses.

"500 I won't open a connection to xxx.xxx.x.x (only to xx.xxx.xx.xxx)"

Best discussed with hosting provider?

Please post the log from the remote browser.

I think the server thinks that you are opening the data connection from a different ip address than the one you use for the control connection. You probably have to set the encryption for the data connection (FTP->Connection->SSL) to clear instead of private.

OK, experimented with that. Didn't seem to work at first, but after setting to clear, then back to private (testing in between each time), it finally let me in after everything was put back to private.

Thank you very much indeed for your help with this - it's greatly appreciated.

Just hope it still works tomorrow