Serach this forum for ftp and you will have several findings
- - - - - - - - - - - - - - - - - - Im three apples high, Im blue, and i most certainly like that cold beer that should be every mans right after a hard days work!
If you're using sql server you can also make it do ftp for you. At work I do not have ftp rights, but I can get around that by using sql server for this. Just a suggestion...
Now that you mention it, yes it does. I asked for FTP rights, but our network admin told me to do it that way. I assumed that it was safe to do, but I don't really know why I thought this. I guess I should bring that up...
I've never been a fan of allowing internal system external access. Ever since a certain former coworker decided to check his email from the web server. And just for note, if you receive an email with a title that has been featured on the cover of most major news papers, in the nightly news, on CNN, and in the security bulletons, don't open it.
Well guys I tried the wininet.dll but had problems so I just used the FTP utility in XP
Just created a script file that lists the files I want to upload that I select from a file list and call it from a batch file.
May sound primitive but it works great and also if you shell the batch file maximised with focus you can see the batch file connecting and copying each file. So you can see it working.
How is utilizing a production server for ftp purposes dangerous? I've not heard that before, at least with respect to the ftp process I set up. If there are some security concerns I'm not aware of I'd certainly like to find out.
I have set up a process similar to what jshurst mentioned in his thread where SQL Server is used. I have a stored procedure that executes an ftp 'put' under the SQL Server Service account context. The procedure basically dumps data to a file, creates an ftp command file (which uses that data file in its put command), and executes an ftp command with the command file in it to kick off the ftp process. The following link demonstrates something similar to what I've done (
Running FTP from a SQL Server is not explicitly risky. But it infers a few things.
1) your database is capable of communicating to targets out side of your domain.
2) FTP ports are open on your firewall.
3) FTP is an unsecured, unencrypted connection.
Number 1 is probrably the largest reason for concern. I tend to prefer that the database servers are on non-routable IPs and are blocked by the proxy. That ensures that no one from out side of the network can get to them. The risk of losing that much data, and the time required to rebuild it, makes it in our best interest to keep it as secure as possible.
Thanks for the info Rick. I'm not much of a network guy (I probably know enough to mess something up) so I'll take up these points with our Network Admin to see if he has considered them.
There's a nice little ftp class that SqueakinSweep posted in thread796-1074156. I'm currently using it in a program that will read in custom batch ftp settings, connect and upload automaticly. Its pretty easy to modify and its free.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.