Jump to content

AD permissions messed up


djryback

Recommended Posts

I have a serious problem with my domain at work. I work in a school, we used to have one windows 2003 server as a DC.

Meanwhile I installed another server with 2008 r2 platform and set it as additional DC. Then I reinstalled the first one so, now both of them have 2008 r2 operating system.

Active directory with users and policies was created few years ago and worked fine. There were basically 3 types of users:

- student (user with minimal rights)

- teacher, and other staff (SuperUser)

- administrator (domain admin)

Until few days everything worked fine, as only administrator was able to use Remote Desktop or access for example server's c$ or d$ drive.

Now somehow it's all messed up, and I don't recall doing any changes in AD or GP.

So symptoms are these:

- Students, teachers and all other users are able to connect via remote desktop to any machine including server.

- All of them are able to access \\server\c$ or similar folders by DEFAULT (this did not change on other workstations, only servers)

So my questions are these:

Does anyone know this kind of behaviour from experience to give me fast solution?

If not, where exactly in active directory group policy I can reset those options:

- forbid using of remote desktop for all user except Administrator

- forbid browsing of any folders by any users unless it's specifically shared to that user

Another thing:

From a XP computers lately I've been getting message that I can't run Remote Administrator, no matter if I'm logged as administrator or other user

Does it have something to do with the fact I've raised functionality level of domain to 2008 r2? Message displayed is:

"Remote computer requires network level authentication, which your computer does not support."

Thanks in advance

Link to comment
Share on other sites


For the XP issue, look at the "Known Issues affecting XP package" here:

http://support.microsoft.com/kb/969084

I've tried now to run Remote Desktop on XP machine (but I'm connected via Remote Desktop to it, since I'm not physically there) and it works. Can it be that it works only from remote location ? Earlier today when i was at work I was localy at the computer and it didnt work.. what does it mean?

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...