unable to see TS license server on another subnet

[katie]

Hello.

Here's the scenario: We have multiple subnets and for the purpose of this
question, let's just say that there are two subnets: A and B. The domain is
Windows NT 4.0

The TS License server resides on subnet A. All other TS servers in App mode
and also on the same subnet (subnet A) have had no issues locating the TS
License server.

I have a TS server (in app mode) on subnet B and it is unable to see the TS
License server on subnet A. If I put the TS server on the same subnet as
the TS License server, it has no issues locating it. I am able to ping the
ip, netbios and fqdn of the TS License server from the TS server on subnet
B.

I've tried the manual registry entry of pointing the TS server to the TS
License server by using the netbios name, fqdn name and also the ip address.
No success.

I need to have this server reside on a different subnet from the TS License
server. Could this be a network block issue? Is there a dedicated port
that TS servers use to communicate to TS License servers?

Please help provide any suggestions/whitepapers/etc, that may help resolve
this issue.

Thank you.

--Katie

 

[Rob Leitman \(MS\)]

The registry method should work. Are you using the Win2000 or Win2003
method? Each version of Terminal Server uses a different technique.

Rob

--
This posting is provided "AS IS" with no warranties, and confers no rights.
TS FAQ:
http://www.microsoft.com/windows2000/community/centers/terminal/terminal_faq.asp
TS Licensing Chat, Nov. 5th:
http://www.microsoft.com/technet/itcommunity/chats/default.asp

 

[katie vang]

Both TS License and app TS server are on Windows 2003.

If I put the TS server on the very same subnet as the TS license server, it
has not problems seeing the license server.

Do you know of how else I may troubleshoot this from a network stand point?
I am guessing there may be a blocking of what types of traffic can go
through the different subnets.

--katie

 

[Rob Leitman \(MS\)]

Just to clarify:

You're using the process described in
http://support.microsoft.com/default.aspx?scid=kb;en-us;q279561 to point the
TS to the LS? (The License Servers registry key method)?

Rob

--
This posting is provided "AS IS" with no warranties, and confers no rights.
TS FAQ:
http://www.microsoft.com/windows2000/community/centers/terminal/terminal_faq.asp
TS Licensing Chat, Nov. 5th:
http://www.microsoft.com/technet/itcommunity/chats/default.asp

 

[Rob Leitman \(MS\)]

That looks right, assuming MCAEDSTERM is the name of the License Server.

The TS uses RPC traffic to talk to the LS. If there's no firewall between
the TS and LS, I don't know what would cause this. You may have better luck
talking to Microsoft Product Support.

Rob

--
This posting is provided "AS IS" with no warranties, and confers no rights.
TS FAQ:
http://www.microsoft.com/windows2000/community/centers/terminal/terminal_faq.asp
TS Licensing Chat, Nov. 5th:
http://www.microsoft.com/technet/itcommunity/chats/default.asp

 

[katie vang]

Thanks for your help. I will do some more testing before talking to
Microsoft.

Another question for you though: is there anything that has to be done on
the TS License server once the registry entry has been made on the normal
application ts server?

--katie

 

[Rob Leitman \(MS\)]

You may have to add the Terminal Server to the Terminal Server Computers
security group on the License Server. Check for eventlog messages on the
License Server.

Rob

--
This posting is provided "AS IS" with no warranties, and confers no rights.
TS FAQ:
http://www.microsoft.com/windows2000/community/centers/terminal/terminal_faq.asp
TS Licensing Chat, Nov. 5th:
http://www.microsoft.com/technet/itcommunity/chats/default.asp