Sun java and client.class

[llupin]

If I install the Sun java plug-in on Windows XP I am unable to use the Wingate java authentication. The plug-in reports that it can't find Client.class (see below). Can any one tell me what I am doing wrong?

Java(TM) Plug-in: Version 1.4.2_05
Using JRE version 1.4.2_05 Java HotSpot(TM) Client VM
User home directory = C:\Documents and Settings\llupin

Proxy Configuration: Manual Configuration
Proxy: http=10.1.0.3:8010,https=10.1.0.3:8010,socks=10.1.0.3:1080
Proxy Overrides: 10.1.0.3:8010,10.1.0.3:1080,<local>

----------------------------------------------------
c: clear console window
f: finalize objects on finalization queue
g: garbage collect
h: display this help message
l: dump classloader list
m: print memory usage
o: trigger logging
p: reload proxy configuration
q: hide console
r: reload policy configuration
s: dump system properties
t: dump thread list
v: dump thread stack
x: clear classloader cache
0-5: set trace level to <n>
----------------------------------------------------
load: class Client.class not found.

java.lang.ClassNotFoundException: Client.class

at sun.applet.AppletClassLoader.findClass(Unknown Source)

at java.lang.ClassLoader.loadClass(Unknown Source)

at sun.applet.AppletClassLoader.loadClass(Unknown Source)

at java.lang.ClassLoader.loadClass(Unknown Source)

at sun.applet.AppletClassLoader.loadCode(Unknown Source)

at sun.applet.AppletPanel.createApplet(Unknown Source)

at sun.plugin.AppletViewer.createApplet(Unknown Source)

at sun.applet.AppletPanel.runLoader(Unknown Source)

at sun.applet.AppletPanel.run(Unknown Source)

at java.lang.Thread.run(Unknown Source)

Caused by: java.net.SocketException: Connection reset

at java.net.SocketInputStream.read(Unknown Source)

at java.net.SocksSocketImpl.readSocksReply(Unknown Source)

at java.net.SocksSocketImpl.connect(Unknown Source)

at java.net.Socket.connect(Unknown Source)

at sun.net.NetworkClient.doConnect(Unknown Source)

at sun.plugin.net.protocol.http.HttpClient.doConnect(Unknown Source)

at sun.net.www.http.HttpClient.openServer(Unknown Source)

at sun.net.www.http.HttpClient$3.run(Unknown Source)

at java.security.AccessController.doPrivileged(Native Method)

at sun.net.www.http.HttpClient.privilegedOpenServer(Unknown Source)

at sun.net.www.http.HttpClient.openServer(Unknown Source)

at sun.net.www.http.HttpClient.<init>(Unknown Source)

at sun.net.www.http.HttpClient.<init>(Unknown Source)

at sun.plugin.net.protocol.http.HttpClient.<init>(Unknown Source)

at sun.plugin.net.protocol.http.HttpClient.New(Unknown Source)

at sun.plugin.net.protocol.http.HttpURLConnection.createConnection(Unknown Source)

at sun.plugin.net.protocol.http.HttpURLConnection.connect(Unknown Source)

at sun.plugin.net.protocol.http.HttpURLConnection.getInputStream(Unknown Source)

at java.net.HttpURLConnection.getResponseCode(Unknown Source)

at sun.applet.AppletClassLoader.getBytes(Unknown Source)

at sun.applet.AppletClassLoader.access$100(Unknown Source)

at sun.applet.AppletClassLoader$1.run(Unknown Source)

at java.security.AccessController.doPrivileged(Native Method)

... 10 more

[quote][/quote]

[adrien]

Hi

Have you looked inside Client.htm, which is used to serve this file?

I wonder whether the sun java system requires a different syntax for specifying the location of a java applet to run.

Adrien

[llupin]

I haven't altered client.htm. I saw this problem when we were running WG 5.2. We just upgraded to WG 6.0.

It works fine for the Win9x, 2K and XP clients that use MS Java. The only exception is I have a WinXP system running SP2 which uses Sun Java plug-in and it works.

[llupin]

Update:

I was configuring a Windows 98 user to be able to access an Exhange server on the local network via the web client. This person was using Star Office so the Sun java was installed.

The web client wouldn't work through the proxy so I changed IE's connection settings to bypass the proxy on local addresses. As I did so I found that the user was using proxy setting different from what I have always used.

Normally when I setup a client I set the http, https to use the http proxy at port 8010 and socks at 1080. I don't bother with ftp or gopher. There is a setting for "use the same proxy server for all settings" Which I normally leave uncheck. I have used this configuration for ages without any problems. That was until we started using Sun Java...

If I use my standard configuration on a machine running Sun's Java the Wingate logon applet opens but never displays the dialog and eventually times out.

If however I set the browser proxy setting to "use the same proxy server for all settings" then the logon applet will open right up and works fine.

Hopefully this will be helpful for others...