Term Services Question - Newbie 4

[djones2002]

Howdy.

This is going to be a tough one, I think.

I've got term services set up on my Win2k server, and am currently testing it for deployment to our remote sites. This is really my first dabble with term services, so I'm a complete newbie.

Anyhoo...Myself and the other IT person here are able to log into the term server using the client with no problem. We are both Administrators. However, when trying to log into the term server using one of my user's logons, I get "The local policy of this system does not allow you to log in interactively".

I've looked at my local policy on the server, and nothing stands out. To be certain, I added "Terminal Server Users" to the "Log onto this machine locally" policy on the server. I have also verified that the user(s) in question have "Allow Terminal Server login" checked in their user profile in AD.

This is a sticky one.

Any thoughts?

Dennis Jones

 

[skotman]

Dennis,
How do you have your Tserver setup? Is it in Admin mode or App Mode?
If it's in Admin mode anyone who connects must be in the admin group. Windows 2k and up comes with 2 free Admin client licenses for TS.
If it's in App mode, anyone should be able to connect for 90? dats (it may be less) then after said time it reverts back to admin mode.
App Mode requires a TS CAL for each connected session

Scott Heath

http://www.scottspad.com

AIM: orange7288

 

[djones2002]

Scott:

Thanks for the info.

How do I check which mode the TS is in?

 

[skotman]

Dennis,
The only way I've ever done it is as follows:

Add/Remove programs: Windows component option: click next with out changing anything.

You should see it there. It really sounds like it's in Admin mode though as that is the default.

Scott Heath

http://www.scottspad.com

AIM: orange7288

 

[djones2002]

Scott:

I believe you are correct. I checked the "Term Services Licensing" applet under Admin Tools, and the server shows as "Not Activated". I was under the impression we had the appropriate licensing...now I've got to verify that and activate the server. Thanks for the help.

Dennis Jones.

 

[fraziergs]

I believe that the problem is with the users that are allowed to logon to the server. If the server is a domain controller you can setup which users can and can't logon to it through the Domain Controller Security Policy.

Windows settings | Security Settings | Local Policies | User Rights Assignments | Log on locally

 

[skotman]

That is true but I dont believe that this is the case since their usernames are allowed to login and both apear to be in the admin group.

Scott Heath

http://www.scottspad.com

AIM: orange7288

 

[Dmasch]

You problem is that you do not have the users setup in the RDP protocal. To do this you will have to go in your admin tools Terminal services configuration, double click on RDP 5.0 then click on permissions tab, add system in there if it is not and then click that that it can have all the access. This is your problem. been there done that.

 

[PHead2]

Run tscc.msc from the command prompt. Look under Server Settings - you should be able to see if you are in remote admin mode or app server mode.

If it's in remote admin mode change it app server mode by reinstalling terminal services and picking the right option.

You also need to add the users to the RDP users group. While this alone will allow users to logon only 2 sessions will be allowed at a time if you are not in app server mode.

The licensing issue is a seperate one - you would get a message stating that no license is available if that were your problem (which it will be when the eval period is up if you haven't activated a license server by then).

 

[djones2002]

Howdy.

Thank you all for the info.

I did go in and add them to the RDP permissions. However, this has not helped.

I followed through on Scott's info and got my license server activated, and installed a 10 user cal. Since I have only one license server, I added a registry key to force my term server to point to my license server by it's NetBios name by default. I also reinstalled term services to force it into App Server Mode.

None of these has worked, and to be honest I'm at a loss.

Any thoughts would be greatly appreciated.

Dennis Jones

 

[djones2002]

All set on this. The term server is installed on a domain controller for reasons beyond our control. So, we changed the DC Policy setting to "Allow Logon Locally" to authenticated users. No problems, now.

Thank you all again.

Dennis Jones

 

[Wayne426]

All,

I have virtually the same problem as Dennis had. I have worked through the connectivity issues, but need to reinstall terminal services into App Server mode. When I start the process, I receive a dire warning about software possibly not working correctly after I change configurations. The box then lists virtually all my installed software, including Small Business Server. In hindsight, I should have made this change right after installing Win2K server. I would like to avoid rebuilding our entire server if possible (groan) Is this a change that can be made safely to a working system?

Thanks for all replies,

Wayne

 

[Dmasch]

In my experience all was still ok. I had bout 5 programs installed also and they all still worked after the change.