General discussion


Terminal Server - No Connection

By johnnow ·

I inherited this problem. Windows 2000 AD with a 2000 Terminal Server and Licensing Server. They added a 2003 Terminal Server but did not activate Licensing. 120 Days Ran Out. I started. I activated 2003 Terminal Licensing on the 2003 Server. I purchased per user cals. I went into the terminal server config and told it that it was its own license server. Problem is I can connect to the 2000 TS Server but when I try to connect to the 2003 TS Server I get a msg that you must be a member of Remote Desktop users group. I check the groups on the 2003 TS Server and I am a member. What am I doing wrong.

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Comments

Collapse -

by NZ_Justice In reply to Terminal Server - No Conn ...

Sonds like permissions:

Make you user login an Administrator of the 2003 Administartors group, so that that login has permissons to terminal into the 2003 Server, to achive this logon to the box localy using the local admin account, then add your domain user login to the admin group.

It could also be that your 2003 server has not joined the domain, Read add you windows 2003 server to your domain.

Collapse -

by curlergirl In reply to Terminal Server - No Conn ...

On the terminal server, check the Local Security Policy/Local Policies/User Rights Assignment and be sure that the Remote Desktop Users Group has been added to the "Allow users to log on through Terminal Services" user right.

Hope this helps!

Collapse -


by morwickdzhalagome In reply to Terminal Server - No Conn ...

can you send me infor about mcse server 2003?

Related Discussions

Related Forums