TERMINAL SERVER REMOTE SESSION PROBLEM

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

When remote administration needs to take place for maintenance, a Terminal Server session would be established using the "administrator" login name, and because of the presence of multiple sessions already open and owned by "administrator", a list is of these sessions are presented to the establisher of the session. It is not possible to know which session is the one that is running the Navision dispacher, which is typically the session that needs to be connected to for maintenance. The required session is not always the first one established, nor does it always have the same session number as it might have had at any previous point in time. (Session numbers do not change, but for various reasons, previous maintenance work might have required the applications to be closed on one session and opened on another).

Therefore, if the session that is connected to is not the desired one, a switch is required to the correct one. This is accomplished using the Terminal Services Manager console application.

At unpredictable times, this act of switching fails, and the session that is switched from, as well as the session being switched to, becomes unresponsive. No keyboard or mouse input is sent through to the session, and no screen updates are received back from the session, and subsequent attempts (from newly connected or established sessions) to switch to either of these, repeats the failure, with yet another session becoming unusable.

This situation generally corrects itself, if given enough time, but this is generally requires more than an hour.
 
General security practices includes having all users, especially admins,
use personal accounts and not share generic accounts.
 
Instead of disconnecting from the Session, Log out of the Session? The only reason you would want to disconnect is to allow a maintenance application to continue to run. If your accessing the server remotely for maintenance, you should get in, perform your maintenance and then Logoff. Make sure that you add the "Logoff" option to the Start Menu, then if your done with your maintenance you can logoff instead of clicking on the Close button which Disconnects the Session. I don't why Microsoft doesn't allow you to choose the session when you reconnect remotely.
 
I've been prompted to select a session number before when I hadn't logged
out.

Geophelps.
 
Back
Top