W2K3 TS Licensing behind a NAT router

[Guest]

Dear All

W2K3 Terminal Server can't connect to W2K3 Terminal Server License Server: no licenses are issued. Both servers are situated behind a NAT-router (screened subnet). Terminal Server License Server is activated and 5 W2K3 TS DEV CALs are applied
The domaincontrollers are W2K and after applying KB 279561 (both NETBIOS name and IP-address have been tried) the W2K3 Terminal Server License Server doesn't issue licenses. A Domain License Server has been configured (No Enterprise)
The W2K3 Terminal Server License Server and W2K3 Terminal Server keep looking on the domaincontrollers as indicated in the search despite KB 279561.
When search is cancelled and a connection is manually established the W2K3 Terminal Server License Server shows the right status, the W2K3 Terminal Server shows a status of unknown.

Any suggestions

Thanks in advance

Boy Oudejan
The Netherland

 

[Guest]

Save this code to a VBS file and execute it via "cscript FileName.vbs" or via Windows "double-click". This will tell you if the TSLS server name that is configured in the Windows Registry. If it comes up null or incorrect then you know your registry entry is incorrect

'**************************************************************************
'
' WMI VBScript that queries the License servers configured for registry bypass

' on the Terminal serve

'**************************************************************************
for each Terminal in GetObject("winmgmts:{impersonationLevel=impersonate}").InstancesOf ("win32_TerminalServiceSetting"
WScript.Echo "The License Servers are = " & Terminal.DirectConnectLicenseServers
nex
'**************End of Script*********************************

Patrick Rous
Microsoft MVP - Terminal Serve
http://www.workthin.com

 

[Guest]

I initially had the same problem

Patrick Rous
Microsoft MVP - Terminal Serve
http://www.workthin.co


----- Boy wrote: ----

Tnx for the script: we found out the KB was not implemented right. We added a value instead of a key. This because we first found the article for W2K (KB239107).

Best regards and thanks again! Bo