Transmenu powered by JoomlArt.com - Mambo Joomla Professional Templates Club

Installed OpenKm on a Windows 2000 server yesterday, followed the tips regarding adding the "-b 0.0.0.0" parameter when starting run.bat. I can now access OpenKM using the ip address of the host computer, from the host computer.

I can however not connect to OpenKM from any other computer on the network nor via the internet. I have opened the 8080-FTP port on the router and forward any calls on this port to the OpenKM host PC.

Note that I also have Apache running on the same host PC, not sure if that has anything to do with it ?

Björn

It seems to be a network related issue. Perhaps is a firewall configuration. By the way, 8080 is not the FTP port.

Ooops, yes I meant 8080-TCP.

All other network related stuff seem to work fine (External desktop, FTP server, Webserver, file sharing). Do I need to set explicit permissions so the OpenKM directory is shared via windows shared folder ? That would seem a bit strange though...

Has anyone else tried using OpenKM on a Windows 2000 Server ?
Did it work "out of the box" ?
Are there any other tests I could do to locate the problem with the installation ?

Thanks,
Björn

EDIT: All of a sudden OpenKM is working, didn't change anything it just started working

JBoss listen at port 8080 by default, so (if you have started JBoss with the -b 0.0.0.0 option) you only have to open port 8080 if there is a firewall. If there is no firewall, port 8080 should be accesible from any machine in the network. Anyway, this is not an OpenKM related issue, is a JBoss related issue. I've tested JBoss + OpenKM in a Windows XP machine and there is no problem.

I flushed my iptables on linux and opened all connections by default on iptables, now I can access OpenKM only throug

http://localhost:8080/OpenKM

and not

http://192.168.1.15:8080/OpenKM

below are my iptables so you know what I'm talking

Code:

# iptables -L -n Chain INPUT (policy ACCEPT) target prot opt source destination ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 state RELATED,ESTABLISHED ACCEPT tcp -- 192.168.1.0/24 0.0.0.0/0 tcp dpt:8080 Chain FORWARD (policy DROP) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 state NEW,RELATED,ESTABLISHED Chain INBOUND (0 references) target prot opt source destination Chain LOG_FILTER (0 references) target prot opt source destination Chain LSI (0 references) target prot opt source destination Chain LSO (0 references) target prot opt source destination Chain OUTBOUND (0 references) target prot opt source destination

It might be a JBOSS problem but anyway it's OpenKM which starts it, maybe you could tell us how to pass some arguments at start to JBOSS (I looked in run.sh but couldn't find much)

You've tried to execute jboss with "run.sh "-b 0.0.0.0" or ""run.bat -b 0.0.0.0" on windows with it options binds service on all network interfaces.