NAT is getting the Ip address , not resolved site address

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

Moderator: Qbik Staff

NAT is getting the Ip address , not resolved site address

Postby uniquemodel » Feb 10 06 2:12 am

Greetz all,

I have wingate 6.1 build 1077 on Windows Server 2003 Standard.
This server is acting as a mail relay to our internal exchange server, as well as acting as a proxy server to allow certian clients access to the internet.
Everything is working great on the client side, but what I want is in the history is to have the resolved name not the ip address.

example:02/09/06 05:56:43 192.168.0.122 0000151881 Requested NAT: TCP Connection to 207.68.183.32:80
I want the TCP Connection to show the website that the user went to,

Is this a client side setting, or a DNS setting that I'm missing?

Ken Barnum
Unique Model, Inc
2500 Waldork Ct.
Grand Rapids, Mi 49544
uniquemodel
 
Posts: 1
Joined: Feb 10 06 1:45 am
Location: Michigan

Postby adrien » Feb 10 06 7:35 am

Hi

Reverse DNS is not reliable, since it relies on the correct DNS settings at the remote sites for the remote domains.

Also one IP address can relate to many web sites with different names.

If you want more information about the web usage of your users, you could try intercepting the connections into the WWW proxy. That will then show you the actual URLs being fetched by your clients, and allow you to specify much more specific policies.

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


Return to WinGate

Who is online

Users browsing this forum: No registered users and 3 guests