I have installed terminal services for the 1st time. I have installed the 32bit client on a win98 machine. The server is set up as an application server. I can attach from the 98 machine but when I try to log in I get a message saying "Local security does not allow interactive login" I am pretty sure I am just missing a setting somewhere. Can anyone point me in the right direction? Mike

You may receive 2 different messages upon an attempt to establish a TS session. First is the one you are seeing, by default WIN2K Server does not allow a user to login locally to the server(interactive=local logon) which is what TS does, if you use an Administrator account there should be no problem establishing a session. After you configure you security policy to allow an account with user rights to logon locally, you may then receive an error stating "unable to logon to a TS session" or something to that effect. At that point you need to go into the TS configuration on the server and right click the RDP-TCP connection and go to permissions and you also have to allow users the ability to establish a session, after all that is done TS will work. Good luck, e-mail me for further guidance.

Thanks, I am testing it on our intranet. When I eventually try from home I need to know what(if any) ports need to be routed through our router to the server. Mike

List of Ports Used by Terminal Server Clients Function Static ports -------- ------------ RDP Client (Microsoft) TCP:3389 (Pre Beta2:1503) ActiveX Client (TSAC) TCP:80, 3389 ICA Client (Citrix) TCP:1494 NOTE: Terminal Server uses port 3389.

You have been a big help. However I can't find the permission to fix my original problem. I have a user I created called mrtest I am testing ts with. I have added him to "logon locally" in local security policy,domain security policy, and domain controller security policy on the server. None of it seems to make a difference. I can make him an administrator and it works but I don't want to make every ts user a admin :-) Mike

within the security policy allow TSInternetUsr the ability to log on locally.

Stevemm, with all due respects, I believe the problem is not that by default Server does not allow regular users to log on to TS, which it will(when it's a stand alone server), the problem was becase a domain controller will not allow regular users to log on locally, whether it is on the console or Terminal Services, and he setup TS on a domain controller. Also Mike, be aware of Microsoft's licensing requirements with TS. After 90 days, the server will require you to purchase licenses for every client that want to connect to TS, except for administrative accounts. It will cut off people after 90 days. However, Windows 2000 on up clients can continue connecting, because they have built in license generators and the license server permits it. So, pay for the license, or pay to upgrade the operating systems. Happy TS'ing.