Announcement

Collapse
No announcement yet.

XP to XP TSC stumper

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • XP to XP TSC stumper

    User is small business owner, has child and splits parenting, so MUST remote into an accounting machine in his office from home. RDC was working, but stopped. User is NOT an idiot, and has been working with other (paid) techs via phone support to resolve... called me in to do on-site troubleshooting and figure this out... doesn't want to buy new system, reinstall, etc.

    --at home, system 1, (old, cranky but clean
    Toshiba laptop) can't connect to system 2,
    (RDC server - XP pro SP2 no-name intel
    system) @ xxx.xxx.xxx.178 (SBC biz SDSL)
    from home DSL (Earthlink on SBC circuit),
    gets RDC window, but no login window

    --other techs moved RDC server from
    listening port 3389 to port 17000,
    changed (generic linksys) router
    settings to forward correctly, but
    the system still won't connect to RDC server

    --other RDC client on other (MY) machines (mac
    or windows based RDC clients) connect to
    the RDC server just fine from his home IP

    --checked for "invisible" login window,
    nothing doing, window is not starting

    --system has 3 users, all have exactly the same
    symptom

    --system 1 connects fine to other RDC
    servers, can daisy-chain from secondary
    RDC server to ...178 RDC server fine as
    well (this work-around is pro tem
    solution)

    --checked system for virii/malware, all clean,
    dumped caches all over system, all users,
    checked registry for bogus info, RDC and
    TermServClient keys are all clean and
    normal in HKCU, HKLM, etc

    --created another RDC server on ...178,
    forwarded 3389 to it, exactly the same
    result, other systems can connect directly
    without trouble, system 1 gets RDC
    window with no login screen

    --go to event log on ...178 RDC system, find
    event corresponding to each failed attempt:
    "termDD... event ID 50... The RDP protocol
    component X.224 detected an error in the
    protocol stream and has disconnected the
    client." All references in MSKB refer to
    updates to 2k servers...

    --at this point client informs me that system 2
    is bogus copy of XP and is not updating,
    AARRGH!!! Genuine Windows has been
    hassling him "for a couple of weeks, but
    after this started"...

    --rescheduled to make system 2 legit

    --will also try changing IP of office
    router (user has 8 IP's) to see if system 1 just
    hates ...178 IP

    I'm thinking a legit/updated copy will probably fix the issue, but still ... I'm com-$%^&-pletely stumped about exactly what is going on here... any help out there?

    jenni

  • #2
    Re: XP to XP TSC stumper

    huh?
    what is a "RDC server" and "TSC"
    Its seems that everyone is more stumped on the question the the problem
    "...if I turn out to be particularly clear, you've probably misunderstood what I've said” - Alan Greenspan

    Comment


    • #3
      Re: XP to XP TSC stumper

      so sorry...

      RDC server = remote desktop connection server
      TSC = terminal services client

      i realize the two are not directly interchangeable, but they rely on the same technology, and merely exist in different contexts, i.e. domain/server environments vs. home/soho users.

      Comment


      • #4
        Re: XP to XP TSC stumper

        the only thing i can think of the KB's related to the event log entry "The RDP protocol
        component X.224 detected an error in the protocol stream and has disconnected the client"

        Have you checked them out?

        if that does not work try rename HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing
        (EG: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensingOLD)
        "...if I turn out to be particularly clear, you've probably misunderstood what I've said” - Alan Greenspan

        Comment


        • #5
          Re: XP to XP TSC stumper

          i did locate those, and a few other KB articles regarding the x.224 event log item, but unfortunately, none of those keys existed on the XP machine hosting the RDC service... i believe those keys are specific to Windows Server OS versions, as opposed to Windows XP.

          The other KB articles said to update/patch the OS, but were also referring to Server OS versions.

          Also, please note that the connecting computer (system 1 above) isn't getting any prompt or error from the hosting machine (system 2 above), merely a blank background in the Remote Desktop window... full screen vs. windowed made no difference, nor did any of the other selectable options in the Remote Desktop Client (disable bitmap caching, color resolution, username saved or not, etc.)

          peace,
          jenni

          Comment


          • #6
            Re: XP to XP TSC stumper

            if that does not work try rename HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing
            (EG: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensingO LD)
            This part is for the "old, cranky but clean Toshiba laptop"

            Just continuing to brainstorm here, try changing one or both of the computer names...with caution.
            "...if I turn out to be particularly clear, you've probably misunderstood what I've said” - Alan Greenspan

            Comment


            • #7
              Re: XP to XP TSC stumper

              Have you removed System 2 completely form the "network" (for want of a better work.), that is, unplugged the cable! Not only does this remove it totally from the equation and any, albeit remote possible cause of the problem, but it also means you won't be working on rectifying a problem on a machine with illegal software.

              I would consider advising the client in writing that he is breaking the law by running illegal software on his computer.
              1 1 was a racehorse.
              2 2 was 1 2.
              1 1 1 1 race 1 day,
              2 2 1 1 2

              Comment


              • #8
                Re: XP to XP TSC stumper

                ok, checked the old toshiba (system 1) for the keys also, not there either.

                Also, the "system 2" machine is the target (the machine we want to connect to) so removing it would... well that'd be nice, but it isn't possible. And, for the record, he's been advised that he'll have to buy a legit license for the "system 2" machine before i do anymore work for him.

                peace,
                jenni

                p.s. - thanks for the suggestions so far!

                Comment

                Working...
                X