Mozilla Firefox - Wingate with Java Authentication

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

Moderator: Qbik Staff

Mozilla Firefox - Wingate with Java Authentication

Postby graemeevans » Nov 10 05 4:19 am

Apologies, On searching and discovering event logs of mcafee antivirus enterprise 8.0 it seems that epolicy orchestrator was blocking access to port 80 for firefox.exe however it allowed iexplore.exe mozilla.exe opera.exe and many others.


Please keep for reference or delete message.








Hello.

We are successfully running wingate 5.2.0 with internet explorer clients with the java logon box working ok everywhere. The course our college has started to run requires the use of alternate browsers. So we are using firefox and opera. Opera works fine. Firefox with the proxy set for our wingate server returns the error message in a popup window.
Code: Select all
The document contains no data.

On setting the error messages to display all error data the error returned is (below for ease of reading)
We are really unsure about this one, any help would be appreciated. Has anyone else had this working?

Thanks
Graeme Evans


Error Message:
Code: Select all
Net Reset Error

Offline Error
The document contains no data.

The address (URL) is not a valid format and cannot be read. A typical address will start with "http://", followed by an address, (e.g. www.netscape.com), followed by a path to the content (or just "/"). A common cause for the problem is using backslashes(\) instead of forward slashes (/).

The file specified by the address (URL) cannot be found. Check that the file exists and that you have sufficient permissions to view it.

The address (URL) does not correspond to a known site and could not be loaded. This could be due to a misspelling in the address or because the site does not exist. If the address is known to be valid, or if the problem occurs for many sites, it may be an issue with your proxy service (if you use one) or the directory name service lookup. In such cases you should consult your system documentation, administrator or Internet Service Provider (ISP) as appropriate for further assistance.

The address (URL) starts with a protocol that is not recognized by the browser. A protocol is the part at the front of the address, such as http: or ftp: which tells the browser how to connect to the site. In this instance, the protocol is unknown so loading cannot continue. Check that the address is correct before retrying.

The browser was unable to connect to the specified site, even though it exists. This may be because the site does not accept connections from your computer, the service may be down, or the site does not support the service or port that you tried to connect to.

The browser timed out while trying to connect to the specified site. The site may be experiencing high loads that are slowing it down, or network problems are preventing data from being received from it in a timely manner. If the site is likely to be busy, consider waiting a few moments before retrying the request.

The browser has stopped a connection because the site is redirecting requests to itself in a manner which prevents it from ever completing.

The site responded to the network request in an unexpected manner. This may be due to address (URL) using the wrong protocol for the specified port, or a non-standard configuration on the site which is running different services than expected.

The link to the site was dropped unexpectedly while negotiating a connection or transferring data. This may be due to a network fault somewhere between the site and your computer. If the problem persists, consult your system documentation, administrator or Internet Service Provider (ISP) as appropriate for further assistance.
graemeevans
 
Posts: 12
Joined: Oct 22 05 3:59 am

Return to WinGate

Who is online

Users browsing this forum: No registered users and 47 guests