And on top of that for support of noncentralized LANs (the normal consulting
role) you need to either repeat the solution for each location or allow
virtually any IP to attempt uploads to your central server.

Particularly damning from a security and use perspective is that the necessity
for file transfers is ad-hoc and erratic.  This means that most sites won't need
it, and when you do, you need it quickly.  Taking the time to set up every LAN
with FTP access when you support 50+ of them winds up being a significant time
investment and may necessitate several workarounds due to special configurations
(and even require new equipment if the client LANs have a limited number of
forwardable ports - such as using NetGear's ISDN/DSL routers).  After you have
that done, you are left with another potential avenue of attack for someone
attempting to crack the system.

Admittedly, those are all issues which can be overcome, *given sufficient time*
to work with them; but that's what most consultants don't have.

What it comes down to is that in cases where I find myself needing regular
access to customer's systems for file transfer, I usually wind up switching over
to pcAnywhere.  I don't like it, it isn't nearly as fast, but ultimately it
saves them money since I don't have to battle with a lot of other
reconfigurations and security issues.

When I get time, I will probably start looking at the instant messaging clients
concept to see if I can use that to do this; it certainly will save a lot of
grief...

----- Original Message -----
From: "Fredrik Malmquist" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, 2002-05-20 11:22
Subject: Re: File Transfer with WinVNC?


> > Another option is to set up a company FTP server - then you have a central
> > log of all traffic back and forth.  It does require setting up an FTP
> client
> > you're comfortable with on the VNC client.  Also, make sure not to allow
> > anonymous uploads or you'll be sure to be abused.  Also, firewall
> > considerations will apply to make sure the client can make an FTP
> connection
> > to the FTP server.  Given these, though, FTP is a good way to transfer
> > files.
>
> FTP really sucks with firewalls, it uses random ports in the high port-range
> that needs to be mapped and discovered, and those ports are random and
> varies with the server you are running, and most of the time it doesn't
> really say what numbers these ports are going to be.
>
> \Fredrik
> ---------------------------------------------------------------------
> To unsubscribe, mail [EMAIL PROTECTED] with the line:
> 'unsubscribe vnc-list' in the message BODY
> See also: http://www.uk.research.att.com/vnc/intouch.html
> ---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, mail [EMAIL PROTECTED] with the line:
'unsubscribe vnc-list' in the message BODY
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------

Reply via email to