Re: Terminal Server Complains No License Server, but License Server Says,"Yes, I gave out Licenses"
- From: "Vera Noest [MVP]" <vera.noest@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 04 Oct 2005 12:58:23 -0700
I would definitively hardcode the name of the LS into the registry
of the TS, because of this:
895151 - Windows Server 2003-based or Windows 2000-based terminal
servers do not automatically discover a license server that is
designated as an enterprise license server
http://support.microsoft.com/?kbid=895151
So you *only* get the warning in the System tray on the TS, but
there is *no* EventID 1009 on the TS?
Might be a "false alarm", similar to this one:
831716 - You receive a "No Terminal Services License server was
found on the network" error message when you run the Manage Your
Server Wizard on a Windows Server 2003-based computer
http://support.microsoft.com/?kbid=831716
Have you tested with a client which has never connected before? Try
connecting twice (on first connection, all clients receive a
temporary license, on second connection you get a permanent
license), and monitor the Licensing Manager on the LS.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___
"Dave Morschhauser" <someone@xxxxxxxxxxxxx> wrote on 04 okt 2005
in microsoft.public.windows.terminal_services:
> I am running Win2K3 on two machines at two different locations.
> The two locations are connected by an ISDN link and by a VPN
> over DSL and Cable Modem. Both connections are available, and
> appear to be working (ping, traceroute, the RDP connections
> themselves). One machine is running SP-1 the other has not been
> upgraded (yet).
>
> Each Win2K3 machine is running TS, and one of them is running
> TSLS. The second one has been operational for about 90 days.
> Within the last week, the second TS has been complaining that
> there is no TSLS, and that the grace period is going to expire.
> The "complaint" is in the form of a balloon in the SysTray.
> Checking with the TSLS Management Console, there are several
> Permanent Licenses that have been issued to clients that would
> have no reason to connect to the first machine, so it appears
> that the TSLS is correctly providing licenses for the second TS
>
> On the second TS, I have run TS Config, and have tried both
> Automatic Discovery, and a hardwired TSLS. In automatic
> discovery, the TSLS server name is reported under "In Enterprise
> role". If I hardwire a TSLS, and press Check Names, it reports
> back that "The specified LS are valid Win2K3 TSLS's" The
> complaints persist regardless of automatic/hardwired mode.
>
> From the second TS, I have run lsview.exe, and it reports the
> TSLS as type "Enterprise", with the time off by a few minutes.
>
> From the second TS, I have run lsreport.exe, and it reports the
> same permanent and temporary licenses as are listed in the TSLS
> Management Console on the TSLS itself.
>
> The Event Log does not have any TSLS error messages, and the
> only TS error or warning messages are related to printers.
>
> Any ideas on what's wrong, and is TS about to stop working?
>
> Dave Morschhauser
> Mystic Valley Communications.
.
- References:
- Terminal Server Complains No License Server, but License Server Says,"Yes, I gave out Licenses"
- From: Dave Morschhauser
- Terminal Server Complains No License Server, but License Server Says,"Yes, I gave out Licenses"
- Prev by Date: Re: How to deny logon for already logged on user
- Next by Date: Re: CAL upgrade
- Previous by thread: Terminal Server Complains No License Server, but License Server Says,"Yes, I gave out Licenses"
- Next by thread: Re: Terminal Server Complains No License Server, but License Server Says,"Yes, I gave out Licenses"
- Index(es):
Relevant Pages
|
