• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 3498
  • Last Modified:

Remote Desktop Services Manager

We have serveral Windows 2008 R2 servers, and I would like to use Remote Desktop Services Manager on Windows 7 to access the Windows 2008 R2 servers. But I get access denied when I try to connect to the remote computer.

I opened ports like 135 and port 445, but still I get "Access Denied".

Is there some more ports I need to open?
0
Mr Woober
Asked:
Mr Woober
  • 4
  • 4
  • 2
  • +1
1 Solution
 
hutnorCommented:
have you got permission to rdp to that server & log onto it?

Is remote access set to allow on the server?

Have you ticked the options on your firewall to allow remote desktop connections?
0
 
hutnorCommented:
turn turn off the server firewall & connect to see if it is a firewall issue.
0
 
hutnorCommented:
Here is a list of all Microsoft ports incase you want to have a look.
http://technet.microsoft.com/en-us/library/cc875824.aspx
http://support.microsoft.com/kb/832017
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
TheMakCommented:
did you got login screen when you tried RDP connection to Windows 2008 server? If yes then problem with the user name you are using.... Use users with full admin privileges and first see if you are able to to login with that users locally on that server and then try RDP.

Anyhow if you still faces problem give us some more details. Like exactly when you get this error message

Regards,
0
 
Mr WooberAuthor Commented:
Yes, I can access it thru RDP and added myself as user. But I still get "Access Denied" when I try to connect the computer via Remote Desktop Services Manager.

I checked the log in the firewall, but there is no log for this. The firewall on the Windows 2008 server is turned off.
0
 
acl-puzzCommented:
Hi

1.make sure this user is member of "Remote desktop user" group

2. Test if port 3389 is open or not like this suppose ip of server is 192.168.1.1

telnet 192.168.1.1 3389

if you see blinking cursor that means port is open if not that means port 3389 is not open which is used by RDP
0
 
hutnorCommented:
he is not trying to RDP/mstsc to the server. he is trying to manage it using a mmc snap in.

I use the Remote Desktop Services Manager with win7 on 2008 & did not need to configure much.

Is the user running the Remote Desktop Services Manager have access to the server?
0
 
TheMakCommented:
Verify that the following services are started:
Remote Registry
Remote Procedure Call (RPC)

Please install the service packs and other updates becoz if it some kind of bug then it will be fix after applying updates.

And also have a look to this article below, Using Remote Desktop Services Manager, RDS CAL,

http://searchsystemschannel.techtarget.com/generic/0,295582,sid99_gci1506672,00.html

Regards,
0
 
Mr WooberAuthor Commented:
I get an error in the log on my computer which says:

DCOM could not communicate with computer 192.168.20.60 with use of those configured protocols.

Seems like its missing a service or something. I checked that Remote Registry and Remote Procedure Call (RPC) is running.
0
 
Mr WooberAuthor Commented:
Ok, I try to add the Remote Desktop Services Manager to connect to computer 192.168.20.60 but when I try to open it, it says "The specified computer could not be reach. Make sure that the computer is accesible and verify computer name"

When I try to access it from my computer I have to login with my username/password to access this computer. Maybe there is some security policy thats missing on the W2k8 server?
0
 
Mr WooberAuthor Commented:
Some port mappings was missing, works now :)
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

  • 4
  • 4
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now