Terminal Services is Jacked UP!!!
Greetings:
I want to allow simple remote administration of our 2003 Server that is acting as a DC. I only want to grant myself access to this as administrator. I have had myriad problems; here is my story:
After installing 2003 Server and AD, I was able to connect via terminal services just fine. One day I had a friend connect from outside of our network to test my ability to remotely troubleshoot the machines while I was traveling. I simply gave him my username and password and allowed him to test using that (i was unsuccessful in granting him access using a different user account). Ever since then, when I tried to connect via RDP, I got the "there are no terminal servers licensing, blah blah blah) error. So I went into the Terminal Services configuration and changed to Per User licensing. This allowed me to connect via TS to at least get the authentication dialog box. When I tried to log on as administrator, I got the "Local Policy does not allow you to logon interactively error). So I went into the GP for the domain and changed the "Allow Logon Locally" to allow the accounts that I desired to log on locally. Now when I try to connect I get the "You do not have access to this session" error. ***Note all errors messages are as I can remember them and not 100% exact, but I think I have conveyed the gist of the message.
I'm stumped. This shouldn't be a tough thing to do.
I want to allow simple remote administration of our 2003 Server that is acting as a DC. I only want to grant myself access to this as administrator. I have had myriad problems; here is my story:
After installing 2003 Server and AD, I was able to connect via terminal services just fine. One day I had a friend connect from outside of our network to test my ability to remotely troubleshoot the machines while I was traveling. I simply gave him my username and password and allowed him to test using that (i was unsuccessful in granting him access using a different user account). Ever since then, when I tried to connect via RDP, I got the "there are no terminal servers licensing, blah blah blah) error. So I went into the Terminal Services configuration and changed to Per User licensing. This allowed me to connect via TS to at least get the authentication dialog box. When I tried to log on as administrator, I got the "Local Policy does not allow you to logon interactively error). So I went into the GP for the domain and changed the "Allow Logon Locally" to allow the accounts that I desired to log on locally. Now when I try to connect I get the "You do not have access to this session" error. ***Note all errors messages are as I can remember them and not 100% exact, but I think I have conveyed the gist of the message.
I'm stumped. This shouldn't be a tough thing to do.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
i agree in all what dis931 sayed.
just one point differs: in windows 2003 the TS grace period is 120 days.
just one point differs: in windows 2003 the TS grace period is 120 days.
thanks for the correction WeHe, I thought I remember it changing for 2003 but didn't remember...thanks
you are right, it has changed.
on w2k its 90 days, on w2k3 its 120 days :)
on w2k its 90 days, on w2k3 its 120 days :)
ASKER
I was going to uninstall TS but I got a warning that any application installed after TS will be unusable. I don't believe that I have installed any applications since the server was set up but I 'm wondering does this mean that those apps will be disabled?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
The "Allow Terminal Services Logon" for the user was unchecked in the AD.
Dis