Results 1 to 5 of 5

Thread: Windows 2000 Terminal Server Problem

  1. #1
    AO French Antique News Whore
    Join Date
    Aug 2001
    Posts
    2,126

    Windows 2000 Terminal Server Problem

    Here my problem... Sometime, my users lost connection to the Terminal Server. Their computer crash, Internet Crash, any reason is good. Bascially, the connection with the Terminal is broke. My problem is that the Terminal Server still thing they are connected. On the Terminal Server Manager, their status is active. This is false because the status should be disconnect.

    Question : How can I force the Terminal Server to change those session to disconnect state? I need a way so the server will ping the client to know if the client are crash or he's still available.

    Thank you.
    -Simon \"SDK\"

  2. #2
    Senior Member
    Join Date
    Oct 2003
    Posts
    707
    SDK don't know if this will help you much but you can give it a read :

    Progressive Perl for Windows: Managing Windows Terminal Services Sessions
    Operation Cyberslam
    \"I\'ve noticed that everybody that is for abortion has already been born.\" Author Unknown
    Microsoft Shared Computer Toolkit
    Proyecto Ututo EarthCam

  3. #3
    AO French Antique News Whore
    Join Date
    Aug 2001
    Posts
    2,126
    Not bad info but not exacly what I'm looking for.
    -Simon \"SDK\"

  4. #4
    Junior Member
    Join Date
    Jan 2005
    Posts
    6
    you can go into the TS permissions and tell it to disconnect after a certain number of minutes of idle time
    what thizz it[gloworange][color=#daff00][/color[FONT=times new roman][SIZE=3]

  5. #5
    AO French Antique News Whore
    Join Date
    Aug 2001
    Posts
    2,126
    This thread is way over. I fix my problem long time ago. Don't answer to thread that are old please.
    -Simon \"SDK\"

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •