Log on FTP From Local Machine

I had this question after viewing Allow Local User to Log On FTP.

More specifically, now that works and local user can log on, the developer has written a program that does several things. New problem is that when the program is running on a dev box it works, but when it runs on the server that is hosting FTP, it fails. Server connects and then fails with "connection closed by remote host".

I tried this myself running a command prompt on the server. Same problem, connection closes as soon as it opens. The odd thing is I am sure I tried this before when working on my previous question.

The only thing that I found works is if you log on using the IP address. If you log on by the server name (short or FQDN) or localmachine, it fails. However the goal is to make the program portable, so specifying the IP address is not the best way to do it.

LVL 26
Brian BIndependant Technology ProfessionalAsked:
Who is Participating?
Dan McFaddenConnect With a Mentor Systems EngineerCommented:
Do you have a DNS CNAME in place?

I have an FTP Site that exhibits the same symptoms.  The IP Address works, the server FQDN drops the connection.  But if I use the DNS Alias that my end-users use, it works fine locally.

Dan McFaddenSystems EngineerCommented:
1. Have you compared the configuration of the DEV FTP site and the other location's site?
2. Is the Windows Firewall on?
3. How is the FTP site binding setup?  Can you post a screenshot?
4. Is the FTP site using a dedicated AppPool?
4a.  How is the AppPool setup?
5. Are there any access rules on what IP addresses are allow to connect?  
5a. Look in the FTP IP Address and Domain Restrictions feature if installed. Check the feature settings for this item.
5b. Is the default access for unspecified clients setting set to Allow or Deny?
6. logging enabled on the site?

Brian BIndependant Technology ProfessionalAuthor Commented:
Thanks for the response, maybe I can shorten the list of questions a bit by clarifying a few things:

The dev box I mentioned is only running the program, it is still talking to the same server. Only when the program is running locally on the server it fails.
On the server if I run FTP and "open <servername>" it returns a message "connection closed by remote host". If I do "open" (the IP of the server), it works and gives a prompt to log on.
I did try it with the firewall off just to be sure and it didn't make any difference.
I also tried another FTP server at another site and it has the same issue (although it is 2008 R2).
Everything is set up at default except for using domain authentication.

I will gather the information later, but does any of that eliminate some of your questions?
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

Dan McFaddenSystems EngineerCommented:
Does the IP Address of the server match the host name in DNS?  What are the results when you run the following commands?

1. on the server with issue:  open command prompt
2. type:  nslookup <ServerName>
3. type:  nslookup <IPOfTheServer>

Also, have you tried FTP'ing using the FQDN of the server?  FQDN = servername.domain.extension.  For example:  ftp.microsoft.com, where "ftp" is the servername of the FTP server.

Brian BIndependant Technology ProfessionalAuthor Commented:
Yes, the IP address is registered correctly. Using FQDN or short name both fail. Only using the IP address works.

Again, this is all when running FTP directly on the server hosting it. Accessing from another system works all ways.
Brian BIndependant Technology ProfessionalAuthor Commented:
Yes, creating a CNAME pointing to the FQDN works with local logon. Gives us the best portability as well if the FTP ever moves.
All Courses

From novice to tech pro — start learning today.