From: "Antti Kurenniemi" 

"John Beckett"  wrote in message
news:p2ms63l495uihmfr1a3o199kd8p3c0ffq9{at}4ax.com...
> "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).

Yay, did that. I used the same account with which I could use the
command-line ftp, but the service still did not work.


> 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.

Done that, manual ok.


> 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.

Not the case, can see other computers in the network when logged in as that
account. I'm leaning towards the service app actually doing something funny
- which is no biggie as I told the programmer to get his ass in here asap
and fix the damn thing. He's flying in tomorrow, which is strange
'cause I'm not used to having any sort of authority over anyone or anything
.


> 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.

This is just a development setup, the real installation will have the ftp
server in a whole 'nuther location.


Antti Kurenniemi

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