Page cannot be displayed - No Web Dispatcher - Only ICM running

Question

Hi,
Our training system is a ‘SAP ERP Central Component 5.0’, on a WAS 6.40 platform. There is only the Central instance running with all processes available, including ICM. The Dispatcher is NOT configured. 
When entering following url, results in 'Page Cannot Displayed'error message:
===============================
http://<virtual-FQDN>:<port>/sap/bc/bsp/sap/hrrcf_start_int?sap-
client=230&BspClient=230&sap-
language=EN&BspLanguage=EN&rcfSpId=9001&rcfContext=MCC
<b>The 'Page cannot be displayed'error occurs FOR ALL SERVICES.</b> The above url was working before and as far as everyone here knows, there have been no changes.
The following url ping tests were SUCCESSFUL. These were typed directly into the Internet Explorer Address:
==================================================
http://<virtual-FQDN>:<port>//sap/bc/ping?sap-client=200
and
http://<virtual-FQDN>:<port>//sap/bc/ping?sap-client=230
and
http://<virtual-FQDN>:<port>//sap/bc/ping
However, performing the ping test from Tx SICF, results in an error.  For some reason, the url resolves to Physical-FQDN for teh hostname.  However, when changing hostname to the Virtual-FQDN, then Ping works.  (Not sure why the Physical-FQDN is not working)
Also testing the service ‘hrrcf_start_int’ from Tx SICF, results in the same ‘Page cannot be displayed’ error.  (Same for all services)
From Tx SE80, INTERNAL has been selected for Publishing.
Service has been activated. 
Have run program SIAC_PUBLISH_ALL_INTERNAL from Tx SE38.  Services has also been deactivated and activated from Tx SICF.  None of this has helped resolve the error. 
Some ICM parameters as follows:
icm/server_port_0     = PROT=HTTP,PORT=8012
icm/host_name_full    = <virtual-FQDN>
As mentioned before, the url was working some 2 weeks back, but for some reason is no longer working.
Regards,
Sanjay

Answer 1

Hi Dezso,
Thanks for your suggestion.
The issue is now being resolved.  The problem was as follows:
Previously the on-site Consultancy had configured one of the Transport Consolidation routes from DEV to TRN.  (This has now been reconfigured so that TRN as well as PRD are the TARGET routes from QA system.
However, previously ABAP Support Packages were applied to DEV & QA.  (& not to TRN).  Then a Developer transported the SPAU transport through the landscape and it obviously went to the TRN server.  (Transport was not imported into Production).
So TRN had no SPs applied, but the transport had been imported into TRN due to landscape setup.
Now the problem is due to an object that concerns authentication which was overwritten by the transport in TRN.  (Preventing user authentication).  We have a work around in that we can send the users directly through the ITS via a url, they can then authenticate and then they copy and paste the url they are using in the IE Address space.  After logging on, the IE session is still holding the session cookie, so no need to authenticate again after copying the url the user wants to use.  (I hope this makes sense?  No sure how better to describe this).
The longer term solution will be apply the SPs also to TRN and then apply the SPAU transport to TRN and it should then be fine.
Regards,
Sanjay