TM1Web Error - Internal and External IP
Posted: Tue Mar 31, 2015 8:53 am
Hi there,
I've been struggling with this issue for a while now:
A client has installed TM1 10.2.1 for the first time and set up a new TM1 server recently before my arrival, intending to largely use TM1Web and Performance Modeler. The (non-TM1) server itself has two IP addresses; one internal and one external. The person before set up the TM1 server configured to the internal IP, which resulted in the server being unreachable in TM1Web.
I tried to reconfigure things to the external IP, changing the admin host in Architect, altering TM1Web.html, but leaving any xml files.
As it stands, TM1Web is now accessible from a separate local machine, yet it requires multiple inputs of the external IP since it keeps trying to redirect to the internal one.
On pmpsvc, the BI dispatch is the internal IP, and trying to change this results in an error. The CAM URI in tm1s.cfg is also set to the internal IP, yet changing this to the external also results in an error.
Am I missing something obvious? Is it perhaps something on their network side?
I've been struggling with this issue for a while now:
A client has installed TM1 10.2.1 for the first time and set up a new TM1 server recently before my arrival, intending to largely use TM1Web and Performance Modeler. The (non-TM1) server itself has two IP addresses; one internal and one external. The person before set up the TM1 server configured to the internal IP, which resulted in the server being unreachable in TM1Web.
I tried to reconfigure things to the external IP, changing the admin host in Architect, altering TM1Web.html, but leaving any xml files.
As it stands, TM1Web is now accessible from a separate local machine, yet it requires multiple inputs of the external IP since it keeps trying to redirect to the internal one.
On pmpsvc, the BI dispatch is the internal IP, and trying to change this results in an error. The CAM URI in tm1s.cfg is also set to the internal IP, yet changing this to the external also results in an error.
Am I missing something obvious? Is it perhaps something on their network side?