PC Review
Forums
Newsgroups
Windows 2000
Microsoft Windows 2000 Terminal Server Applications
TS License Server Issue
Forums
Newsgroups
Windows 2000
Microsoft Windows 2000 Terminal Server Applications
TS License Server Issue
![]() |
TS License Server Issue |
|
|
Thread Tools | Rate Thread |
|
|
#1 |
|
Guest
Posts: n/a
|
I have a a W2K Ts that is not seeing the license server.
The License server is W2K and in the same domain. The registry fix is there and I have also tried the ip address. Any ideas? |
|
|
|
#2 |
|
Guest
Posts: n/a
|
After you installed the registry entry, did you restart
the server? Is this license server installed on the domain controller? -M >-----Original Message----- >I have a a W2K Ts that is not seeing the license server. >The License server is W2K and in the same domain. The >registry fix is there and I have also tried the ip >address. Any ideas? >. > |
|
|
|
#3 |
|
Guest
Posts: n/a
|
The sevrer was restarted. The license server is on a
member server. This is happening on 2 of our Terminal servers. >-----Original Message----- >After you installed the registry entry, did you restart >the server? > >Is this license server installed on the domain controller? > >-M > >>-----Original Message----- >>I have a a W2K Ts that is not seeing the license server. >>The License server is W2K and in the same domain. The >>registry fix is there and I have also tried the ip >>address. Any ideas? >>. >> >. > |
|
|
|
#4 |
|
Guest
Posts: n/a
|
The last reply was mine as well. My W2K servers are
member servers in an NT 4.0 domain. The servers that I am having problems with are in different subnets. I see that if they are in different subnets from the licensing server, then it wouldn't be able to contact it. However, I am using the registry key so that should override the discovery. Could this be causing my issue due to the fact that it is not overriding the discovery? >-----Original Message----- >The sevrer was restarted. The license server is on a >member server. This is happening on 2 of our Terminal >servers. >>-----Original Message----- >>After you installed the registry entry, did you restart >>the server? >> >>Is this license server installed on the domain controller? >> >>-M >> >>>-----Original Message----- >>>I have a a W2K Ts that is not seeing the license >server. >>>The License server is W2K and in the same domain. The >>>registry fix is there and I have also tried the ip >>>address. Any ideas? >>>. >>> >>. >> >. > |
|
|
|
#5 |
|
Guest
Posts: n/a
|
My main concern is that some of your systems may be
considered 'untrusted' since they are not in your domain, and I don't think that the license server will issue licenses to systems that aren't trusted. Would it be possible to move one of the problem terminal servers into your NT domain and then checking to see if the problem still existed? -M >-----Original Message----- >The last reply was mine as well. My W2K servers are >member servers in an NT 4.0 domain. The servers that I am >having problems with are in different subnets. I see that >if they are in different subnets from the licensing >server, then it wouldn't be able to contact it. However, >I am using the registry key so that should override the >discovery. Could this be causing my issue due to the fact >that it is not overriding the discovery? >>-----Original Message----- >>The sevrer was restarted. The license server is on a >>member server. This is happening on 2 of our Terminal >>servers. >>>-----Original Message----- >>>After you installed the registry entry, did you restart >>>the server? >>> >>>Is this license server installed on the domain >controller? >>> >>>-M >>> >>>>-----Original Message----- >>>>I have a a W2K Ts that is not seeing the license >>server. >>>>The License server is W2K and in the same domain. The >>>>registry fix is there and I have also tried the ip >>>>address. Any ideas? >>>>. >>>> >>>. >>> >>. >> >. > |
|
|
|
#6 |
|
Guest
Posts: n/a
|
They are in the same domain. Some of the servers are at
regional offices, but in the same domain. >-----Original Message----- >My main concern is that some of your systems may be >considered 'untrusted' since they are not in your domain, >and I don't think that the license server will issue >licenses to systems that aren't trusted. > >Would it be possible to move one of the problem terminal >servers into your NT domain and then checking to see if >the problem still existed? > >-M > >>-----Original Message----- >>The last reply was mine as well. My W2K servers are >>member servers in an NT 4.0 domain. The servers that I >am >>having problems with are in different subnets. I see >that >>if they are in different subnets from the licensing >>server, then it wouldn't be able to contact it. However, >>I am using the registry key so that should override the >>discovery. Could this be causing my issue due to the >fact >>that it is not overriding the discovery? >>>-----Original Message----- >>>The sevrer was restarted. The license server is on a >>>member server. This is happening on 2 of our Terminal >>>servers. >>>>-----Original Message----- >>>>After you installed the registry entry, did you restart >>>>the server? >>>> >>>>Is this license server installed on the domain >>controller? >>>> >>>>-M >>>> >>>>>-----Original Message----- >>>>>I have a a W2K Ts that is not seeing the license >>>server. >>>>>The License server is W2K and in the same domain. The >>>>>registry fix is there and I have also tried the ip >>>>>address. Any ideas? >>>>>. >>>>> >>>>. >>>> >>>. >>> >>. >> >. > |
|
![]() |
|
| Thread Tools | |
| Rate This Thread | |
|
|

Main Page 

