Java Security Settings
Thread Starter
High Flying Bird
Joined: Dec 2000
Posts: 2,297
Likes: 0
From: Old Sarum ish
I've been trying to log in remotely to my departmental server... to no avail. It seems my Java Applet Security Settings are to blame. I've looked under 'Internet Options' customising, where there's something about 'Scription of Java Applets', but it doesn't seem to make any difference what is selected. Nor does having all my security settings set at 'low'.
I'm running Windows XP, IE 6.
Can anyone help?
I'm running Windows XP, IE 6.
Can anyone help?
Joined: Jan 2002
Posts: 156
Likes: 0
From: Sandwich, Kent, UK
Hi Aerbabe,
I wouldn't call myself an expert, but I have done a bit of Java programming, and I think you just can't fix this - and it's a feature, not a bug, as they say...
Java, and particularly applets, were designed with a very strong security model, to allay people's fears of Java viruses etc. Because of this, an applet is only allowed to commnuicate with the 'host' from which it was itself physically loaded, or possibly also with other hosts on the same network.
Therefore, if you have an applet stored locally on your machine, it might work fine when connected directly to your work intranet, but will correctly refuse to connect over the internet to the same machine, because that machine is now 'foreign' and potentially hostile (and of course the remote machine also doesn't want any old applet connecting to it, either).
Good luck though, I'm probably wrong, it's happened before...

cbl.
I wouldn't call myself an expert, but I have done a bit of Java programming, and I think you just can't fix this - and it's a feature, not a bug, as they say...
Java, and particularly applets, were designed with a very strong security model, to allay people's fears of Java viruses etc. Because of this, an applet is only allowed to commnuicate with the 'host' from which it was itself physically loaded, or possibly also with other hosts on the same network.
Therefore, if you have an applet stored locally on your machine, it might work fine when connected directly to your work intranet, but will correctly refuse to connect over the internet to the same machine, because that machine is now 'foreign' and potentially hostile (and of course the remote machine also doesn't want any old applet connecting to it, either).
Good luck though, I'm probably wrong, it's happened before...

cbl.




