Terminal Service on 2KServer Odd connection problem.

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

tnkrtrn - 28 Apr 2004 06:51 GMT

I've got an odd sort of problem. I can connect to the server using
RDC on an XP pro machine with no problem ... as long as I'm on the
LAN. As soon as I try to connect from outside the lan I can't
connect. The first thing I checked was to make sure 3389/tcp was
being properly forwarded. It was. After that I thought there might
be a security policy that didn't allow me to connect if I didn't
connect from the LAN. No such luck there. Then I thought maybe it
was because I hadn't purchased the licenses yet. But I also thought I
had temp licenses for 90 days and I have unlimited connections from
the LAN. So I didn't think that was the problem. I pretty much want
to test this out and if it works well we'll purchase the license well
before the 90 days so I'm not worried about a time limit. If this
doesn't work out we'll end up using this server for something else and
scrapping the whole term service idea. Anyway I digress. I'm stumped
about why I have seemingly unlimited connections from my LAN but none
when I leave it. This is the error message I get in the event viewer.

Event ID:1004
Source:TermService
The terminal server cannot issue a client license.

Reply to this Message

Vera Noest [MVP] - 28 Apr 2004 14:39 GMT

There might be a black hole router between your client and the TS,
which blocks packets above a certain size. This prevents the transfer
of the permanent TS CAL to the client (on first connection, the
client gets a temporary license, on second connection, it gets a
permanent license).

If this is the problem, you have to change the MTU size. Check the
Terminal Services FAQ, there are 2 items about this under
"Connectivity"

http://www.microsoft.com/windowsserver2003/community/centers/terminal
/terminal_faq.asp

--
Vera Noest
MCSE,CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
*----------- Please reply in newsgroup -------------*

> I've got an odd sort of problem. I can connect to the server
> using RDC on an XP pro machine with no problem ... as long as
[quoted text clipped - 18 lines]
> Source:TermService
> The terminal server cannot issue a client license.

Reply to this Message

tnkrtrn - 28 Apr 2004 19:45 GMT

Thanks for you help Vera. After I posted yesterday I decided to
switch to Administrative mode to see if that would work. Surprising
enough it does. Of course it only allows two connections but that was
enough for my boss to see how benificial this would be. So back to my
original question which is any clue why I can't connect in App mode.
And actually I have another question. This one might be for a
licensing expert. I have a Windows 2000 server license and all the
clients will be connecting using XP. Do we need to buy a term license
for each user thats connecting or for each pc thats connecting.
Because of different locations we have more pc's than users. Also
I've heard that if you have xp you don't need a license for that
connection. Is that true?

> There might be a black hole router between your client and the TS,
> which blocks packets above a certain size. This prevents the transfer
[quoted text clipped - 37 lines]
> > Source:TermService
> > The terminal server cannot issue a client license.

Reply to this Message

Vera Noest [MVP] - 28 Apr 2004 21:44 GMT

By switching to Remote Administration mode, you circumvented the
problem, because no license needed to be downloaded to the client.
I still think that you have a black hole router on your network,
and the problem will appear again when you switch back to
Application Server mode.

About the license requirements:
Licensing for a W2K TS is always "Per Device", not "Per User". Per
user TSCALs were introduced in Windows 2003.
If all clients run XP Pro or W2K Pro, then you do not have to buy
additional TS CALs. Those clients receive a free TS CAL from the
TS Licensing Server. But you *must* install and activate a TS
Licensing Server (on your domain controller if your TS is a member
of a W2K domain).

I recommend reading the Windows 2000 Terminal Services Licensing
FAQ
http://www.microsoft.com/windows2000/server/howtobuy/pricing/tsfaq
.asp

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---

> Thanks for you help Vera. After I posted yesterday I decided to
> switch to Administrative mode to see if that would work.
[quoted text clipped - 19 lines]
>> the Terminal Services FAQ, there are 2 items about this under
>> "Connectivity"

http://www.microsoft.com/windowsserver2003/community/centers/ter

>> minal /terminal_faq.asp
>>
[quoted text clipped - 27 lines]
>> > Source:TermService
>> > The terminal server cannot issue a client license.

Reply to this Message