NTLM Authentication not working...?

[Bunkah]

Maybe I'm doing it wrong, but my user Database is taken from my Windows Server 2008, same with my groups.

They're all there, and every change I make, it updates the list.

Now for every User Service that I intercept (RDP, FTP, SMTP, etc..) there's a user policy configuration, but it doesn't work because when I look up in the History, they're all logged as Guests and the service is blocked until I add Everyone with unrestricted rights.

My Server is the DCHP (which I want to keep) and the computers are using DCHP, so I can't use the "Assumed" option.

It worked with my WWW Proxy Server because I added the Proxy information in my Internet Explorer. Wingate logs the port 80 properly, but when it comes to other ports where there's not always proxy settings, it logs Guests.

is there a way that the current Domain Username is transmitted to the Wingate when there's a connection established?..

Do I have to install the Wingate Internet Client to every computers?

[logan]

Hi Bunkah,

What you are experiencing is normal behaviour. It's important to keep in mind that not all protocols support authentication. This means the clients can only authenticate their sessions through services that support proxy authentication (e.g. the WWW Proxy).

If you require that users authenticate with their domain account for all sessions through WinGate, then the WinGate Internet Client is a good option.

You could also drop the authentication level for all services to user may be assumed and require that users open a browser before they do anything else. After users open their browser and authenticate with the WWW Proxy, they will become assumed and get access to all other WinGate services as well.

If you don't mind requiring your users to enter their authentication details from time to time, you could use the QbikAuth tool in order to authenticate the clients.