I wouldn't so much worry about tying up the bandwidth with multiple
software clients. At least, no more than a hardware client would. In
other words, 2 software clients talking using separate clients will
generate the same amount of traffic as two clients talking through a
hardware client.
.
From: Aaron T. Rohyans [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 17, 2008 1:30 PM
To: NT System Admin Issues
Subject: RE: VPN Client's vs. Hardware
I wouldn't so much worry about tying up the bandwidth with multiple
software clients. At least, no more than a hardware
Go on :-). What do you have on the back-end to support this? What are
your users RDP-ing in to?
Malcolm
From: Stephan Barr [mailto:[EMAIL PROTECTED] On Behalf Of
lists
Sent: Tuesday, 17 June, 2008 13:57
To: NT System Admin Issues
Subject: RE: VPN Client's vs. Hardware
I've moved from VPN
reduces desktop support issues, as you
can imagine.
Cheers.
From: Malcolm Reitz [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 17, 2008 2:05 PM
To: NT System Admin Issues
Subject: RE: VPN Client's vs. Hardware
Go on :-). What do you have on the back-end
Issues
Subject: RE: VPN Client's vs. Hardware
Terminal Services on 2000/2003 depending on the client. I'm a small consulting
company in the Midwest and all of my clients use TS in one way or another.
Client licenses are often free/embedded depending on OS. TS/RDP is sensitive to
packet loss
.
Cheers.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 17, 2008 2:24 PM
To: NT System Admin Issues
Subject: RE: VPN Client's vs. Hardware
Is easily controlled via GPO.
Can you elaborate on this? What are you controlling via
