AD users can't log into FTP site hosted on Win 2003 Svr

Have a Windows 2003 SP2 member server hosting a single FTP site on port 21 without anonymous access. The Home Directory is set to a local folder (i.e. C:\Folder\FTPSiteFolder\) with Read/Write permissions in IIS. The Users group, Administrators group, System account, and a specific user account for outside access to the FTP all have Modify or greater NTFS permissions. When browsing to the FTP site in IE 7 from inside the network or even locally on the server hosting the FTP site both produce the same results... the login prompt appears but no user account (even the adminsitrator) can login. There is no error message and the login prompt just reappears.

The Windows event log on the server shows a Warning with Event ID 100, Source: MSFTPSVC, Description: The server was unable to logon the Windows NT account 'administrator' due to the following error: Logon failure: unknown user name or bad password.  The data is the error code.

NOTE: If I configure Anonymous access the site works fine.
BiziteksAsked:
Who is Participating?
 
evanmcnallyConnect With a Mentor IT ConsultantCommented:
You need to specify a default domain name in the IIS metabase.

Try the steps from this link (also pasted below) http://support.microsoft.com/kb/200475

Resolution 4
Try using the command line FTP utility and specify the FTP username in DOMAIN\Username format when you log into the FTP Site. If this works, then you can either instruct all users to log on by using DOMAIN\Username format, or you can specify the default authentication domain that the FTP Service should use when authenticating accounts that do not exist locally and that were not entered in the DOMAIN\Username format. To do this you must make changes to the Metabase.

To specify a default logon domain so users do not have to type DOMAIN\Username when logging on to the FTP Server, you can either use the Windows Script Host (if it was installed during the Windows NT Option Pack setup) or the NTOP utility Mdutil.exe.

Both methods are described below.

To use the Windows Script Host method, use one of the following methods depending on the version of IIS that you are running:

Note In IIS 6.0, you can resolve this issue by modifying the metabase only when the FTP isolation type is "Isolated (Active Directory)" or if the UserIsolationMode property is set to 2.
IIS 6.0
1. Change to the %Systemroot%\Inetpub\Adminscripts directory.
2. Type the following:
Adsutil Set MSFTPSVC/DefaultLogonDomain "Domain Name"
Make sure when you type in the Domain Name that it is enclosed in quotation marks.
3. Stop and restart the FTP Service.

IIS 5.0
1. Change to the %Systemroot%\Inetpub\Adminscripts directory.
2. Type the following:
Adsutil Set MSFTPSVC/DefaultLogonDomain "Domain Name"
Make sure when you type the Domain Name that it is enclosed in quotation marks.
3. Stop the FTP Service, and then restart the FTP Service.

IIS 4.0
1. Change to the %systemroot%\system32\inetsrv\adminsamples directory.
2. Type the following:
cscript //h:cscript
This sets Cscript as the default WSH interpreter.
3. Type the following:
Adsutil Set MSFTPSVC/DefaultLogonDomain "Domain Name"
Make sure when you type in the Domain Name that it is enclosed in quotation marks.
4. Stop the FTP Service, and then restart the FTP Service.
If the Windows Script Host was not installed during the NTOP setup, use Mdutil.exe. as follows: 1. Copy Mdutil.exe. from the Windows NT Option Pack compact disc to the %WINDIR%\System32\ directory.

Make sure to copy Mdutil.exe. from the appropriate platform directory on the compact disc.
2. Open a command prompt, and change to the %WINDIR%\System32 directory.
3. Execute the command below replacing <DomainName> with the name of the accounts domain you want to authenticate your user against by default: mdutil set msftpsvc/DefaultLogonDomain -utype UT_Server -dtype String -value <DomainName>

mdutil set msftpsvc/DefaultLogonDomain -utype UT_Server -dtype String -value <DomainName>
                        
Make sure that <DomainName> is typed without quotes.
4. When the command completes successfully, stop and restart the FTP Service.
0
 
evanmcnallyIT ConsultantCommented:
Try submitting the usename as windows DOMAINNAME\USERNAME  or as username@windowsdomainname.com

This should force your member server to check in with a domain controller rather than looking at its local account database.
0
 
BiziteksAuthor Commented:
OK, that worked. Is there a way to get it to take just the username?
0
 
BiziteksAuthor Commented:
Thanks! That worked perfectly.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.