Can't connect to Remote Instance

[aking]

Hey guys,

Having an issue that's fairly new to me and I was hoping someone here might have some pointers.

We setup a new TM1 Instance on one of our Server. Fired up Architect on the server, Connect, Everything is fine. However, whenever anyone attempts to connect to the server from a remote machine, the cursor just spins for a while then cancels. No error message, no prompt, nothing.

The instance is set to Security 1, so it's not an issue with Cam connection. I've seen in other threads that the Firewall needs to be configured, which it has (We have another server we aren't having the issue with, I basically exported and imported the settings). I've also see a solution of setting the Instance's IPAddress=T in the config. No good.

All Instances are 10.2.2 FP4
All Servers are Win8

At this point I'm considering installing Wireshark, though I think packet sniffing on IT's corporate network would be frowned upon.

Any thoughts you have would be appreciated. Spent a little while banging my head against this yesterday and it looks like today will be the same.

Thanks.

[Edward Stuart]

I assume you can ping the server from the local machine?

Plus it's always worth checking the tm1.ini file on the local machine to check the adminhost isn't going awry

[tomok]

Check the tm1s.cfg file for both servers and make sure the PortNumber setting is different for each.

[aking]

I assume you can ping the server from the local machine?

I can ping the Server, and even telnet into the Admin SSL port, but can't telnet to the port we have the server linked to. I found I was also able to telnet to the port on the Affected Server that we use for the Instance on the Unaffected Server, so I tried restarting the Affected Instance on that port, but no dice.

Plus it's always worth checking the tm1.ini file on the local machine to check the adminhost isn't going awry

I know there is a tm1p.ini file, but isn't that primarily for the web end of things? Where can I find the file? Are you talking about the one that is on my Local Machine, or the Affected Server?

Check the tm1s.cfg file for both servers and make sure the PortNumber setting is different for each.

That should only matter if they're on the same Server, shouldn't it? I may not have explained the architecture well enough. The two Instances have their own Servers, but those Server should be setup identically, more or less.

One more thing to note, when I was bouncing the Affected Instance, I saw it was still in my Server Explorer (Perfectly normal if you haven't refreshed). However, when I double-clicked on the Instance name, it spun like it did before. It didn't give me the "This server is not responding" dialog.

[macsir]

Check your sever to see if you have two IP addresses enabled. Disable one network should be OK for tm1.

[Edward Stuart]

https://www-01.ibm.com/support/knowledg ... 51823.html

Always worth checking fully qualified domain names too.

Assume you are connecting from a client which can connect to other instances.

Does the adminhost on the client machine list all TM1 servers? If so check just the affected server. If a non existent server is listed TM1 can hang whilst it tries to resolve the connection