https://worldofeuc.com logo
Join Slack
Powered by
This message was deleted.
# _general
s
This message was deleted.
d
Well,,, only thing support would answer is, did you follow the loadbalancing best practice?
m
Yes, I followed it
d
did it work before? what has changed? nowadays, if you upgrade the only thing that breaks is de "sc sdset" stuff. If it never worked, it might be that your netscaler LB service group isn't configured as http but as tcp. links like https://www.davidwilkinson.co.uk/2017/03/09/load-balancing-appsense-management-and-personalization-servers-10-1-using-netscaler-11-x/ describe the correct setup.
In about 15hrs I'm at my customer where I can access all issues I ran into and will see if I have a 404 in my KB and share that info
👍 1
m
VIP with SourceIP persistence
SSL Offloading
s
can you bypass the loadbalancing and go directly to a specific server?
m
I have not try to create this key : BackConnectionHostNames (I don't want to use https://vip:7771 on the UWM server)
Yes, in the remote console it's OK with http://serverserver1:7771 but error 404 with https://vip:7771 If I enter https://vip:7771 in a browser it works
Customers looking to host the UWM consoles on the UWM servers and connect to the console using the load balanced virtual server will need to ensure loopback connection hostnames are specified for all Management and Personalization Servers. The following Microsoft knowledgebase article describes how to allow connections back to the same host: http://support.microsoft.com/kb/926642 Alternatively, the consoles may be installed on remote machines and console connections made directly into the respective servers.
"Into the respective servers" so it's not possible by design to connect to https://vip:7771 with remote console
3 Views
Open in Slack
PreviousNext
Powered by