Why "mput" and not just the "put" command?
I have a similar problem with one of my users, and his issue is hit
convoluted and screwed up security system on his network. (Crazy home-made
firewall, VPN to get behind it..)
Pick up a machine, connect with a different network and it works fine.
So... try removing your security devices as a variable.
Also, make sure you are in passive mode, not active mode.
Does it work when you type it out?
Try turning off the local firewall (the crappy one on the machine built into
Windows)
[quoted text, click to view] "K" <nospam@nospam.com> wrote in message
news:e%23Fz1V1YIHA.5900@TK2MSFTNGP02.phx.gbl...
> This may not be one for here, so if not please direct me to the relevant
> place.
>
> I have a 2003 server running FTP server (IIS).
>
> I have a very simple DOS script which runs as a scheduled task on remote
> machines to send a single 55k file back to the FTP server at each logon.
>
> I am having problems however. I have copied my script below to show what
> is happening.
>
> prompt
> open <server ip address>
> <domain\username>
> <password>
> mput *.adt y
> close
> bye
>
> The script works fine but when it gets to the mput *.adt y command, it
> creates the file on the server as a 0-byte file and then sits for a while
> before timeing out.
>
> What could be causing this? It obviously makes the connection because it
> can create the 0-byte file, but seems to fall over thereafter.
>
> Any help would be much appreciated.
>
> Regards
>
> Keith
>