Re: Terminal Session Information on Console

On the machine Xp thats runs Tsadmin (instaled localy), i conect to Windows
Server 2000 Terminal Services for review the rdp information connection
(anothers clientes), but these connections (rdp)are always empty (cero)

thank you very much.

"Soo Kuan Teo [MSFT]" wrote:

I'm sorry I'm not quite 100% clear on exactly what issue you have. Allow me
to share with you the expected behavior of Terminal Services Manager
(TSADMIN.EXE):
1. The information tab only shows information on a Terminal services (TS)
connection that is started with a rdp client (such as mstsc.exe). For
example, the information tab will be empty if you try it on a physical
console session, a disconnected session, a listener.
2. You need to do a few manual adjustments if you try to use tsadmin.exe to
connect to a remote XP professional:
2a. You need to add your user account (that runs tsadmin.exe) to XP's
local administrators group to be able to connect remotely .
2b. on the XP machine, please verify:
2b1. registry key
HKLM\SYSTEM\CurrentControlSet\Control\TerminalServer\AllowRemoteRPC is set
to 1.
A reboot maybe required if you change this setting.
2b2. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal
Server\fDenyTSConnections is set to 0.
2b3. Disable "Force Guest" logon. goto to local security pololicy
(secpol.msc)->Security Settings->Local Policies->Security Options->Network
access: Sharing and security model for local accounts, set to "Classic"
2b4. Firewall exceptions for "File and Printer Sharing" and "Remote
Desktop" needs to be enabled.

2c. On the machine that runs tsadmin.exe,
2c1. Make sure key manager does not contain the XP machines name,
goto Control panel->Stored User Names and Passwords. (Alternate way to
access this is with cmdkey.exe command line)

Thanks
Soo Kuan
--
This posting is provided "AS IS" with no warranties, and confers no rights.

"Americo Fernando" <AmericoFernando@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:47C79CE6-30D3-49AC-905E-6F7F092DFC55@xxxxxxxxxxxxxxxx
I am checking and terminal service manager console no show session
information when is runing on XP, but if terminal service manager console
run
on another Windows Server whether display information. Any idea ?

"Soo Kuan Teo [MSFT]" wrote:

What is the Windows version of Terminal Services are you running?
Can you please verify if you have the correct permissions to view those
information?

--
This posting is provided "AS IS" with no warranties, and confers no
rights.

"Americo Fernando" <AmericoFernando@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:E7E09B69-D926-4AF2-B25F-ADC22CB69456@xxxxxxxxxxxxxxxx
hello anyone

I use terminal service maneger remote console, when select information
tab
on client rdp-Tcp conection, no information is display all the fiels is
empty
(ex. Client built number : 0), But if i use the console localy the
information is display (ex. client built number: 2600)

any idea ?

thanks and regards




.

Relevant Pages

  • Re: Keyboard Madness in TS Environment
    ... all users on that client, I would stop troubleshooting the issue ... out multimedia keyboard to a USB keyboard. ... session from the terminal services manager. ... once I ended my connection, ...
    (microsoft.public.windows.terminal_services)
  • Re: Could Not Establish A Connection To The Remote Computer...
    ... This prevents the transfer of the permanent TS CAL to the client ... second connection, it gets a permanent license). ... We have Terminal Services in application mode along with its ...
    (microsoft.public.win2000.termserv.apps)
  • Re: Terminal Services Security Issue with Cached Credentials
    ... It did as the GPO says and still prompted me for my credentials ... the Vista client. ... You may also want to post in one of the Terminal Services ... "Always prompt client for password upon connection" ...
    (microsoft.public.windows.server.security)
  • Re: New TSClient to W2k3 AD Server
    ... I am not trying to connect to console. ... laptop as on AD member stationand from laptop it works ... client it worked fine from AD members. ... There you should see your existing console connection ...
    (microsoft.public.windows.terminal_services)
  • Re: Terminal Services Security Issue with Cached Credentials
    ... on a server and then tried connecting to it using cached credentials. ... the Vista client. ... You may also want to post in one of the Terminal Services newsgroups to ... "Always prompt client for password upon connection" ...
    (microsoft.public.windows.server.security)