PFFFFT, I'm going to let some accountant bring her PC into my IP subnet. A
PC I have no control over. A PC on which I don't even know if there is AV,
let alone up-to-date AV.
Well, OK, the OP has SBS2003 Premium, so if he has gone to ISA2004 he can
explore quarantine VPN (not something I've had time to do yet).
Sure, limit the user ID, not only with 'logon to' only the specific RDP
session host but file privelages which only allow the QB database to be
accessed. But bring them in via RWW, and you might want to hack the RWW RDP
connection page to not allow 'connect my local drives', either Ray Fong or
Sean Daniel blogged the hack, shame, I don't think you can do it on a per
user basis.
The best method of giving anyone access to your SBS2003 network from outside
is a locked down seperate TS accessed _only_ through RWW.
"Leythos" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> In article <#(E-Mail Removed)>, (E-Mail Removed)ie
> says...
>>
>> Leaves RDP through RWW, to either an XP ws or a seperate TS.
>
> No, it leaves RDP through a VPN (even PPTP) connection, and since RDP
> uses 30kbps, that means there is plenty of capacity on a slow connection
> with the overhead of a VPN.
>
> The best method would be to have them VPN into the network, limit them
> to ONE COMPUTER, they login to the computer using RDP, do their work on
> it, then log out - no files left on their home computer to be filtched
> if compromised.
>
> --
> --
> (E-Mail Removed)
> remove 999 in order to email me