Trouble connecting to a terminal server licensing server.

Hi there,

Here is the scenario:

LAN with Workgroups as follows (No Active Directory or Domain):

WORKGROUP
- SRV01 - Win2003 Server Standard Edition - Terminal Server role and Terminal Server Licensing role
- SRV02 - Win2003 Server Standard Edition R2 SP1 - Application Server role and Terminal Server role

HEAD OFFICE
- SRV03 - Linux Server acting as a file server
- WinXP Pro SP2 clients

ACCOUNTING
- WinXP Pro SP2 clients

All devices are 192.168.100.0,255.255.255.0 and the router (DHCP & DNS) is 192.168.100.2.

Here is the problem.

SRV02 can't connect to SRV01 as its licensing server!

I have added SRV01 as a registry key under HKLM.../LicenseServers and it attempts to locate it but returns the following error:

"No Terminal Server license server is available in the current domain or workgroup. To connect to another license server, click Action, click Connect, and then type the server name."

There is no firewall running on either server and the same happens regardless of whether anti-virus is running.

I'm not sure if it's relevent but I have changed the RDP listening port to 3390 on SRV02 so as to distinguish it from SRV01.

Your help will be gratefully received. If I had hair, I'd have pulled it out by now!!!

Regs,
Bill.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

dmccurdy51Commented:
For grins I would change the port back, reboot, and try again.

My first real thought is the registry key is is not setup correctly.  I would also try the IP address instead of name.  

Also I believe in R2 Microsoft include a GPO and or a setting under the "Terminal Server Configuration" utility to define the license server.  You might look there first.

This site may help you troubleshoot.
http://technet2.microsoft.com/WindowsServer/en/Library/0f7c0e36-5b67-4830-a30f-b0fb3ad91dee1033.mspx

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.