Java authentication

Use this forum to post questions relating to WinGate, feature requests, technical or configuration problems

Moderator: Qbik Staff

Java authentication

Postby telia » May 02 05 3:14 am

Hello,

We have a PC that's running WinGate 4.5.2 and assumed users are able to access the internet without any problems from the local LAN as well as from another remote location on a different sub-net which is linked to the local LAN using routers.

Our problem is with a certain application which uses Java authentication, there are no problems logging in from the local LAN but users at the remote location are unable to do so and get an error message that application is experiencing technical difficulties.

We would appreciate if someone could help us solve this problem. The IP addresses of the various equipment are as follows:-

1) Wingate server: 192.168.0.1
2) Local router: 192.168.0.2
3) Remote router 192.168.1.2
4) Remote PCs 192.168.1.*

Thank you
telia
 
Posts: 5
Joined: May 02 05 1:02 am

Postby telia » May 04 05 4:50 pm

As no one seems to be helping out here maybe because my problem may be too simple, I would just like to add that the default gateway on the remote computers is 192.168.1.2

Thank you.
telia
 
Posts: 5
Joined: May 02 05 1:02 am

Postby genie » May 04 05 5:37 pm

Hi,

When you said "remote location" - did you mean the application running outside your local network? It might be the case of service not being bound on the external IP address then.
genie
Qbik Staff
 
Posts: 1788
Joined: Sep 30 03 10:29 am

Postby telia » May 05 05 5:18 am

Thank you for your response.

The remote location is on separate network connected to a switch on the main network using routers.

We don't have any problems accessing the internet from the remote location except the authentication process to a particular website which uses Javaw and requires ports 80 and 443 to be open.

Wingate connects to the internet via a USB DSL modem and the IP address assigned by the ISP is dynamic.

The only IP addresses showing up in the bindings tab of the WWW proxy server service are the internal NIC IP and 127.0.0.1 which are both bound together.

Thank you very much for your assistance.
telia
 
Posts: 5
Joined: May 02 05 1:02 am

Postby adrien » May 05 05 12:25 pm

Hi

The Java authentication you refer to is WinGate's one? If so, it connects to the Remote Control Service in WinGate on port 808, so you would need that port open as well.

Adrien
adrien
Qbik Staff
 
Posts: 5448
Joined: Sep 03 03 2:54 pm
Location: Auckland

Postby telia » May 06 05 8:43 am

Hi.

Port 808 is open as I am able to log in with Gatekeeper from the remote computer on the sub-net but I am unable to do so with the other application that uses javaw for authentication.

Thank you for your assistance.
telia
 
Posts: 5
Joined: May 02 05 1:02 am

Postby Pascal » May 06 05 9:20 am

Let's just be clear - do you actually require the Java Applet (Served by WinGate for authentication purposes) or does this remote website have it's own Java authentication scheme which is failing? The two will be very distinct and separate problems.
Pascal

Qbik New Zealand
pascalv@qbik.com
http://www.qbik.com
Pascal
Qbik Staff
 
Posts: 2623
Joined: Sep 08 03 8:19 pm
Location: Auckland, New Zealand

Postby telia » May 07 05 5:23 am

We don't use the Wingate Java Applet and users are assumed as mentioned in my first post.

The remote website has it's own Java authentication scheme which is failing from any PC on the subnet. We don't have any problems with authentication on the local LAN.
telia
 
Posts: 5
Joined: May 02 05 1:02 am


Return to WinGate

Who is online

Users browsing this forum: No registered users and 49 guests

cron