Workaround to Watchguard Authentication

[hanginginthere]

Does anyone know of a way to bypass the authentication applet that Watchguard requires in order to establish an outbound Internet connection?

This is becoming a REAL aggravation to my 300+ users and I'm tired of getting complaints. I've tried the WGAgent, but it still requires a logon once every 24 hours and at $15/user it's expensive.

I have a new firewall in next year's budget but I'd like to find something in the meantime.

Thanks.

 

[AlienEmpire]

It sounds like your HTTP service is configured to use Users instead of IP's to access the Internet. You can remove the users and let the "ANY" option give access to everyone. Or, you can use users and the IP's of the workstations that need Internet access.

If everyone is going to have Internet access it's easier to remove all the users from the Outbound HTTP service and use the ANY option.

 

[hanginginthere]

Thanks AlienEmpire.
I was hoping for an integrated solution that used Microsoft's SAM (NT) or AD (W2K) for authentication instead of: 1) reentering all users into the WatchGuard 2) playing around with IP's (we're using DHCP) since we need to know who goes to which web site.

Guess I'll have to replace it next year.

 

[Frankenherder]

You can go to your policies, under network you can add your NT servers as Authentication servers so you do not have to add every user.

I am new at this but it should work.

 

[hanginginthere]

We have declared our NT PDC as the authentication server in Watchguard, but it still throws up the Watchguard Authentication Applet. In checking the Watchguard website, it appears this is normal and is not going to be changed. I was hoping we had something misconfigured (I inherited this configuration). Or that there was another way to integrate Watchguard Internet access back to the domain without throwing up the applet. Apparently not.

Thanks