Are you sure you are accessing the same server inside as you are outside?
Can you confirm with event log entries that coincide with connection
attempts?
As far as I know, TS has no provisions to make distinctions based on IP. The
only thing I can think of is logon from workstation controls (limits on what
users can log on from what workstations), but that makes no real sense in
this case.
Venger
"Stempl" <(E-Mail Removed)> wrote in message
news:#(E-Mail Removed)...
> I have a interesting migration problem.
> We have two Windows 2000 server SP 3 with Terminal Services in
> Application mode, with 2 domains ( each server is the DC of the domain)
> in different structures, but one trusting the other manually without
> any problem (This is because we have to migrate the whole information
> from the older server, but AD has a corrupt database which we canīt
> repair, but is working (until now).
> The problem we are arguing about is the fact that i canīt access the
> new Terminal server from outside our router. When accessing from LAN,
> every user can login, but when trying to access from DSL connection, we
> get the message "You do not have access to logon to this session".
> The old server is the gateway for the whole network and is the only one
> which is connected to the router via NIC.
> Therefore we have two IP segments, one for the LAN, one for the router.
> The old server acts as IP-Router.
>
> What did we wrong that we canīt access the new terminal server ???
>
|