I have installed Crowd 2.2.2 on a test server (172.17.79.230) and restored to it the XML backup from my production server (10.74.47.118). The problem I'm having is that Crowd works perfectly when accessed from a browser on the local machine. I can authenticate via the URLs http://172.17.79.230:8095/crowd/console OR http://localhost/crowd:8095/console. What I can't do is access the Crowd server from any other machine. Requests simply time out. I have been assured by IT that port 8095 is open and is not being blocked by the network config.
I found a reference in CWD-2315 that imples that the problem lies with the cwd_application_address table still pointing to the production Crowd server (10.74.47.118).
The database on the test server shows the following:
mysql> select * from cwd_application_address where application_id = 3;
+------------------+--------------------------+-----------------------+---------------------+
| application_id | remote_address | remote_address_binary | remote_address_mask |
+------------------+--------------------------+-----------------------+---------------------+
| 3 | 10.74.47.118 | Ckovdg== | 0 |
| 3 | 127.0.0.1 | fwAAAQ== | 0 |
| 3 | localhost | NULL | 0 |
| 3 | usindtbx01d.corp.eng.com | NULL | 0 |
+------------------+--------------------------+-----------------------+---------------------+
If I read the above correctly, I should update the cwd_application_address table on with an entry for the test server:
mysql> insert into cwd_application_address values ("3","172.17.79.230","TBD TBD TBD","0");
I hesitate to start fooling with the database directly, but there's a certain amount of logic there. Has anyone else faced this problem and is this solution logical?
