Over the last five weeks we’ve been looking at IIS FTP. This last week we take a look at troubleshooting techniques for when FTP just doesn’t work as you hoped. When it works, IIS FTP works consistently and works very well. However, when it doesn’t work it can be difficult to narrow down to the root cause.

This week we explore some troubleshooting techniques and review the following FTP connectivity stack.

• DNS Resolution/Network Connectivity
• Firewall Access (Passive/Active / Secure?)
• IIS Bindings
• Authentication
• Authorization
• Isolation Mode / File paths
• NTFS Permissions

For reference, there were two external resources which I referenced. They are:

• Flushing the IIS FTP logs to disk http://weblogs.asp.net/owscott/archive/2012/02/03/flush-http-and-ftp-logs-in-iis.aspx
• One of the more advanced steps is to use Event Tracing. Here is the link I referred to. http://blogs.msdn.com/b/robert_mcmurray/archive/2008/08/29/ftp-and-etw-tracing.aspx

This week's video lesson is the final of a 5-week mini-series on IIS FTP. The five weeks include:

• Week 1: IIS FTP Basics
• Week 2: IIS FTP and IIS Manager Users
• Week 3: IIS FTP and User Isolation
• Week 4: IIS FTP Firewall settings, Active vs. Passive
• Week 5: IIS FTP Troubleshooting

This is week 48 of a 52 week series. You can view past and future weeks in the section below.

Having problems viewing on your mobile device? Click here instead.

About Scott Forsyth

Senior Systems Engineer at ORCS Web, Inc (www.orcsweb.com) and co-founder of Vaasnet (www.vaasnet.com). Microsoft MVP for IIS. ASPInsider. Strengths are IIS, ASP.NET, DNS, Windows Server, and Hyper-V. This author has published 50 articles on DotNetSlackers. View other articles or the complete profile here.