Remote Connections - Working from home???

Hello everyone,

I have just set up a Terminal Server that is working
perfectly for clients connecting from a remote location.
The remote office client systems are connected via one
side (ie, router #2) of a matched pair of VPN/Firewall
Routers. The Domain Controller and Main office clients are
on the other side (ie, router #1). Both offices' clients
are members of the same domain.

My question is, how do I set up terminal access for remote
(home) users? The VPN is allowing authenticated users into
the LAN, but when the clients try to use mstsc.exe for a
thinclient session to the terminal server, they are not
authenticated and subsequently booted. What am I missing?

The obvious difference to me is that the branch office users are domain
members, but the dialup clients will not be. You could try getting a user to
use the "login using a dialup connection" option to see if that solves the
problem.

It is probably easier to see what credentials the user sends to TS. Is
there a "Run as" option they can use to send the correct credentials?

"Mark Steingart" <(E-Mail Removed)> wrote in message
news:093601c3ba9e$1043be20$(E-Mail Removed)...
> Hello everyone,
>
> I have just set up a Terminal Server that is working
> perfectly for clients connecting from a remote location.
> The remote office client systems are connected via one
> side (ie, router #2) of a matched pair of VPN/Firewall
> Routers. The Domain Controller and Main office clients are
> on the other side (ie, router #1). Both offices' clients
> are members of the same domain.
>
> My question is, how do I set up terminal access for remote
> (home) users? The VPN is allowing authenticated users into
> the LAN, but when the clients try to use mstsc.exe for a
> thinclient session to the terminal server, they are not
> authenticated and subsequently booted. What am I missing?

Bill,
Thanks for your input. I found the answer to the issue and
it had nothing to do with Terminal Server or MS win2k3...

It seems the firewall's rules for terminal server access
had to specifically specify the internal LAN IP for the
Terminal Server. Simple, Huh?

Mark Steingart


>-----Original Message-----
> The obvious difference to me is that the branch
office users are domain
>members, but the dialup clients will not be. You could
try getting a user to
>use the "login using a dialup connection" option to see
if that solves the
>problem.
>
> It is probably easier to see what credentials the
user sends to TS. Is
>there a "Run as" option they can use to send the correct
credentials?
>
>"Mark Steingart" <(E-Mail Removed)> wrote in
message
>news:093601c3ba9e$1043be20$(E-Mail Removed)...
>> Hello everyone,
>>
>> I have just set up a Terminal Server that is working
>> perfectly for clients connecting from a remote location.
>> The remote office client systems are connected via one
>> side (ie, router #2) of a matched pair of VPN/Firewall
>> Routers. The Domain Controller and Main office clients
are
>> on the other side (ie, router #1). Both offices' clients
>> are members of the same domain.
>>
>> My question is, how do I set up terminal access for
remote
>> (home) users? The VPN is allowing authenticated users
into
>> the LAN, but when the clients try to use mstsc.exe for a
>> thinclient session to the terminal server, they are not
>> authenticated and subsequently booted. What am I
missing?
>
>
>.
>