UNSOLVED

ashad1

updated

15 years ago

A

ashad1

31 Posts

0

3251

April 28th, 2011 10:00

Cannot connect to published Desktop

Hi community,

i have a problem with the connection from the web acces / app portal to connect to a published desktop (parallels container).

after starting the desktop vworkspace client try to connect to the container but fails.

i have cheked the license, its fine.

firewall is off.

network is ok.

enviroment:

vWorkspace 7.2

Container Running W2k8 R2 x64

is there any solution about this ??

please let me know...

regards,

attiq

  • 947

    0

    Posted April 28th, 2011 13:00

    What is the "Logon State" status of the container in the desktop group?

  • ashad1

    31 Posts

    947

    0

    Posted April 28th, 2011 14:00

    Normal Logon State is "Logged Off"

    While connecting, it turns to "Logged On"

  • ashad1

    31 Posts

    947

    0

    Posted April 28th, 2011 14:00

    we dont user secure-it.

    its a simple message like "ask your administrator"

    i have attached it!

    regards

  • 947

    0

    Posted April 28th, 2011 14:00

    Are you also connecting through Secure-IT ?

    What is the error message you receive when trying to connect ?

  • vtscott1

    19 Posts

    947

    0

    Posted April 29th, 2011 11:00

    Has remote desktop been turned on in the target machine? Try connecting directly with an RDP client.

  • ashad1

    31 Posts

    947

    0

    Posted April 29th, 2011 11:00

    yes rdp is turned on.

    directly connection to the container works fine.

  • 947

    0

    Posted April 29th, 2011 12:00

    Hello Attiq,

    A few questions on this issue

    1. Has this issue just started occurring or is this a new environment/allways occurred?
      1. If issue just started occurring, what has changed?
    2. What version of PNTools do you have installed on your Parallels Container?

    Thanks,

    Roman

  • ashad1

    31 Posts

    947

    0

    Posted April 29th, 2011 14:00

    hi,

    the issue is gone.

    our network guy made some misconfiguration in security-config of the VLAN in the ASA

    thanks anyway guys for your help.

    regards,

    as