[THIN] Re: Troubleshooting Remote Access Problem
- From: Christopher Wilson <christofire@xxxxxxxxx>
- To: thin@xxxxxxxxxxxxx
- Date: Wed, 25 Mar 2009 10:46:46 -0500
Found a resolution:
In the RDP properties you can specify a specific network adapter. Should
not have been an issue in this case since there is only one adapter. The
RDP settings were configured to use "All network adapters configured with
this protocol". For some reason, explicitly identifying the adapter was the
fix. With one adapter both settings **should** mean the same thing. Go
figure.
On Wed, Mar 25, 2009 at 9:52 AM, Raffensberger, Stephen D <
sraffens@xxxxxxxxxxxxxxxxx> wrote:
> I would check the event logs on the terminal server for clues…especially
> Microsoft licensing problems.
>
>
>
> Steve Raffensberger
>
> CSG Citrix Administrator
>
> Sovereign Bank
>
> email: sraffens@xxxxxxxxxxxxxxxxx
>
>
> ------------------------------
>
> *From:* thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] *On
> Behalf Of *Christopher Wilson
> *Sent:* Wednesday, March 25, 2009 10:42 AM
> *To:* thin@xxxxxxxxxxxxx
> *Subject:* [THIN] Troubleshooting Remote Access Problem
>
>
>
> Mornin' List.
>
>
>
> I'm having some trouble identifying why I can not connect to a server via
> RDP and thought I would bounce it off you all.
>
>
>
> Windows 2003 R2 SP2 server functions as connection broker in Quest
> vWorkspace farm.
>
> I applied patch 1c for vWorkspace 6, rebooted and could no longer access
> via RDP (I'm disinclined to blame this but it's the last change I know of)
>
>
>
> Troubleshooting steps taken:
>
> Verify Remote access is enabled
>
> Verify membership in Remote Admins group
>
> Verify Terminal Services (App mode) not installed
>
> Reset RDP listener
>
> Delete and Recreate RDP listener
>
> Apply Windows updates (server was very out of date on patches)
>
> Verify Windows firewall turned off
>
> Applied Patch 2 for vWorkspace 6
>
>
>
> No luck. This is message you receive when attempting to connect via RDP:
>
> Remote Desktop Disconnected
>
> The computer can't connect to the remote computer.
>
> Try connecting again. If the problem continues, contact the owner of the
> remote computer or your network administrator.
>
>
>
>
>
> Any ideas?
>
>
>
> Thanks,
>
> Christopher
>
>
> This message contains information which may be confidential and privileged.
> Unless you are the addressee (or authorized to receive for the addressee),
> you may not use, copy or disclose to anyone the message or any information
> contained in the message. If you have received the message in error, please
> advise the sender by reply e-mail, and delete or destroy the message. Thank
> you.
>
Other related posts:
