Skip to main content

LevelBlue Completes Acquisition of Cybereason.  Learn More

LevelBlue Completes Acquisition of Cybereason.  Learn More

Services
Cyber Advisory
Managed Cloud Security
Data Security
Managed Detection & Response
Email Security
Managed Network Infrastructure Security
Exposure Management
Security Operations Platforms
Incident Readiness & Response
SpiderLabs Threat Intelligence
Solutions
BY TOPIC
Offensive Security
Solutions to maximize your security ROI
Operational Technology
End-to-end OT security
Microsoft Security
Unlock the full power of Microsoft Security
Securing the IoT Landscape
Test, monitor and secure network objects
Why LevelBlue
About Us
Awards and Accolades
LevelBlue SpiderLabs
LevelBlue Security Operations Platforms
Security Colony
Partners
Microsoft Security
Unlock the full power of Microsoft Security
Technology Alliance Partners
Key alliances who align and support our ecosystem of security offerings
Loading...
Loading...

FAQ: Is it possible to configure the Web Proxy Auto-Discovery Protocol (WPAD) with WebMarshal?

Expand / Collapse


This article applies to:

  • WebMarshal

Question:

  • Is it possible to configure the Web Proxy Auto-Discovery Protocol (WPAD) with WebMarshal?

Information:

Yes, it is possible to use the Web Proxy Auto-Discovery Protocol (WPAD) and force clients to use a particular proxy when accessing the Internet. Below are instructions for configuring WPAD using an automatic configuration script. DNS and DHCP can also be used to publish the location of the proxy configuration file. For more information see the articles mentioned in the Notes section.

Procedure:

Follow the steps below to force users to use a specific proxy server to access the Internet.

  1. Create the following .dat file and substitute the IP range you want to use the proxy.

    NOTE:
    The .dat file forces users to browse through WebMarshal which is on machine 10.168.44.129 and to not browse through WebMarshal if a user is browsing to an intranet server (with a specific name).

  2. Save the file to a web server accessible from within the local network. The below image assumes the file is found in the root of a server named "servername".
  3. Using Windows Group Policy push the following settings to each user.

     

Note:

The contents and testing of the script are your responsibility.

At the time of writing this article Wikipedia.com is a good starting point for variations to the script. See the following Wikipedia articles:

        


    To contact Trustwave about this article or to request support:


    Rate this Article:
         
    Tags:

    Add Your Comments


    Comment submission is disabled for anonymous users.
    Please send feedback to Trustwave Technical Support or the Webmaster
    .