higherho wrote: » Any suggestions?
Devilsbane wrote: » Is someone logged in locally?
instant000 wrote: » When you check the sessions, how many do you see logged into the server? How many console, and how many remote?
instant000 wrote: » That's doubtful. Would you have reason to be suspicious of that? Any recent maintenance done on the server? When was your last backup? It is running Windows ... if you cannot verify any changes, you could reboot it and see if that clears it.
Budzy wrote: » Hi higherho, Perhaps have a look at this if you haven't already checked it: On the server's desktop: under admin tools -> Terminal services configuration Under connections, you should see RDP-tcp, open up the properties of this. Select the Network adapter tab and make sure the maxium connections option is set to 2. As long as the licencing mode is set to remote administaion then this should work unless we're dealing with a greater problem here. Edit: Not sure if you need to restart the terminal server service once you do this.
higherho wrote: » It was hardened a little bit ago by another individual and before that it did work so I was just nailing down possibilities on what he could have changed.
ChooseLife wrote: » That brings up a number of questions... Are you really supposed to unharden the server? Can you work with the individual to undo the change?
MrAgent wrote: » I would definitely go and check your policies again. I had the same issue once. Turned out to be a local policy.
Devilsbane wrote: » Run rsop.msc on the computer to get the result of all the policies applied. If you do find that the policy is set somewhere, Rsop will tell you where so that you can go change it.