How do I get admin console response out of new install?

Help

I've just done a fresh install of AMS5.01 on vanilla Centos 6.3, which seemed to install correctly using the default settings (1935,80 for ams, 1111 for admin).

/var/logs/messages states everything is working correctly (machine has two NICs, using 192.168.0.4 and 192.168.0.84). Within Centos putty winow I can restart the server with no error messages.

However, I cant seem to get a response other than a ping from AMS itself from another machine. I can't bring up http://192.168.0.4 in another browser on the same subnet. Internally, there are no firewalls blocking connection. I've tried 192.168.0.4:1111 and 192.168.0.4:80 with no response.

Nov 13 11:36:33 dl160-2 Service[14225]: Server starting...

Nov 13 11:36:34 dl160-2 Server[14225]: /opt/adobe/ams/Apache2.2/bin/httpd -f ./conf/httpd.conf -d "/opt/adobe/ams/Apache2.2" -k start returned 0: [Tue Nov 13 11:36:33 2012] [info] mod_jithttp - AMS installation path: "/opt/adobe/ams/"#012httpd: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for ServerName

Nov 13 11:36:34 dl160-2 Server[14225]: /opt/adobe/ams/Apache2.2/bin/htcacheclean -n -t -i -p/opt/adobe/ams/Apache2.2/cacheroot -d5 -l1024K returned 0:

Nov 13 11:36:34 dl160-2 Service[14225]: Server started (/opt/adobe/ams/conf/Server.xml).

Nov 13 11:36:34 dl160-2 Adaptor[14251]: Listener started ( _defaultRoot__edge1 ) : localhost:19350/v4

Nov 13 11:36:35 dl160-2 Adaptor[14251]: Listener started ( _defaultRoot__edge1 ) : 80/v4

Nov 13 11:36:35 dl160-2 Adaptor[14251]: Listener started ( _defaultRoot__edge1 ) : 1935/v4

Nov 13 11:36:36 dl160-2 Adaptor[14251]: Listener started ( _defaultRoot__edge1 ) : 127.0.0.1:19350 (rtmfp-core)/v4

Nov 13 11:36:36 dl160-2 Adaptor[14251]: Listener started ( _defaultRoot__edge1 ) : 192.168.0.4:19350 (rtmfp-core)/v4

Nov 13 11:36:36 dl160-2 Adaptor[14251]: Listener started ( _defaultRoot__edge1 ) : 192.168.0.84:19350 (rtmfp-core)/v4

Nov 13 11:36:36 dl160-2 Adaptor[14251]: Public rtmfp-core addresses for listener _defaultRoot__edge1 are: 127.0.0.1:19350;192.168.0.4:19350;192.168.0.84:19350

Nov 13 11:36:36 dl160-2 Adaptor[14251]: Listener started ( _defaultRoot__edge1 ) : 127.0.0.1:1935 (rtmfp)/v4

Nov 13 11:36:36 dl160-2 Adaptor[14251]: Listener started ( _defaultRoot__edge1 ) : 192.168.0.4:1935 (rtmfp)/v4

Nov 13 11:36:36 dl160-2 Adaptor[14251]: Listener started ( _defaultRoot__edge1 ) : 192.168.0.84:1935 (rtmfp)/v4

Nov 13 11:36:36 dl160-2 Adaptor[14251]: Listener started ( _defaultRoot__edge1 ) : 127.0.0.1:80 (rtmfp)/v4

Nov 13 11:36:36 dl160-2 Adaptor[14251]: Listener started ( _defaultRoot__edge1 ) : 192.168.0.4:80 (rtmfp)/v4

Nov 13 11:36:36 dl160-2 Adaptor[14251]: Listener started ( _defaultRoot__edge1 ) : 192.168.0.84:80 (rtmfp)/v4

Nov 13 11:36:38 dl160-2 Service[14666]: Server starting...

Nov 13 11:36:38 dl160-2 Adaptor[14666]: Listener started ( FCSAdminIpcProtocol ) : localhost:11110/v4

Nov 13 11:36:39 dl160-2 Adaptor[14666]: Listener started ( FCSAdminAdaptor ) : 1111/v4

Nov 13 11:36:40 dl160-2 Service[14666]: Server started (./conf/Server.xml).

Can this be an AMS thing, or a local connectivity thing? From the machine I am testing from (192.168.0.11), I can ping, tracert and ssh onto the AMS server, but cant bring up the admin console in a browser window