josefdi's Posts

Hi my environment is a 3 node VIDM 2.8 cluster, all of a sudden the VIDM portal doesnt come up. i get the 404 page not found error. Tries the below steps but still no luck 1. verified rabbi... See more...
Hi my environment is a 3 node VIDM 2.8 cluster, all of a sudden the VIDM portal doesnt come up. i get the 404 page not found error. Tries the below steps but still no luck 1. verified rabbitmqctl cluster_status.... all the nodes are listed and running on all three appliances 2. updated the updateiptables.hzn & rebooted the appliances as per kb 2149675 3. able to connect to the sql databse. Any pointers to check please?  tks
Hi guys We had a working VIDM environment till yesterday, We had a power failure in one of the DC's and all the VIDM VM's were down. When the Datacenter was online, the VIDM portal was down an... See more...
Hi guys We had a working VIDM environment till yesterday, We had a power failure in one of the DC's and all the VIDM VM's were down. When the Datacenter was online, the VIDM portal was down and rabbit cluster was not working. get the below message when ran - rabbitmqctl cluster_status attempted to contact: [rabbitmq@node3] rabbitmq@node3:   * connected to epmd (port 4369) on node3   * epmd reports: node 'rabbitmq' not running at all                   no other nodes on node3   * suggestion: start the node3 tried restarting all the 3 nodes , but still the rabbit cluster is not coming online. Alsoe tried the below steps, but no gain 1.  Verify that ports 4369, 5700, and 25672 are open. a.  To open ports, run the following command: touch /usr/local/horizon/conf/flags/enable.rabbitmq b.  Run the following script: /usr/local/horizon/scripts/updateiptables.hzn 2.  Restart RabbitMQ: a.  Kill existing RabbitMQ processes, if any. rabbitmqctl stop rabbitmq-server –detached b.  You might also need to restart the VMware Identity Manager service if RabbitMQ does not come up gracefully: service horizon-workspace restart Pl anyone faced similar issues when all the VM's are down all at once .. Tks
Always On group was created on SQLserverA and it was the primary till the failover, so it works only when the availability group is primary on SQLServerA and VIDM portal doesnt come up if the ava... See more...
Always On group was created on SQLserverA and it was the primary till the failover, so it works only when the availability group is primary on SQLServerA and VIDM portal doesnt come up if the availability group fails over to other replicas. Has anyone faced similar issues.
Hi I am testing a manual Failover of the Always On VIDM SaaS database. My environment is VIDM 2.8 in multisubnet. SQl servers are SQL2014 in an Always ON CLuster. SQLserverA and SQlServ... See more...
Hi I am testing a manual Failover of the Always On VIDM SaaS database. My environment is VIDM 2.8 in multisubnet. SQl servers are SQL2014 in an Always ON CLuster. SQLserverA and SQlServerB and in one subnet and SQLServerC and SQLServerD are in another Subnet. My issue is When the availability group has its primary on SQLServerA, my VIDM portal works fine, but when triggered a manual failover to SQLserverC, the VIDM portal appears only partially. There are no errors reported during the manual failover. I have 2 listeners configured one for each subnet. Are there any pointers to where i need to check ? Thanks
I am encountering a strange issue.. Whenever i reboot the access point 2.8 , i am not able to login to the admin page..The admin page doesnt connect. So if i delete the VM and then re deploy usi... See more...
I am encountering a strange issue.. Whenever i reboot the access point 2.8 , i am not able to login to the admin page..The admin page doesnt connect. So if i delete the VM and then re deploy using the powershell script, i am able to login to the admin page, but if i reboot the AP i am unable to see admin page.. Any ideas?  Thanks.
It is working now. I just removed all and created new ranges as you showed.. first for the default and then the internal. I did have the same setting earlier but in wrong order. Thanks.
My config  looks the same... except that I edited the default and changed it to reflect only the internal range ( 10.0.0.1 to 10.255.255.254) .. I then created another range for external & includ... See more...
My config  looks the same... except that I edited the default and changed it to reflect only the internal range ( 10.0.0.1 to 10.255.255.254) .. I then created another range for external & included relevant policies.. i will now remove everything and create the default for external and one for internal.. Will update. Tks
external  works only if I use the default range 0.0.0.0 to 255.255.255.255 and point it to the access point URL which is accessible from internet, but it breaks the internal acess. internal on... See more...
external  works only if I use the default range 0.0.0.0 to 255.255.255.255 and point it to the access point URL which is accessible from internet, but it breaks the internal acess. internal only works if pointed to the connection server URL. I did did go through the reports and added a couple of networks other than the 10.0.0.0 subnet , but still no joy externally
My environment consists of VIDM 2.8 and access points. Internal connections works fine if i specify the view connection server fqdn as client URL in the network range..but external connection fai... See more...
My environment consists of VIDM 2.8 and access points. Internal connections works fine if i specify the view connection server fqdn as client URL in the network range..but external connection fail with unable to resolve hostname ( understandable as it cannot resolve the internal connection server from the internet). External connections goes through if i specify the access point as the client URL. My issue is how to segregate the external network range .What should be the external IP range .. My internal range is 10.0.01 to 10.255.255.254.. I tried different options, but couldn make it work. Any pointers please.
Thanks Mark. It works after i changed the external URL's to point to the access point as you mentioned. I have specified  my internal network range as 10.0.0.1 - 10.255.255.254 in VIDM & point... See more...
Thanks Mark. It works after i changed the external URL's to point to the access point as you mentioned. I have specified  my internal network range as 10.0.0.1 - 10.255.255.254 in VIDM & pointed to the view server fqdn as client URL. My external setting works if point to the access point as client URL, but how i specify the external IP range ie all the IP range except 10.0.0.1 - 10.255.255.254, Thanks again for your help.!!
Hi Mark...I followed the instructions having both the horizon and web proxy sections included.still getting the error 1. Internally i am able to connect to the vIDM portal - https://view.domain.... See more...
Hi Mark...I followed the instructions having both the horizon and web proxy sections included.still getting the error 1. Internally i am able to connect to the vIDM portal - https://view.domain.com 2.Able to to launch apps and desktops. No issues Externally , connections goes through the AP and vIDM, see attached the ini file 1. Able to connect to portal https://view.domain.com 2. Apps are listed, but getting the error - Horizon Client: Couldnt resolve hostaname. Tried changing the view client URL to IP address of the connection server in vIDM network range , this time the connection timoes out when launching the application. \Tks
i assume .. to do that i need to reconfigure the access point to point to connection server & remove the reverse proxy.. I will do that and update. In the mean time, could you please tell me if t... See more...
i assume .. to do that i need to reconfigure the access point to point to connection server & remove the reverse proxy.. I will do that and update. In the mean time, could you please tell me if the default https and blast gateway settings should be ticked or unticked in the connection server settings..Thanks.
Hi Guys I get the below error when accessing externally ie from internet. Environment consist of access points, VIDM and Horizon servers. I am able to access and login to the VIDM portal and see... See more...
Hi Guys I get the below error when accessing externally ie from internet. Environment consist of access points, VIDM and Horizon servers. I am able to access and login to the VIDM portal and see the icons, but get the error when trying to launch the application. VMware Horizon Client: Error couldnt resolve hostname I am not getting any error when accesssed through internal networks to the same VIDM portal. The connection server gateway settings are ticked (enabled) currently, if i untick them my internal connection breaks and i get error 404 error. Are there any thoughts ?
Hi... Did you manage to resolve ? .. getting the below error when trying to launch the application. No errors on SAML authentication in Horizon. The vIDM appliances are load balanced through F5. ... See more...
Hi... Did you manage to resolve ? .. getting the below error when trying to launch the application. No errors on SAML authentication in Horizon. The vIDM appliances are load balanced through F5. Any pointers please.
Hi I am also getting the same error when launching the application from vDIM portal.. Did you manage to resolve this.. Thanks.
and now i get the below error when accessing the portal..
Hi I am getting the below error after i added another appliance to the existing cluster.. You do not have permission to access this page: /hc/1/authenticate/ Pl anyone have any pointers.... See more...
Hi I am getting the below error after i added another appliance to the existing cluster.. You do not have permission to access this page: /hc/1/authenticate/ Pl anyone have any pointers.. Thanks.
Thanks .. I have gone through the link.. am able to ping, DNS entries are corrrect , able to forward and reverse lookup the fqdn and IP..Able to connect to the FQDN but getting the SSL timeout.... See more...
Thanks .. I have gone through the link.. am able to ping, DNS entries are corrrect , able to forward and reverse lookup the fqdn and IP..Able to connect to the FQDN but getting the SSL timeout..as shown below when i runt the curl command curl -v -3 -ssl https://my.fqdn.com * About to connect() to https:// myfqdn.com port 443 (#0) *   Trying 10..X.X.X connected * Connected to XXXXXXXX) port 443 (#0) * successfully set certificate verify locations: *   CAfile: none   CApath: /etc/ssl/certs/ * SSLv3, TLS handshake, Client hello (1): * SSL connection timeout * Closing connection #0
Hi I am getting the error " Invalid Identity Manager url, unable to find valid certificate to " when it ry to install the load balanced FQDN URL.. I had installed the root CA certificate...bu... See more...
Hi I am getting the error " Invalid Identity Manager url, unable to find valid certificate to " when it ry to install the load balanced FQDN URL.. I had installed the root CA certificate...but When i try to connect using curl, get the below response..any pointers please error:14094410:SSL routines:SSL3_READ_BYTES:sslv3 alert handshake failure * About to connect() to  port 443 (#0) *   Trying .. connected * Connected to port 443 (#0) * successfully set certificate verify locations: *   CAfile: none   CApath: /etc/ssl/certs/ * SSLv3, TLS handshake, Client hello (1): * SSLv3, TLS alert, Server hello (2): * error:14094410:SSL routines:SSL3_READ_BYTES:sslv3 alert handshake failure * Closing connection #0
I am getting the below error when i changed the password  auth adapter port to 389 from 3268. I have not enabled kereberos.. does it needs to be enabled  & any other settings that needs changing ... See more...
I am getting the below error when i changed the password  auth adapter port to 389 from 3268. I have not enabled kereberos.. does it needs to be enabled  & any other settings that needs changing ?