Re: Can't connect via VNC from work to home

From: Charles Newman (charlesnewman1_at_comcast.net.spammers.will.be.shot.on.sight)
Date: 02/15/05 

Date: Tue, 15 Feb 2005 00:55:13 -0800

"Somebody" <somebody@nospam.russdoucet.com> wrote in message
news:elbQd.91250$vO1.570441@nnrp1.uunet.ca...
>
> "Leythos" <void@nowhere.lan> wrote in message
> news:pan.2005.02.14.21.44.31.551111@nowhere.lan...
>> On Tue, 15 Feb 2005 06:21:48 +1100, Grosby wrote:
>> Anytime you expose your company to something they didn't authorize you
>> risk their network. Many companies don't block/filter web sites because
>> it's an expense to do so, others rely on the good nature of the employees
>> to not do anything they aren't suppose to do.
>>
>> There are few instances where a person connects from work to home for
>> Business reasons, fewer still that don't want to access a file at home
>> from work sometime.
>
> I'm interested to know what risks are incurred by remote controlling a
> machine at home, from within the corporate LAN. That's what the OP was
> trying to do.

   I would suppose it would depend on what you are doing. If you are
using Remote Desktop, your work PC wold be no more than a
"dumb terminal" to your home PC, with no file transfer capability of
any kind between the two machines, so there would be no real
risk to the network as far as security goes. And do remember that
inbound connections are blocked on the lowest tiers of DSL and
cable service. If you want to connect inbound, you will need to
upgrade to one of the more expensive tiers on most cable and
DSL services.

>
> -Russ.
>
>