RE: Deploying ISA 2004 firewall client - how to enforce?

Aha! I think I've found the problem.
 
The AutoDiscovery information was just not being published.
 
From Help File:
 
<snip>
To publish automatic discovery information

1.      In the console tree of ISA Server Management, click Firewall
Policy. 

        Where? <ms-its:Y:\Microsoft ISA Server 2004
Beta\isa.chm::/FW_H_PublishAutoDisc.htm#> 

        *       Microsoft ISA Server 2004 
        *       Server_Name 
        *       Configuration 
        *       Networks 

2.      In the details pane, select the applicable network (usually
Internal). 
3.      On the Tasks tab, click Edit Selected Network. 
4.      On the Auto Discovery tab, select Publish automatic discovery
information. 
5.      In Use this port for automatic discovery requests, type the port
number on which the ISA Server should listen for WPAD and WSPAD
requests. 

 Notes

*       To open ISA Server Management, click Start, point to All
Programs, point to Microsoft ISA Server, and then click ISA Server
Management. 
*       Click the Apply button in the details pane to save the changes
and update the ISA Server configuration. 

</snip>

Hopefully this will sort things out :)

Cheers Tom.

Jason 
________________________________

From: Jason Merrique [mailto:j.merrique@xxxxxxxxxxxxxxx] 
Sent: 13 May 2004 14:27
To: [ISAserver.org Discussion List]
Subject: [isalist] RE: Deploying ISA 2004 firewall client - how to
enforce?



        http://www.ISAserver.org
        
        Cheers Tom,
         
        Would the answer be applicable for ISA 2004?
         
        Cheers,
         
        Jason
         


________________________________

                From: Thomas W Shinder [mailto:tshinder@xxxxxxxxxxx] 
                Sent: 13 May 2004 14:15
                To: [ISAserver.org Discussion List]
                Subject: [isalist] RE: Deploying ISA 2004 firewall
client - how to enforce?
                
                
                http://www.ISAserver.org
                
                Hi Jason,
                 
                Here's a chapter from the ISA EDU kit. There a golden
nuggets dispersed through this kit.
                 
        
http://www.tacteam.net/isaserverorg/isaedukit/5automate/5automate.htm
                 
                HTH,
                Tom
                 
                Thomas W Shinder
                www.isaserver.org/shinder
                ISA 2004 Beta - Get it now!
                http://www.microsoft.com/isaserver/beta/default.asp
<http://www.microsoft.com/isaserver/beta/default.asp> 
                ISA Server and Beyond: http://tinyurl.com/1jq1
                Configuring ISA Server: http://tinyurl.com/1llp
                
                 

                        -----Original Message-----
                        From: Jason Merrique
[mailto:j.merrique@xxxxxxxxxxxxxxx] 
                        Sent: Thursday, May 13, 2004 7:53 AM
                        To: [ISAserver.org Discussion List]
                        Subject: [isalist] RE: Deploying ISA 2004
firewall client - how to enforce?
                        
                        
                        http://www.ISAserver.org
                        
                        Hi Tom,
                         
                        Well thats what I thought....
                         
                        I've added the WPAD entries to the DHCP scope
options (not sure what you mean by DNS though....) but the firewall
clients still aren't automatically detecting the server. They can if I
*manually* set it to do that, or to "Detect now". It just isn't Enabled
by default.
                         
                        It's driving me nuts :\
                         
                        Cheers,
                         
                        Jason

        a blank email to $subst('Email.Unsub') 

Other related posts: