Applets & RMI - How Straightforward

Question

I recently developed an application to run over the corporate Intranet using an Applet on the the client side and Servlets on the server to do the database querying. Everything works fine but I cannot deploy the solution as the server runs IIS and I canot get the administrator to set up a servlet container.
Thus, I thought I would switch to using RMI on the server. I'm new to RMI and have been trying to get the basic communication between the Applet and a remote object working in order to test the feasability of this solution. I can run it okay on the local machine with both Applet Viewer and IE5.0, however, when I try to run the Applet from another machine I get the following error.
java.security.AccessControlException: access denied (java.net.SocketPermission 127.0.0.1:1099 connect,resolve)
The Applet is trying to connect to the same machine from which it was downloaded and thus, I believe, there should not be any need to mess around with the policy files as seems to be suggested by mnay replies to other posts relating to this error.
I am confused by the fact that the exception indicates the client loopback address - 127.0.0.1:1099 - which suggests to me that the problem possibly lies elsewhere???
A println of the String ipadd below indicates the correct host - 13.22.2.41/QueryServer
String ipadd = getCodeBase().getHost() + "/QueryServer";
try
DatabaseQuery dq = (DatabaseQuery)Naming.lookup(ipadd);
Vector v = dq.performDatabaseQuery("SOME_QUERY");
}In the main() of my remote object I Have:
try
RemoteQuery rq = new RemoteQuery();
String serverObjectName = "//13.22.2.41/QueryServer";
Naming.rebind(serverObjectName, rq);
System.out.println("Server Running.....");
}After compiling the classes. I do start rmiregistry followed by rmic RemoteQuery followed by java RemoteQuery . As stated above, everything works perfectly on the local machine.
Any ideas anyone.
No dukes awarded for suggestions involving policy files!!

Answer 1

Given that the loopback address is quoted in the Exception Message, it seems to me that possibly my Applet is "missing something" and the applet's lookup attempt is defaulting to the client (hence the exception as the Applet cannot of course access the local system) rather than the server.