AOL and wingate

[jonifresh]

Hi

I have a Adsl 2 meg broadband with Bulldog and i used to logon to AOL using a TCP-IP connection, AOL allows people to login to there port hole providing they have a AOL account setup. Since i installed wingate i can no longer connect any wingate client computers. (error is dns problem- check dns settings etc) is there a way for this to work or seen as its AOL is it out of the Question.

Many thanks
W.J

[jamesc]

Hi Jonifresh,


*Can't say I have ever been an AOL customer, so I am not familiar with the interface you are using; i.e. web page or application? Could be a connectivity issue or possibly a caching issue as a guess.

1. Are your LAN clients using the WinGate Internet Client (WGIC)?
2. Do they have NAT as well?
3. Can you confirm DNS is working?

If they do have the WGIC installed, and NAT, then we may need to setup the AOL application name as "Local Access" within the WGIC applet; this means the WGIC will ignore and the connection will pass on to NAT.

You can turn off caching via the Cache option in GateKeeper for the sake of testing.

[jonifresh]

Thanks for responding

The client computers don't have the WGIC software installed, they are connecting to the wingate server through internet explorer's proxy settings, pointing to the WG Server's IP address. AOL works fine on the wingate server but i receive a dns error when i try to connect my client laptop to AOL - The AOL software is installed on client and server computer. I read somewhere that it can be done but details were not given.

Thanks

Wayne

[jamesc]

Hi Wayne,

I saw your support ticket this morning regarding the same issue; there are a couple more things that you might want to try.

1. So it is not a caching problem; correct? You have tried that; yes?

2. Does the DNS server that WinGate use's, is it ultimately the same one the LAN Clients use? i.e. When surfing from the WinGate server, it will probably connect to a DNS server specified on the External Network card. When a LAN client connects, it may be a different server if you put an address into GateKeeper --> DNS / WINS Resolver.

3. Have you tried removing the proxy from IE as a test, and use a secondary connection method like NAT / WGIC.

4. When the WinGate servers' Internet Explorer is pointed to the localhost address, can it access the website?

5. Is the website using HTTPS or HTTP.

6. Do you have any plugins?

7. Does turning on WWW Proxies debug logging indicate what the issue is?
GateKeeper --> WWW Proxy Service --> Logging.
C:\Program Files\WinGate\Logs\WWW Proxy server

[jonifresh]

Thanks for you message

I still cant get this to work, I'm not that clued up on dns settings etc, and i'm new to wingate so you have lost me a little in your last post.

(to summerize)
The client computers work ok, surfing the internet normally through I.Explorer. mozilla etc: its just AOL thats the problem

I installed the wingate server to use ENS as advised during installation
and i disabled the wingate firewall just to make sure it wasn't that.

I have configured the client's I/E browser to use proxy settings, pointing to the wingate server 192.168.2.10 and used port 80.

AOL software is on the wingate server (which works but wingate does not log any events) and AOL is installed on the client computers.

The error from AOL 9 on the clients, is a DNS serror.

Has anyone got this to work and if so does it work correctly, i cant see how wingate would beable to log all internet events used through AOL'S web browser.

Thanks for any help.


Wayne