Re: RDP limited but RWW just fine



Nicholas wrote:
On Jul 23, 4:38 pm, "Gregg Hill" <greggmhill at please do not spam me
at yahoo dot com> wrote:
The actual limit is THREE **simultaneous** sessions, but ONLY for
administrative access to the server for the purpose of server management,
not running applications, per the licensing.

How do you get all three? Run Remote Desktop Connection twice normally for
session 1 and 2, then run "mstsc /console" (or "mstsc /admin" for the new
RDP client) to get to session 0. Three connections available at the same
time!

As noted by others, check the TS Manager to see if you have a session open
already that someone has left hanging.

Gregg Hill

"Nicholas" <gro...@xxxxxxxxxxxxxx> wrote in message

news:8545d3e8-26af-425d-a567-bc6c415b8ed6@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

New SBS 2003 system went in last weekend. Users consist of 3 with
admin rights (including administrator), 1 with poweruser, and the rest
users.
We find now that only the admin and the 1st user that was added with
admin rights can rdp to the box. The other admin user always sees the
'server has exceeded' message on login attempts.
Further, we added a test users with admin rights, and that user has
the same problem; cannot get
past the exceeded msg.
However, RWW allows everyone in that should be allowed just fine. We
see the 'exceeded' message only when that condition actually exists,
during rww use. It seems that only the first 2 admin users are being
allowed to RDP in though. I realize docs say only 2 admins on rdp,
but doesn't that refer to 2 logged-in admins, and not just users with
the privs? Or are we reading it wrong here?
?

Gee... no one really gets it here, I guess. No offense intended, but
you guys aren't reading
my posts, I guess. There are NO CONCURRENT LOGINS going on here. The
problem is,
why is my office manager login with admin privs being denied entry?
When her login is used,
there are NO other RDP sessions active. Zero. Nada.

Ok. Let's try this:

1. I log on using RDP with username A: fails, "exceeded" message.
2. I immediately try again using username B: Succeeds.
3. I log off, and then try RDP again with username A: Fails,
"exceeded" message.

The simple way to state the problem is, I have a user with Admin privs
who cannot RDP to the server directly,
as she always get the "exceeded" message on attempting.

However, if we use the Admin account, or my own personal login, those
two always are allowed entry.

In all cases, there are NO OTHER RDP sessions active. So there is NO
"exceeding" environment present. It's just me, or myself and
the office manager working here. The other system activity is all
users, and very low useage as well.

Make sense now?



When I am at my workstation with "my" user account, that account has no RDP rights to the server.

I use a domain administrator account (a separate one) to log into the server.

There are workstations administrators and Domain administrators.

Make sure she is given a separate domain admin account separate and distinct from her user account to log in.

I'm guessing that this account has "workstation" administrator rights, but not true domain admin rights.
.



Relevant Pages

  • Re: Administrator Privlidges for all
    ... admin privlidges. ... >Windows 2000 pro Server. ... >share a folder and restrict access to that folder there ... select Administrator. ...
    (microsoft.public.windowsxp.security_admin)
  • Web Server - User Access and Priviledges.
    ... restriction policy that came out with the server 2003 ... Have a logon for your everyday use and one admin ... account that your or only a few people have access to. ... >Create a second Administrator account on each Web Server. ...
    (microsoft.public.win2000.security)
  • Re: Prevent Admin Logon to RWW
    ... 'Administrator' does not have RRAS rights, if I wish to VPN to a server I do so using a less priveleged account, I may then use the VPN to RDP as 'Administrator', OR since the introduction of RWW RDP Proxy I would prefer to 1st 'Connect to my computer at work' as a non-priveleged user and then RDP to the server with elevated priveleges. ... you can still do remote admin work ...
    (microsoft.public.windows.server.sbs)
  • Re: Terminal Services Setup/Flaw
    ... What do you think is allowing the connection with .rdp to another server? ... check the local RDU group on the local server one more time and see who is a member of that group. ... What would I modify in that group policy to inhibit this type of login? ... domain admin priviledges and went to work last week. ...
    (microsoft.public.windows.terminal_services)
  • Re: Unable to connect to 2K3 Server with RDP 6
    ... Second, I'm assuming that this is not the administrator account for the domain, just the machine you are logging into. ... RDP 6.0 assumes the domain is the same as the client machine's unless specified otherwise. ... The client and the server are on the same domain. ... > This computer can't connect to the remote computer. ...
    (microsoft.public.windows.terminal_services)