Not sure what changed, but I cannot get the Local, Internal (LAN) address to stick with the correct adapter (IP address).
The server running BI has multiple NICs and the configuration has not changed for years. This morning I noticed I could not access BI via the app or web browser. After some initial troubleshooting I narrowed it down to the incorrect adapter being selected:
The correct adapter (IP) is 172.16.1.65. When I change it to the correct adapter, it instantly reverts back to 172.16.1.209, which is a valid IP on the server and I can access the web server using that IP address at http://172.16.1.209:81. That's just not what I want, and it's not where my reverse proxy is pointing to. I've tried modifying the Bind exclusively setting and it will stick, but still not allow the changing of adapters. I've restarted the service and the computer. Nothing works. I still access the server through RDP at 172.16.1.65, so the interface is working correctly.
Any thoughts on why the BI setting won't stick? I'm on the current version 5.8.9.0 x64 (9/18/24) <- maybe this update is the issue?
Thanks!
*SOLVED - Web Server > LAN Adapter setting
*SOLVED - Web Server > LAN Adapter setting
Last edited by zfwjs on Fri Sep 20, 2024 4:14 pm, edited 1 time in total.
Re: Web Server > LAN Adapte on BI servers?r setting
Roll it back to the previous version and see if the problem is corrected.
edit: Maybe the 'Register IP address to assist...' is checked on the About page registration and is cached somewhere on BI servers?
edit: Maybe the 'Register IP address to assist...' is checked on the About page registration and is cached somewhere on BI servers?
Re: Web Server > LAN Adapter setting
Thanks for the response. This box was checked 'Register IP address to assist...'. I unchecked it, but if it's cached somewhere, that could be the issue with the latest version? After unchecking the box, I still couldn't get the adapter to stay changed.
I rolled back to the previous version, 5.9.7.4, and the setting now remains on the desired 172.16.1.65.
Thanks for the help!
I rolled back to the previous version, 5.9.7.4, and the setting now remains on the desired 172.16.1.65.
Thanks for the help!