Configure SBS Remote Desktop for one session ONLY, BUT not locking new connection attempts




Hi there. I'm having this issue with a rather *fresh-install of SBS 2003
(no Service Packs)*.
Before fresh-installing, i had this configured just as I wanted. But
now, I can't seem to find my way through this.

Please, can anybody tell me: how can I limit AND/OR allow to choose
which remote session to login to (since the same user can create two
sessions+console session), when using remote desktop to access SBS
2003, BUT in a way that new connection attempts are still allowed
(automatically replacing active connection(s))?

BASICALLY I'M TRYING TO CONFIGURE IN MY SERVER WHAT WOULD BE THE
WINDOWS XP BEHAVIOR REGARDING REMOTE DESKTOP CONNECTIONS.
This means I currently have two problems.

The server is allowing two concurrent connections. I tried to mess
around with the Terminal Services Configuration to limit that, but that
brought me a "hidden issue" that I didn't have in the past.

Consider the following scenario:
- You remote desktop into your server;
- Connection drops (due to an internet-related problem, for instance),
and you eventually have to leave your current location, so you just
close down the RDP window, expecting to finish your server mainteinance
later;
- *EDIT:* or you just lock the session in some computer you were using,
and suddenly had to leave in a hurry, forgetting to disconnect the
remote session;
- When you try to remote desktop again at a later point, the connection
is almost immediately refused (my laptop OS is in Portuguese, so I can't
really tell what the precise message is, but it's something like:
"This computer couldn't establish a connection to the remote computer.

Try to connect later. If the problem persists, contact the remote
computer owner or the network administrator.")


*The behavior I'm looking for is something like:*
- Server would accept new connections every time, "kicking" the
currently active connections in the case of a successful login;
- Users would login to active sessions and not to new ones - this
allows to continue the interrupted work.


Thank you in advance for your time and support. If you have any further
questions, please feel free to ask.

Kind regards,
Luis Domingues
(footswitch)


--
footswitch
------------------------------------------------------------------------
footswitch's Profile: http://forums.techarena.in/member.php?userid=38931
View this thread: http://forums.techarena.in/showthread.php?t=947176

http://forums.techarena.in

.



Relevant Pages

  • Re: RDP fails with "This computer cant connect to the remote computer" with no Terminal Services err
    ... Remote Desktop for Administration and did not require a TS Licensing Server ... Frame 8 resets the TCP connection. ...
    (microsoft.public.windows.terminal_services)
  • RE: Cant Connect to Remote Desktop on External Network
    ... server I CAN NOT connect to these same EXTERNAL networks using VPN and Remote ... Yes I reran Email and Internet Connection Wizard. ... external network or you can not RDP to external network from SBS and LAN ... Accessories and Communications and Remote Desktop Connection? ...
    (microsoft.public.windows.server.sbs)
  • Re: Remote Desktop connect then disconnects
    ... I forgot to add that this compute can use Remote Desktop to connect to our ... Just delete the connection in TS Configuration, ... MCSE, CCEA, Microsoft MVP - Terminal Server ... established A network problem occurred. ...
    (microsoft.public.windows.terminal_services)
  • Re: SQL Server / ADP Not Saving All Information
    ... connection, including the remote desktop, so I cannot tell you more on this. ... Server backend running on Windows 2003 Terminal Server. ... Does SQL Server 2000 have an autosave feature? ...
    (microsoft.public.access.adp.sqlserver)
  • Re: Remote Desktop over VPN connection
    ... Firewall is turned on that there is an exception for Remote Desktop. ... I found that if I establish the VPN connection using IP ...
    (microsoft.public.security)