none
TS 2008 - Event id 303 during logon process RRS feed

  • Question

  • Hi,
    during the logon on the windows 2008 terminal server farm, the ts gateway records an event id 303 with only few seconds of session.

    Here an example:
    The user "DOMAIN\user", on client computer "x.x.x.x", disconnected from the following network resource: "ts-farm.domain.local". Before the user disconnected, the client transferred 9111 bytes and received 53882 bytes. The client session duration was 1 seconds.

    Here the events sequence on ts gateway:
    1. id 200 (authentication metod)
    2. id 300 (authorization policy)
    3. id 302 (connected to ts-farm)
    4. id 303 (disconnected to ts-farm after 1 second?!?)
    5. id 200 (authentication metod)
    6. id 300 (authorization policy)
    7. id 302 (connected to ts-farm)

    The strange thing is that the logon process goes to end without problems.

    Is it normal?

    Thanks,
    Simone

    Thursday, April 2, 2009 12:25 PM

Answers

  • Do you have TS Session Broker deployed as well?
    This sequence of events will happen (and is expected) when you already have a session on one of the TS in the TS farm and then next time when you connect to the TS farm the first connection might happen to a different TS machine in the farm. The session broker then detects that you already have a session on some other TS and hence instructs the client to reconnect again to the TS where you already have a session. Hence the first connection gets disconnected and you see a whole new sequence of connection happening in the TS Gateway eventlogs. Hope this is clear to you now!!

    Thanks
    Vikash

    • Proposed as answer by Rong ChenModerator Wednesday, April 8, 2009 5:50 AM
    • Marked as answer by Simogoose Wednesday, April 8, 2009 8:00 AM
    Wednesday, April 8, 2009 4:45 AM
    Moderator

All replies

  • Do you have TS Session Broker deployed as well?
    This sequence of events will happen (and is expected) when you already have a session on one of the TS in the TS farm and then next time when you connect to the TS farm the first connection might happen to a different TS machine in the farm. The session broker then detects that you already have a session on some other TS and hence instructs the client to reconnect again to the TS where you already have a session. Hence the first connection gets disconnected and you see a whole new sequence of connection happening in the TS Gateway eventlogs. Hope this is clear to you now!!

    Thanks
    Vikash

    • Proposed as answer by Rong ChenModerator Wednesday, April 8, 2009 5:50 AM
    • Marked as answer by Simogoose Wednesday, April 8, 2009 8:00 AM
    Wednesday, April 8, 2009 4:45 AM
    Moderator
  • Yes,
    there is a TS Session Broker.

    Thanks for your reply.

    Simone

    Wednesday, April 8, 2009 8:02 AM
  • Hi,

    I have the same question as Simone.

    The user that logs on has no other sessions open on any of the TS's, so the proposed answer doesn't apply.

    The first logon/logoff session connects to the FQDN of the farm, using the DNS name of the broker. The second logon/logoff session connections to an IP address, being an address of one of the RS's (session hosts).

    Since we als suffer from several seconds in the logon process (5 secs), this is somewhat anoying for the users.

    Anyone knows why this is happening?

    Thanks, Stanley.

    Saturday, August 7, 2010 8:16 PM