VMware Workspace ONE Community
danielmgrinnell
Enthusiast
Enthusiast

Getting Error "this horizon server expects to get your logon creds from another app server

I am getting this error does anyone know whats causing this ?

idm.PNG

Thanks

28 Replies
BarryK4308
Contributor
Contributor

Anyone else seen this issue and have a fix? We're seeing the same message the moment we attach ID to HV, everything looks good apart from the moment you go to connect.

0 Kudos
ElJefe61
Enthusiast
Enthusiast

Has anyone figured this out yet?  I am experiencing the error on a brand new Identity Mgr. 3.2.0.1 build.  Any insight would be greatly appreciated.

0 Kudos
MarkusHartmann
Contributor
Contributor

Hi there,

any update on this? Facing the same issue today.

Currently rolling out a Workspace One Deployment (SaaS) with OnPremise Horizon View.

greetings Markus

0 Kudos
talavital
Contributor
Contributor

Same issue.

Vidm is saas. Horizon is on premise.

any update ?

0 Kudos
Matrix__1970
Enthusiast
Enthusiast

Ok for me!!!!! Thank you!!!!

Matrix

0 Kudos
Matrix__1970
Enthusiast
Enthusiast

Ok for me!!!!! Thank you!!!!

Matrix

0 Kudos
mverschooten
Contributor
Contributor

MarkusHartmann​: You have to point the connection servers time source to the same source as the saas tenant. (in the case of EMEA region to 193.1.31.66).

For all the others, point the connection server to the same timesource as the idm appliance. In the appliance you might need to edit /etc/ntp.conf file.

0 Kudos
tbada
Contributor
Contributor

Same issue however i restarted the connection servers and changed the default launch to web....this fixed the issue

initially i launched with Horizon 7 client

0 Kudos
mshellenberger
Contributor
Contributor

In case this is helpful to anyone else... I had the same error message when my connection server information in my virtual apps collection was not set the the FQDN of the server and active directory (i.e. HR01.internalADDomain.internal). I was puzzled then how I get my external clients to connect since that's not a routable domain outside the LAN. Turns out I was missing the network mappings configuration where you can override the URL to use based on client IP. (In my case I wanted all clients to route through the external domain name. Here's some screenshots of where to do that in the virtual app config:

pastedImage_0.png

pastedImage_1.png