When accessing HTTPS, IP does not resolved to URL. Normal ?

[carves]

Dear All,

Looking at the Activity window, when a user goes to a normal website (port 80), I can see the full length of the URL which is fine. But when they are accessing secure site (port 443), the IP address no longer resolved to a domain name/URL.

Its just showing: NAT: TCP Connection to 123.123.123.123:443

Is this normal ? And is there a way to make the destination secure IP address resolved to a domain name ?

Thanks,
Ben

[adrien]

Hi

this is happening because your clients are not configured to use a proxy. Port 80 is intercepted to the proxy, and the host header in the request is used to generate the full URL that you see.

For port 443, it's not intercepted, and shows as a NAT TCP connection.

Because the clients aren't using a proxy, they do their own DNS resolution (resolve site name into an IP address), they then connect to that IP address.

If the clients were using WinGate as a DNS server, the session should show with the name that was used originally to look up that IP.

But the best option is to configure your clients to use a proxy. There are several ways this can be done pretty much centrally:

1. AD group policy - if you're on an Active Directory, you can set proxy settings with a group policy
2. WPAD (web proxy auto detect).

Regards

Adrien

[carves]

Hello,

Apology for late reply.

But how can I do those things ?

Thanks,
Ben

[carves]

Never mind, I figure it out.

Apparently I did not install the DNS Service.

Now everything works.

Thanks,
Ben-