- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- BackOffice Products
- >
- Terminal Service licensing server
BackOffice Products
1753821
Members
8494
Online
108805
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-02-2004 01:51 AM
тАО07-02-2004 01:51 AM
Terminal Service licensing server
I cannot get our Terminal Server 2000 licensing server service to start up in an Active Directory environment. The error says it cannot find a domain controller. And event viewer gives the classis error 29. All of the servers are an ADC including the terminal server. We are using it as an application server for remote users. New users cannot connect because they cannot get a license. How do I fix this?
- Tags:
- License
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-04-2004 11:05 PM
тАО07-04-2004 11:05 PM
Re: Terminal Service licensing server
Hi Cynthia,
Is your licensing server on a domain controller ?? if not then you should add the service to a domain controller. That should solve the problem.
regards
john
Is your licensing server on a domain controller ?? if not then you should add the service to a domain controller. That should solve the problem.
regards
john
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-05-2004 07:42 AM
тАО07-05-2004 07:42 AM
Re: Terminal Service licensing server
It is.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-05-2004 07:09 PM
тАО07-05-2004 07:09 PM
Re: Terminal Service licensing server
This doc describes the discovery process:
Description of Terminal Services License Server discovery
http://support.microsoft.com/default.aspx?kbid=232520
A point to note is: "Add or edit the DefaultLicenseServer registry value (REG_SZ) in the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TermService\Parameters key with the NetBIOS name of the designated License Server. If it is located on a remote subnet, confirm that the Terminal Services-based computer can resolve the NetBIOS name of the specified server using Windows Internet Naming Services (WINS) or Lmhosts name resolution."
This doc may give us more information about where the problem is:
How to enable debug logging for Terminal Services Licensing
http://support.microsoft.com/default.aspx?scid=kb;en-us;305089
Event ID 52 When You Start Terminal Services
http://support.microsoft.com/default.aspx?scid=kb;en-us;258021
Use ipconfig (/all and /flushdns before) NSLOOKUP to check DNS config/name resolution.
Cheers,
Rune
P.S. I am assuming Win2K SP4 (fixes to terminal services licensing in a post-SP3 hotfix for example)
Description of Terminal Services License Server discovery
http://support.microsoft.com/default.aspx?kbid=232520
A point to note is: "Add or edit the DefaultLicenseServer registry value (REG_SZ) in the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TermService\Parameters key with the NetBIOS name of the designated License Server. If it is located on a remote subnet, confirm that the Terminal Services-based computer can resolve the NetBIOS name of the specified server using Windows Internet Naming Services (WINS) or Lmhosts name resolution."
This doc may give us more information about where the problem is:
How to enable debug logging for Terminal Services Licensing
http://support.microsoft.com/default.aspx?scid=kb;en-us;305089
Event ID 52 When You Start Terminal Services
http://support.microsoft.com/default.aspx?scid=kb;en-us;258021
Use ipconfig (/all and /flushdns before) NSLOOKUP to check DNS config/name resolution.
Cheers,
Rune
P.S. I am assuming Win2K SP4 (fixes to terminal services licensing in a post-SP3 hotfix for example)
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP