 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
Windows Server Forum / Windows NT / Terminal Server / October 2003windows 2003 terminal server
I installed a Windows 2003 server with terminal server. The server was able to issue 3 temporary licenses, but now I am trying to get it to issue permanent licenses. I have installed licenses and by repeatly testing have many more licenses than we will ever use. Remote desktop does work. What do I need to do to get it to issue licenses? Thanks Roger You have installed and activated a TS Licensing Server, I presume? And installed the TS CALs on the LS? Did you install "Per User" or "per Device" TS CALs? Do these installed TS CALs show up in the LS (as unused licenses)? Verify that the TS can locate the LS. Check the EventLog, problems with licensing are documented there. If your LS is in a different domain than the TS, you might have to hardcode the address of the LS into the registry of the TS: 279561 - How to Override the License Server Discovery Process in Windows Server 2003 Terminal Services http://support.microsoft.com/?kbid=279561 -- Vera Noest MCSE, CCEA, Microsoft MVP - Terminal Server http://hem.fyristorg.com/vera/IT --- please respond in newsgroup --- > I installed a Windows 2003 server with terminal server. The > server was able to issue 3 temporary licenses, but now I am [quoted text clipped - 7 lines] > > Roger > You have installed and activated a TS Licensing Server, I presume? Yes - I can use remote desktop and that works. If I were to disable that, wouldn't terminal server provide the connection if there? I thought they were both seperate. > And installed the TS CALs on the LS? I have installed both per user and device cals > Did you install "Per User" or "per Device" TS CALs? I tried both in an attempt to get it to work. > Do these installed TS CALs show up in the LS (as unused licenses)? yes - I was just watching a Microsoft presentation on TS and they said that in user mode, it would not show the used. > Verify that the TS can locate the LS. > Check the EventLog, problems with licensing are documented there. The Terminal Server Licensing server CPCSVR1 has no permanent licenses for product 'Windows Server 2003 - Terminal Server Per Device CAL Token'. Use Terminal Server Licensing administrative tool to register more licenses. I have changed to per user after this errors but I do have both types of installed now. I did have user licenses installed at that time. I do not get these errors anymore since I changed to user, but I still get the connect error where the client could not establish a conneciton to the remote computer. > If your LS is in a different domain than the TS, you might have to > hardcode the address of the LS into the registry of the TS: > > 279561 - How to Override the License Server Discovery Process in > Windows Server 2003 Terminal Services > http://support.microsoft.com/?kbid=279561 I followed these instructions prior to sending this message. > -- > Vera Noest [quoted text clipped - 13 lines] > > > > Roger OK, so now you have fixed the licensing problem and don't get any Events about licensing anymore, correct? But clients still can't connect? Then we have a different connection problem altogether now. Are *all* clients having problems connecting? No Events at all when they try to connect? Can they ping the server? Can they telnet to port 3389? -- Vera Noest MCSE, CCEA, Microsoft MVP - Terminal Server http://hem.fyristorg.com/vera/IT --- please respond in newsgroup --- >> You have installed and activated a TS Licensing Server, I >> presume? [quoted text clipped - 56 lines] >> > >> > Roger I have not seen any more errors with licensing. I have tested two clients at this time. I am able to ping the server. I cannot telnet to port 3389. Thanks Roger > OK, so now you have fixed the licensing problem and don't get any > Events about licensing anymore, correct? [quoted text clipped - 72 lines] > >> > > >> > Roger If you can't telnet to port 3389, then the TS is not listening on port 3389 or you have a name resolution problem. See KB below. 187628 - Using Telnet to Test Port 3389 Functionality http://support.microsoft.com/?kbid=187628 Have you checked the status of the rdp listener in TS Manager? -- Vera Noest MCSE, CCEA, Microsoft MVP - Terminal Server http://hem.fyristorg.com/vera/IT --- please respond in newsgroup --- > I have not seen any more errors with licensing. I have tested > two clients at this time. I am able to ping the server. I [quoted text clipped - 83 lines] >> >> > >> >> > Roger I read the information on the telnet test and it works. I expected to see more. rdp listener is working. I think my terminal server is working. The main problem was with the licensing and that is now corrected. The other problem I had was with security and that has been corrected. I have been able to connect 6 sessions with no problem. The configuration here is per user and I do not see any usage in the license manager, but I do see the connections in the terminal manager. There was a larger difference between the w2k version and this. I did set up a test on another server and that was configured per device, and I only saw one license used out of two devices. I thought I would have seen two licenses used. W2k autodefined the printers, I noticed that win 2003 did not seem to. Is this normal? Thank you for your help Roger > If you can't telnet to port 3389, then the TS is not listening on > port 3389 or you have a name resolution problem. See KB below. [quoted text clipped - 97 lines] > >> >> > > >> >> > Roger No, Windows 2003 should also autocreate local printers. Have you checked the sessions for autocreated printers on the server and the client? The problem could also be that Windows 2003 doesn't have native drivers for the printers that you are using. If that's the case, you'll have to map them to a native driver. 239088 - Windows 2000 Terminal Services Server Logs Events 1111, 1105, and 1106 http://support.microsoft.com/?kbid=239088 -- Vera Noest MCSE, CCEA, Microsoft MVP - Terminal Server http://hem.fyristorg.com/vera/IT --- please respond in newsgroup --- < rest of post removed, since original problem is solved > > W2k autodefined the printers, I noticed that win 2003 did not > seem to. Is this normal? > > Thank you for your help > > Roger > No, Windows 2003 should also autocreate local printers. Have you > checked the sessions for autocreated printers on the server and Oops! should be: "Have you checked the SETTINGS".... -- Vera Noest MCSE, CCEA, Microsoft MVP - Terminal Server http://hem.fyristorg.com/vera/IT --- please respond in newsgroup --- The printers are working also. I had a problem with one printer driver on the remote pc, and after deleting that one, the printers would autocreate. Everything is working. Thank you for your help Roger > > No, Windows 2003 should also autocreate local printers. Have you > > checked the sessions for autocreated printers on the server and [quoted text clipped - 6 lines] > http://hem.fyristorg.com/vera/IT > --- please respond in newsgroup --- |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2009 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.