wingate client hava to connect server with username/Password

[vtrong2002]

Hi all.
I'm using wingate 5.2.3.
I install winage and user default wingate congfig.
I create some user, and set System policies fo this users.
Windows client, i install wingate client. But when windows client start, wingate client don't request username/ password to connect wingate server. I want to confige wingate client show form (Wingate internet Client Login) when windows start. Please help me.

Please help me. Thanks

[Pascal]

Have you set the System Policies to require authentication? This is done by adjusting the "Security Level" (User may be unknown, User may be assumed, User must be authenticated)

You also need to ensure that the policies will be used, this is done by adjusting the "Default Rights Must also be granted", "Default Rights May also be granted" and "Default Rights are Ignored" options.

[vtrong2002]

Thanks.
I want to set the System Policies to require authentication. (When windows client is started, wingate client <Strong>have to </strong> request username/password, but some people don't - user guest default)

"Default Rights Must also be granted", "Default Rights May also be granted" and "Default Rights are Ignored" options. where i can confige?

what I have to choice?

thanks.

[Pascal]

You will find those in the appropriate policy screen. In your case, if I understood everything correctly, you need to set it in the WRP Service. Switch to the policies tab and you'll see it there. Of course, this brings the added complexity of then managing the combination of the two policy groups so you'll need to ensure that the recipients are set properly in that service.

One suggestion - 5.2.3 keys are useable with 6.0.4. In the future you might consider moving up to the latest version as it has fixes included.

[vtrong2002]

WRP Service?
please help me step to step confige WRP Service.
i have to choice what options?

[Pascal]

If you are using the WinGate Internet Client access will, in part, be defined by the WRP Service. If you have GateKeeper open look in the System Tab. (Where DNS, GDP and so on are located). There you should see Winsock Redirector Service (WRP). Double click that and then navigate to the Policies tab. There you will find the settings. I believe by default it has no recipients in there, so all that should be required will be to change that one setting and click [OK].

[vtrong2002]

I add new recipient.
i choice Everyone and user must be authenticated?

after, in Default rights(System policies) i have to choice what options?

[Pascal]

Didn't you already have System Policies setup?

[vtrong2002]

Didn't you already have System Policies setup?

yes. i create some user - vtrong, and add to System policies vtrong with user must be authenticated option.

[Pascal]

Alright, then you don't need any recipients in WRP - you only need the one in System Policies. Hang on a moment ... I'm going to borrow from an email I wrote last night.

Think of it in two primary layers.

-------------------------------------------
System Policies
-------------------------------------------
Service Policies
-------------------------------------------

Those two can be combined as either an OR (Default Rights May Be Used Instead) or an AND (Default Rights Must also be Granted) or they are completely ignored (Default Rights Are Ignored).

Alright, once you've go that down - the Service Policies are divided into three logical sections.

-------------------------------------------
ENS/NAT Policies
-------------------------------------------
WinGate Internet Client Policies
-------------------------------------------
Various Service Policies (Proxies)
-------------------------------------------

Each one of those represents a unique connection schema through WinGate.

Ideally, you would isolate the connection system you are using (WRP [WGIC], in your case) and would setup the policies there. However, this can be defeated by one of your users then setting a proxy service in IE
for example, and neatly circumventing all your hard work.

This is where the System Policies comes in. You can setup the basic access rights (Time restrictions, authentication levels and so forth) in there. Each individual Service (WRP and the rest) have their policy specification set to "Default Rights MUST also be Granted" to force the time restrictions from the System Policies to take effect as well. So use the System Policies like a very generic blanket for common setups.

Then you refine the setup in your Service policies.

[vtrong2002]

Thanks for your suport.
I choice user must be authenticated option when i add new group on System Policies, this is ok.

Thanks.