Consequently, many developers have switched to using Secure File Transfer Protocol (SFTP) or File Transfer Protocol over SSL (FTP/S). However, using FTP can leave your data and passwords vulnerable during the transfer, as FTP doesn’t encrypt passwords. I think something else may be going on.ĪLL OTHERS: Please open your own threads detailing your own situation.For nearly three decades, developers have been using File Transfer Protocol, or FTP, to transfer files. Nightfall_gr: Please open another thread if this is happening to you. Have to remember that security often includes human enforcement / responsibility to the technical solution.ĭesireuben: Look into passive FTP, or try a different web browser. but they are then under orders to use the company VPN, and deviants risk losing their laptops. Now, when the users dialup, that is a different story, or when their laptop goes to the motel. That is why we run firewalls upstream, and disable them on the workstation. XP SP2 with firewall on will even prevent domain administrators from doing certain things to a workstation.
But that keeps the software off of each local machine, consuming memory, and CPU time. In all of these cases, however, some skill is required (aside from the store-solution) to configure and manage. I would suggest a wireless router box if you want a "store solution", or if you have a business, you will need something stronger such as a PIX unit. Not everyone desires that solution, however. I run a linux server between my desktops and the internet, and that linux box is the firewall. I can show you logs of continual access attemps on my systems. The internet is an evil place: worms and attacks are all over the place. Passive FTP manages the ports differently, making the transaction firewall happy.īrotherPayne: I like running a firewall "upstream" from the client computers I use, so that if the firewall is compromised, I have yet another layer of security between the internet and me. Typically FTP wants to pick a random port to fire the data back on, and a firewall can block that.
I am seeing more passive ftp approaches, especially with the rise of firewalls. Geucimer: You may be onto something here. This thread has unfortunately become clouded with different types of problems attached to the same thread, perhaps caused by the same problem: XP SP2. I would first be checking to see if resolves to 123.123.123.2 (replace with what the real IP numbers should be) and be sure that you have access to the ports. Addresses not looking up, that sort of thing. Not sure if XP SP2's neato firewall will do that to you.ī) Perhaps your company's firewall is preventing the connectionĬ) There might be a problem with your IP scheme, or the addresses not correct.ĭ) There might be a DNS problem. Need a little more information to help you.ġ) Are you running any firewall software on the Windows XP computer itself?Ģ) Are you trying to connect to any of the servers outside of a firewall, or are you at work, trying to connect to an internal server?ģ) Are you able to ping the addresses you are trying to connect to?Ĥ) Are you able to browse out on the internet using IE or Firefox to connect to these places.Ī) It is possible that a firewall is preventing outside connectivity attempts.