How to debug licensing server communication error?

  • Thread starter Thread starter Sascha Ziemann
  • Start date Start date
S

Sascha Ziemann

Guest
Hi,

I have an Windows domain with terminal servers and two license
servers. Everything works fine there.

Now I want to install a standalone system for testing purposes, which
is not part of the domain. My problem is, that the new server can not
connect to any licensing server, although the network connection works
pretty fine. I can ping the terminal licensing server from the new
standalone terminal server.

How can I debug the error? The graphical tool gives me only a pretty
useless error message: "cannot connect".

cu Sascha
 
Re: How to debug licensing server communication error?

This is by design. For a solution, check here:

Can I use a single TS Licensing Server to issue TS CALs to Terminal
Servers in multiple untrusted domains and workgroups?
http://ts.veranoest.net/ts_faq_licensing.htm#LS_untrusted_domains

If the standalone server is only for testing purposes, it might be
easier to install the TS Licensing Service also on the standalone
TS, point the TS to itself as the LS and install a couple of TS
CALs on it. Or (if you are going to test only during a limited time
period), use the grace period.

813052 - Maximizing the Windows Server 2003 Terminal Services
Evaluation Period
http://support.microsoft.com/?kbid=813052

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

Sascha Ziemann <ceving@googlemail.com> wrote on 01 feb 2008 in
microsoft.public.windows.terminal_services:

> Hi,
>
> I have an Windows domain with terminal servers and two license
> servers. Everything works fine there.
>
> Now I want to install a standalone system for testing purposes,
> which is not part of the domain. My problem is, that the new
> server can not connect to any licensing server, although the
> network connection works pretty fine. I can ping the terminal
> licensing server from the new standalone terminal server.
>
> How can I debug the error? The graphical tool gives me only a
> pretty useless error message: "cannot connect".
>
> cu Sascha
 
Back
Top