Trouble with MetaTagger Configuration Manager

We're running TS 6.7.1 plus MetaTagger 4.1.2 on Windows 2003 EE SP1, on VMWare.

I'm able to login into and use the MT Configuration Manager (http://localhost:9080/ciadmin/) from the TS/MT server itself, but not from my own computer. From my computer, I get "iwmtadminserver is not running" when I attempt to login. All mtserveletd_out.log shows is:

[JSP] login.jsp
----> username=admin

We've opened up the following firewall ports:

9090: MetaTagger Server Master Port
9095: MetaTagger Server Primary Port
9096: MetaTagger Studio Server Port
9080: MetaTagger Servlet Port

Any suggestions? Do we need to open all the ports above? Any others?

Thanks,

S.

Find more posts tagged with

Comments

Migrateduser

can you take a look at

/conf/admin.cfg

and see if the your VMWare host is correct. The reason being, if the TCP/IP port bind was on the localhost interface, it won't be visible outside the host.

nipper

We're running TS 6.7.1 plus MetaTagger 4.1.2 on Windows 2003 EE SP1, on VMWare.

I'm able to login into and use the MT Configuration Manager (http://localhost:9080/ciadmin/) from the TS/MT server itself, but not from my own computer. From my computer, I get "iwmtadminserver is not running" when I attempt to login. All mtserveletd_out.log shows is:

[JSP] login.jsp
----> username=admin

We've opened up the following firewall ports:

9090: MetaTagger Server Master Port
9095: MetaTagger Server Primary Port
9096: MetaTagger Studio Server Port
9080: MetaTagger Servlet Port

Any suggestions? Do we need to open all the ports above? Any others?

Thanks,

S.

This maybe a stupid question but i have to ask:

are you using http://localhost:9080/ciadmin from your main system or

http://vmwareservername:9080/ciadmin

The 1st will not work since the VMWare server is technically another box.

I am running MT 4.1.1 on VMware Win 2K so I will be happy to help try to debug it if you want to compare configs.

I just logged into ciadmin, so no issues there.

fiquebem

Thanks for your responses, Snkmoorthy and Nipper!

>and see if the your VMWare host is correct. The reason being, if the TCP/IP port bind was on the localhost interface, it won't be visible outside the host.

Excellent point! The Computer Name of the Windows 2003 EE SP1 server (running on VMWare) is TEAMSITE. It doesn't belong to any domain. The conf/admin.cfg file has teamsite. I manually changed this setting (in admin.cfg) from "teamsite" to "IP #1," but it was automatically changed back to teamsite when the MetaTagger Admin Server started.

Incidentally, what I see when I run ipconfig from a command prompt is IP #2. But IP #2 doesn't seem to work from the outside world. http://whatismyip.com shows IP #1.

So I continued to get the **** "iwmtadminserver is not running" when I tried to login to http://IP #1:9080/ciadmin/login.jsp from my machine. I finally mapped "teamsite" to "IP #1" in my C:\WINDOWS\system32\drivers\etc\hosts. Now I can get into http://teamsite/ciadmin/login.jsp from my machine.

Thanks very mucho, Snkmoorthy. You're da man!

S.

fiquebem

>I finally mapped "teamsite" to "IP #1" in my C:\WINDOWS\system32\drivers\etc\hosts. Now I can get into http://teamsite/ciadmin/login.jsp from my machine.

We're afraid to ask our users to update their drivers\etc\hosts files. What else can we do?

Thanks,

S.

Migrateduser

The ethernet interface of your VM is NAT'ed or Bridged? NAT won't work, because the VM cannot be seen outside your host OS.