mulitple (concurrent) RDP connections?

Is there anything I can do to enable more than one RDP connection concurrently on the same box? Here's my situation..

The client is a SMB with 3-4 outside sales people & execs who will need remote access to their respective machines here in the office, particularly to access a couple of dB's. VPN is waaaaaaay too slow and not adequate for dB access even over a 2Mbps+ pipe. Trying to keep some of the dB's synced between laptops and home office server is not working. The app is ACT... don't EVEN get me started. I HATE this app, but I'm stuck with it, management won't budge for at least another year. They also use Quickbooks Enterprise (gag again). I'm pitching ERP solutions but budget won't allow until next FY

Current network has 3 WS2k3 AD DC's; one is basically an inherited box which serves only to share one printer and house shares for a single security group on the domain. The newest is an AD DC with FSMO/FS/TS/DNS/DHCP serving the vast majority of files, dB's, and user shares. Third is an AD DC acting only as RRAS/VPN server and AV server, no file shares. Servers run in native WS2k3 environment. All clients are XP Pro SP1

I have my router passing 3389 to aserver now for remote admin. What I would like to do is pass all 3389 traffic through my router to a specific client (called "Remote" for the purpose of this discussion) on the private network, from which exec's and outside sales reps could RDP their respective machines, and I could continue to admin servers from there with RDP. In other words, outside machines hit my router's public/internet IP with a 3389 request from their machine at home or hotel, which is then forwarded to "Remote". They log onto "Remote" and then RDP their own machine inside the office from there. Is there a way to reghack or otherwise configure "Remote" to accept multiple RDP connections concurrently? I had heard it rumored that there is such a method, but I certainly can't figure it out on my own

If this is just too much gymnastics to accomplish the goal, I am very open to any and all suggestions for alternate methods

Thanks for any input you can spare

Sammy

The remote admin feature is limited to two connections (and is intended
for what it is called - remote administration of the server). To get more
than two connections you need to use Terminal Services.

"RDP_novice" <(E-Mail Removed)> wrote in message
news:03EFD8F8-53F5-4CF6-8B85-(E-Mail Removed)...
> Is there anything I can do to enable more than one RDP connection
concurrently on the same box? Here's my situation...
>
> The client is a SMB with 3-4 outside sales people & execs who will need
remote access to their respective machines here in the office, particularly
to access a couple of dB's. VPN is waaaaaaay too slow and not adequate for
dB access even over a 2Mbps+ pipe. Trying to keep some of the dB's synced
between laptops and home office server is not working. The app is ACT...
don't EVEN get me started. I HATE this app, but I'm stuck with it,
management won't budge for at least another year. They also use Quickbooks
Enterprise (gag again). I'm pitching ERP solutions but budget won't allow
until next FY.
>
> Current network has 3 WS2k3 AD DC's; one is basically an inherited box
which serves only to share one printer and house shares for a single
security group on the domain. The newest is an AD DC with
FSMO/FS/TS/DNS/DHCP serving the vast majority of files, dB's, and user
shares. Third is an AD DC acting only as RRAS/VPN server and AV server, no
file shares. Servers run in native WS2k3 environment. All clients are XP Pro
SP1.
>
> I have my router passing 3389 to aserver now for remote admin. What I
would like to do is pass all 3389 traffic through my router to a specific
client (called "Remote" for the purpose of this discussion) on the private
network, from which exec's and outside sales reps could RDP their respective
machines, and I could continue to admin servers from there with RDP. In
other words, outside machines hit my router's public/internet IP with a 3389
request from their machine at home or hotel, which is then forwarded to
"Remote". They log onto "Remote" and then RDP their own machine inside the
office from there. Is there a way to reghack or otherwise configure "Remote"
to accept multiple RDP connections concurrently? I had heard it rumored that
there is such a method, but I certainly can't figure it out on my own.
>
> If this is just too much gymnastics to accomplish the goal, I am very open
to any and all suggestions for alternate methods.
>
> Thanks for any input you can spare.
>
> Sammy

Thanks. Any good KB's or other references explaining domain user remote logons thru TS? I have Terminal Server setup on one of the DC's, and TS licenssing on another DC, but have never used the "Thin Client" scenario for users to logon and access apps. TS uses RDP 5.2, correct

Any good reosurces to get me up to speed (quickly) would be appreciated

Thanks again

Sammy