If services are running , then please check if port 443 is bind to Horizon service or something else. You can run "netstat -ano|findstr 443"
Thanks for the reply. I don't see port 443 listening on connection server. All I get in output that remote IPs are using port 443 with session established with connection server on random port like 51504, 64841 etc.
Some of these connections are from antivirus software, so i stopped the antivirus, but no luck.
Thanks for the response. Here are the details:
1- Have only one connection server in setup
2- All services including 'Connection Server' service are running
3- OS is Windows 2019 server std.
4- I am not using load balancer. I am trying to open the admin console directly on connection server itself but its not working.
What version of Horizon?
Its Horizon 7.11
Yes, it doesn't show the port 443 listening at all.
I hope port 443 is not blocked in the environment.
In case if it is a new deployment , I would recommend you to take snapshot / backup of the Connection server and uninstall the Connection server ( DO NOT UNINSTALL ADAM DB from Connection server) and reinstall Connection server application pointing to same Adam DB.
Also would recommend the Windows Firewall enable and during reinstall of the Connection server application, it will re-configure the Windows Firewall.
You can also stop / disable Antivirus software.
If still same issue, it could be related to OS.
Just observed in the logs that there is issue with port 4001 and 443. I see below logs in horizon logs:
2020-07-27T11:32:51.420-04:00 WARN (0890-0A84) <localhost-startStop-1> [JMSUtil] Tracker JMS publisher & receiver taking a long time to start: 4998989 milliseconds so far
2020-07-27T11:32:54.356-04:00 WARN (1860-018C) <Thread-2> [bp] Item enqueued on "Outbound JMS Forwarder" but there are no workers available to process it. Busy workers = 0, queue length = 504
while generating the log bundle, I got below errors:
Testing message bus connection
Error when attempting to publish message, testing TCP port
Unable to connect to xyz.dom:4001 - CONNECT_REFUSED
Testing broker service
Failed to connect to broker xyz.dom:443 - CONNECT_REFUSED
There appears to be some issue with JMS component. Any suggestions apart from re-installing the Connection server role?
Thank you vBritinUSA and all the folks who provided their valuable inputs.
Here is what I did to resolve the issue:
1- I uninstalled the connection server by keeping the AD LDS instance intact.
2- Rebooted the server
3- Reinstalled the Connection server using the domain admin account having the admin access to the connection server.
4- Setup detected the existing LDS instance and selected it by default.
5- Completed the setup.
Boom.... the Horizon Admin console was up and accessible. It has all the configurations intact.
Thanks once again to all of you for your valuable inputs. Much Appreciated!!