Hi,
I'm having problems setting up coldfusion 9, and I've narrowed it down to the web server configuration tool.
First, the server is running a brand new install of Windows 2008 R2 64bit. It's running IIS 7.5, and I've enabled ISAPI filters+extension, and IIS6 metabase compatibility.
The server is one of 1&1's new cloud offerings. I don't think this should be the problem, unless it's a way they've configured it.
I've already successfully installed CF9 on the same OS on a dedicated server with a different host.
Anyway, running the CF9 64 bit installer seems to work ok, but it doesn't configure up IIS. I've tried installing/uninstalling/re-imaging the server several times with no success.
To confirm my suspicions that CF was installing ok, I tried it using the built in web-server on port 8500, and that works fine.
I've tried running the web server configuration gui tool, but I get the following message:
Could not connect to any JRun/ColdFusion servers on host localhost.
Possible causes:
o Server not running
-Start Macromedia JRun4 or ColdFusion MX server
o Server running
-JNDI listen port in jndi.properties blocked by TCP/IP filtering or firewall on server
-host restriction in security.properties blocking communication with server
Googling this found several blog posts for earlier version of CF. Most suggest running the 'netstat -an' command, which gives:
Active Connections
Proto Local Address Foreign Address State
TCP 0.0.0.0:80 0.0.0.0:0 LISTENING
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1688 0.0.0.0:0 LISTENING
TCP 0.0.0.0:2522 0.0.0.0:0 LISTENING
TCP 0.0.0.0:2932 0.0.0.0:0 LISTENING
TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING
TCP 0.0.0.0:6085 0.0.0.0:0 LISTENING
TCP 0.0.0.0:6086 0.0.0.0:0 LISTENING
TCP 0.0.0.0:7997 0.0.0.0:0 LISTENING
TCP 0.0.0.0:8500 0.0.0.0:0 LISTENING
TCP 0.0.0.0:8983 0.0.0.0:0 LISTENING
TCP 0.0.0.0:9923 0.0.0.0:0 LISTENING
TCP 0.0.0.0:9953 0.0.0.0:0 LISTENING
TCP 0.0.0.0:9963 0.0.0.0:0 LISTENING
TCP 0.0.0.0:19999 0.0.0.0:0 LISTENING
TCP 0.0.0.0:20000 0.0.0.0:0 LISTENING
TCP 0.0.0.0:47001 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49152 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49153 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49154 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49155 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49156 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49201 0.0.0.0:0 LISTENING
TCP 127.0.0.1:8079 0.0.0.0:0 LISTENING
TCP 127.0.0.1:9953 127.0.0.1:49186 ESTABLISHED
TCP 127.0.0.1:49186 127.0.0.1:9953 ESTABLISHED
TCP 127.0.0.1:49538 127.0.0.1:9923 TIME_WAIT
TCP 127.0.0.1:49539 127.0.0.1:9963 TIME_WAIT
TCP 127.0.0.1:49540 127.0.0.1:9923 TIME_WAIT
TCP 127.0.0.1:49541 127.0.0.1:9963 TIME_WAIT
TCP 127.0.0.1:49542 127.0.0.1:9923 TIME_WAIT
TCP 127.0.0.1:49543 127.0.0.1:9963 TIME_WAIT
TCP 127.0.0.1:49544 127.0.0.1:9923 TIME_WAIT
TCP 127.0.0.1:49545 127.0.0.1:9963 TIME_WAIT
TCP [::]:80 [::]:0 LISTENING
TCP [::]:135 [::]:0 LISTENING
TCP [::]:445 [::]:0 LISTENING
TCP [::]:1688 [::]:0 LISTENING
TCP [::]:2522 [::]:0 LISTENING
TCP [::]:2932 [::]:0 LISTENING
TCP [::]:3389 [::]:0 LISTENING
TCP [::]:6085 [::]:0 LISTENING
TCP [::]:7997 [::]:0 LISTENING
TCP [::]:8500 [::]:0 LISTENING
TCP [::]:8983 [::]:0 LISTENING
TCP [::]:47001 [::]:0 LISTENING
TCP [::]:49152 [::]:0 LISTENING
TCP [::]:49153 [::]:0 LISTENING
TCP [::]:49154 [::]:0 LISTENING
TCP [::]:49155 [::]:0 LISTENING
TCP [::]:49156 [::]:0 LISTENING
TCP [::]:49201 [::]:0 LISTENING
UDP 0.0.0.0:500 *:*
UDP 0.0.0.0:4500 *:*
UDP 0.0.0.0:5355 *:*
UDP 0.0.0.0:62255 *:*
UDP 0.0.0.0:62257 *:*
UDP 0.0.0.0:62259 *:*
UDP 0.0.0.0:62261 *:*
UDP 127.0.0.1:62253 *:*
UDP 127.0.0.1:62254 *:*
UDP 127.0.0.1:62256 *:*
UDP 127.0.0.1:62258 *:*
UDP 127.0.0.1:62260 *:*
UDP 127.0.0.1:62262 *:*
UDP [::]:500 *:*
UDP [::]:4500 *:*
UDP [::]:5355 *:*
I've removed a few lines that mentioned the external IP of the server, but I don't think they're important.
The main thing, is that it seems to be listening on port 2932 which is configured in jndi.properties
At this point I'm stuck.
I did find some blog posts that suggested adding some arguments to narrow the ports scanned when you run the configuration tool. I tried them without success - as they were quite old, is it possible they have changed with the latest config tool?
The other thing I've contemplated is connecting IIS manually. However, I can't find any instructions for doing this with CF9.
Does anyone have any suggestions?
Thanks in advance,
Gareth