Can Terminal Service, but Can't Terminal Service out

Can Terminal Service, but Can't Terminal Service out

Post by Zaj » Thu, 16 May 2002 00:33:40



Computers within a domain can terminal service Win 2k
servers within the domain, but they can not use Terminal
Services to any Terminal Servers outside of the
organization using Public addresses.
Any help is appreciated we were working with Terminal
services for a long time and now we can't. Does this sound
like a Security Setting I am not realizing.
Thanks,
Eric
 
 
 

Can Terminal Service, but Can't Terminal Service out

Post by Tim Hines, MCS » Thu, 16 May 2002 09:05:17


Are there any firewalls in the picture?  If so you will need to open port
3389 for RDP.  Can you ping the server by name?  Can you telnet to port 3389
by typing telnet ip address 3389.  We need to verify connectivity first.
What error do the clients receive when they try to connect.

--
Tim Hines, MCSA, MCSE (2000 & NT4)


Quote:> Computers within a domain can terminal service Win 2k
> servers within the domain, but they can not use Terminal
> Services to any Terminal Servers outside of the
> organization using Public addresses.
> Any help is appreciated we were working with Terminal
> services for a long time and now we can't. Does this sound
> like a Security Setting I am not realizing.
> Thanks,
> Eric


 
 
 

1. Terminal Services Licensing and Activation, Terminal Services Licensing and Ac

Hi,

I have a client that has already purchased 10 Windows 2000
Terminal Services CALS through Open License Program (OLP
NL).

He installed and activated the 10 licenses in its
corporate lan.

Now he wants to built 10 more small networks with:
1x Windows 2000 Server
3x Windows 2000 CALS
3x Windows 2000 Terminal Services CALS
3x Thin Clients as Terminals

Every network will be autonomous with no connection to
the corporate lan, its own Terminal Services License
Server and own small Active Directory.

My question: Which is the right way for purchasing the
additional Terminal Services Licenses?

1. A single order for 30 additional TS CALS (OLP NL)
2. Multiple orders for 10x3 additional TS CALS (OLP NL)

Thanks in advance,

Christos

----------------

When using Thin Clients you have to buy TS CALS.

The setup for every-one of the small networks
will be the following:


3x Windows 2000 CALS OLP NL
3x Windows 2000 Terminal Services CALS OLP NL
3x Windows Based Terminals (Thin Clients) as Desktop
Devices

Servers will have installed their own Active Directory,
TS License Server.

Every TS License server must have activated 3 tokens,
each for every seat. A total of 3 License Tokens for
every of the 10 networks = 30 TS Licences/TS License
tokens.

My question: Which is the right way for purchasing the
30 additional Terminal Services Licenses and Activate
the tokens?

1. With a single order for 30 additional TS CALS (OLP NL)?
2. With multiple orders for 10x3 additional TS CALS (OLP
NL)?

2. Explorer.exe crashes upon starting ...

3. Terminal Services License Server on same box as Terminal Services?

4. 3rd European MPI Workshop (corrected)

5. Technet Chat: What’s new in Terminal Services and Terminal Services Deployment - 1/23/03

6. MAPI Error on client - SOS

7. Terminal Services Error (Terminal services client disconnected)

8. Apple Java/C/C++ Programmer Wanted

9. Terminal Services Licensing and Activation:::::Terminal Services Licensing and A

10. what's the easiest way to move the Terminal Services (TS) License Service (TSLS)...

11. The Terminal Services Licensing service terminated with service-specific error 3221291009.

12. Can't Stop Terminal Services Service

13. Terminal Service Licensing Service don't work