Issues with external access to web daemon

All,

I'm running TS 7.1 on Windows 2008 which in turn runs on a VMWare.

Installation basically worked ok and locally everything works fine. However, if I want to call the TS UI from a remote client, it is not working. I cannot access port 80 or better said nobody seems to listen. Port 9080 (JBoss) and port 81 (a separate Apache that I use for preview) are working fine.

When I do a netstat -oa I see this confirmed:

Active Connections

Proto Local Address Foreign Address State PID
TCP 0.0.0.0:81 WIN-6FQ74S4Q0N6:0 LISTENING 260
TCP 0.0.0.0:135 WIN-6FQ74S4Q0N6:0 LISTENING 920
TCP 0.0.0.0:445 WIN-6FQ74S4Q0N6:0 LISTENING 4
TCP 0.0.0.0:1025 WIN-6FQ74S4Q0N6:0 LISTENING 588
TCP 0.0.0.0:1026 WIN-6FQ74S4Q0N6:0 LISTENING 956
TCP 0.0.0.0:1027 WIN-6FQ74S4Q0N6:0 LISTENING 1076
TCP 0.0.0.0:1028 WIN-6FQ74S4Q0N6:0 LISTENING 680
TCP 0.0.0.0:1053 WIN-6FQ74S4Q0N6:0 LISTENING 1636
TCP 0.0.0.0:1054 WIN-6FQ74S4Q0N6:0 LISTENING 1636
TCP 0.0.0.0:1055 WIN-6FQ74S4Q0N6:0 LISTENING 1636
TCP 0.0.0.0:1080 WIN-6FQ74S4Q0N6:0 LISTENING 1800
TCP 0.0.0.0:1084 WIN-6FQ74S4Q0N6:0 LISTENING 208
TCP 0.0.0.0:1096 WIN-6FQ74S4Q0N6:0 LISTENING 668
TCP 0.0.0.0:1098 WIN-6FQ74S4Q0N6:0 LISTENING 1636
TCP 0.0.0.0:1099 WIN-6FQ74S4Q0N6:0 LISTENING 1636
TCP 0.0.0.0:1433 WIN-6FQ74S4Q0N6:0 LISTENING 2396
TCP 0.0.0.0:3873 WIN-6FQ74S4Q0N6:0 LISTENING 1636
TCP 0.0.0.0:4444 WIN-6FQ74S4Q0N6:0 LISTENING 1636
TCP 0.0.0.0:4445 WIN-6FQ74S4Q0N6:0 LISTENING 1636
TCP 0.0.0.0:4446 WIN-6FQ74S4Q0N6:0 LISTENING 1636
TCP 0.0.0.0:5357 WIN-6FQ74S4Q0N6:0 LISTENING 4
TCP 0.0.0.0:6688 WIN-6FQ74S4Q0N6:0 LISTENING 288
TCP 0.0.0.0:6689 WIN-6FQ74S4Q0N6:0 LISTENING 288
TCP 0.0.0.0:8009 WIN-6FQ74S4Q0N6:0 LISTENING 2028
TCP 0.0.0.0:8080 WIN-6FQ74S4Q0N6:0 LISTENING 2028
TCP 0.0.0.0:8081 WIN-6FQ74S4Q0N6:0 LISTENING 1736
TCP 0.0.0.0:8083 WIN-6FQ74S4Q0N6:0 LISTENING 1636
TCP 0.0.0.0:8088 WIN-6FQ74S4Q0N6:0 LISTENING 1736
TCP 0.0.0.0:8898 WIN-6FQ74S4Q0N6:0 LISTENING 2036
TCP 0.0.0.0:8899 WIN-6FQ74S4Q0N6:0 LISTENING 2036
TCP 0.0.0.0:9080 WIN-6FQ74S4Q0N6:0 LISTENING 1636
TCP 0.0.0.0:12973 WIN-6FQ74S4Q0N6:0 LISTENING 1612
...
...

It seems that the configuration in C:\Interwoven\TeamSite\iw-webd\conf\httpd.conf has no influence at all. When I change

Listen 80

to an arbitrary port and do a iwreset -ui or just restart the web daemon service, I still can access the TS UI locally via port 80.
By the way accessing TS via port 8080 works fine as well.

So where else is actually defined that the web daemon is listening to port 80 and what do I have to do else to make it accessible from other computers? Might this be also a Windows issue?

The iwwebd part in iw.cfg looks like this:
[iwwebd]
default_protocol=http
http_port=80
https_port=443
host=the DNS name of the server

Maybe I'm totally missing an obvious thing, but...

Regards,
Christian

Find more posts tagged with

Comments

curiousmaverick

In most probability it is a firewall issue.

I too encounterd a similar problem and got it resolved by our network team.

cblumen

I edited my original post and added the config from iw.cfg. Actually there you can change the port. But changing the port does not help when its not accessible from external.

What I also forgot to mention: in the results of netstat, I get an antry for port 80, but it is

TCP [::]:80 WIN-6FQ74S4Q0N6:0 LISTENING 4588

What does [::] mean here?

html_table.rptdesign

curiousmaverick

You need to check which process PID 4588 refers to. You can easily do that from Task Manager.

cblumen

Problem solved!

In C:\Interwoven\TeamSite\iw-webd\conf\iwwebd.conf

it is not sufficient to just have

Listen 80

but you have to have

Listen the_ip-address:80

cblumen

One more update to this.

You have to actually edit
C:\Interwoven\TeamSite\iw-webd\conf\iwwebd.conf.template

as
C:\Interwoven\TeamSite\iw-webd\conf\iwwebd.conf gets recreated after a toolkit rebuild and your changes would be lost.

So in C:\Interwoven\TeamSite\iw-webd\conf\iwwebd.conf.template write

Listen your_ip_addresslithium_IWWEBD_HTTP_PORT__

jasonmcneil

Just wanted to post that this worked for me, thanks!

swathi

Hi, i tried in the same way. i have added my server Ip address and still i was not able to access the teamsite UI http://ipaddress from my desktop. teamsite Ui is opening only in the server.
did it worked for any one?

Migrateduser

This also worked for me and I am running VMWare with TS 7.2.1 on Windows 2008 R2 64bit.

cblumen,
Thanks for posting the solution. Smiley Happy

mart2001

Thanks!! I had the same issue and putting this in worked for me.
When I try to put in hostname, it did not work. So I had to use ip address in order to make it work.

John742

Did everyone with this problem have multiple ip addresses on the server? I also have the same issue but appeared to be apaching flaking on the binding when it saw multiple ip's. Normally it should bind to all ip's if you do not specify one.

Migrateduser_427

I know this is a bit old, however we also encountered this issue and want to share further on this as was provided below from IW Support:

----------------------------------------------------------------

"...this issue is related to a configuration problem with IPv6 on the server. The web daemon is attempting to take connections on IPv6, rather than IPv4. Follow the below steps to resolve this issue:
- Open the file \iwwebd\conf\iwwebd.conf.template.
- Look for this section:
#
Listen __IWWEBD_HTTP_PORT__
Listen __IWWEBD_HTTPS_PORT__
#

Change it to:
#
Listen 0.0.0.0lithium_IWWEBD_HTTP_PORT__
Listen 0.0.0.0lithium_IWWEBD_HTTPS_PORT__
#
- Run the command: iwreset -ui

On Windows 2008, the command prompt must be run as administrator or the iwreset command will not work. This will force the web daemon to listen only on IPv4 addresses and should resolve your issue.
..."

---------------------------------------------------------------

After the iwrest, you should notice that the file "\iwwebd\conf\iwwebd.conf" gets updated to reflect this change as well.

This worked in our TS 6.7.2SP2 WIN 2008 server set-up.