Wingate usage in a NATed environment...

[snaydragon]

I have a client that has requested we setup a filtering/auditing solution, and wingate fits the bill. I have it in place, however, have run into a snag.

Here's the setup:

This is a smallish environment, ~13 users. They all are statically addressed, and have NO centralised users or management. They also have a third party ASP that is EXTREMELY uncooperative, so the only place I can put the wingate server is on the outside of the ASP's router. This has the effect of making only one IP show up as a wingate client. I have local users created on the wingate server, and different policies for different users. However, as soon as the first user authenticates (using gatekeeper), it automatically treats all other users as the first user. I need it to prompt everyone for usernames, or be able to recognise that there are multiple users on this one IP.

To also clarify: Using local usernames/passwords from the machines is not an option. The machines all use a common username and password, and this cannot change. Moving the wingate server is not an option, I can't place it behind the ASP's router, as I do not know what routing structures the ASP uses, and they will not disclose, and will NOT work with us unless the client pays them to (the client refuses - extremely large amounts of $$ being demanded by the ASP).

With this information, does anyone have any advice? I'll be more than happy to post any other information desired, to help illustrate the picture.

Thanks in advance for any assistance...

[adrien]

Hi

if you add the IP of the ASP router (the one that shows up as the client IP for the client connections) as a multi-user IP (on the users tab in GateKeeper), then it won't inherit credentials any more, and each connection will be required to auth.

Regards

Adrien