From: John Beckett 

"Antti Kurenniemi"  wrote in
message news::
> I'll check the accounts first thing tomorrow.

I guess you know that you should run services.msc, find the service,
Properties. On the Logon tab, configure a user and password. After OKing
out, stop the service, and start it again (so it logs on as the new user).

The user you configure could be local or domain - not important. It does
not have to be an admin. There are various special accounts you might use,
but I would use a new local user (with default properties). Except: In the
properties of the new user, set:
  Change password at next logon - No
  Password never expires - Yes

The user you configure has nothing to do with the FTP process (different
name and password). Test that the user can manually log on at the server
and manually FTP.

There are no policies or permissions that would stop the service doing FTP,
except for what Mike mentioned - the account may not be able to access the
network.

BTW if the two computers are not going to have a firewall between them,
there is no reason to use FTP. You can simply use file sharing to copy
files back and forth. Advantage: The authentication won't show the password
in plain text on the network.

John

--- BBBS/NT v4.01 Flag-5