Hi Mike,

When you say 'The error is also following profiles on that given computer.' can you describe in more detail what you mean by this?

If you say the user's profile works from your computer have you tried the reverse, logging in as you onto their computer and connecting to the same application?

In your config.xml file is the Internet Proxy enabled, if so try removing this if it is not required.

Thanks,

David

Anybody?

That is exactly what I mean by it is following profiles on that computer.  If I or anybody else logs into this given computer, and tries to run AppPortal they get the same error message.

Hmm, thought I had the proxy disabled (since we are not requiring it); however, it is currently set at   UseProxy=1

I'll see if that makes any difference.

I had changed the config.xml file to read  UseProxy=0

I had not had a chance to test things until today - After testing just a few minutes ago, that did NOT resole the issue.

Any other ideas?

Hi Mike,

We know remote access is enabled on the computer and we know the user has permissions to remote access to it,so it is likely network/name resolution related.

Earlier you said that you could connect via MSTSC, how did you specify the host was it by IP, FQDN or NetBIOS name?

Can you try using the NetBIOS or short name to either ping the host computer or use MSTSC,does this connect?

Are both client and host on the same network, or are you connecting via the Secue Gateway?

David

MSTSC via hostname (netbios)

When he is connecting in the office, he is on our wireless.  This is something I thought of too and then over ruled my thought since he also has the same issue when he tries to connect via our VPN (powers that be decided it would not be allowed over a gateway...use of VPN required).

Servers are one one network, VPN is on one network, and wireless is yet another network.

Nobody else is having any issues

Decided to try removing the configuration that comes from config.xml

Created the new configuration using IP address instead of netbios or fqdn.

Also made sure that proxy was set to NO

Same results - Still cannot connect

You say you are launching an app. Are you using vWorkspace or MS seamless? If MS Seamless are you getting the same problem for a published desktop to the same server?

Hi Mike,

We haven't gone down one route because you mention the Client has 8.0 version of AppPortal installed. Are you completely sure about that version ? If it is 7.6 there could be a very quick answer to why this isn't working.

Thanks, Andrew.