Continuing the blogcast series on infrastructure essentials.
Where we left off, we were able to browse the Internet from clients connected to the intranet, but we had to manually configure the ISA Firewall Client application for the name of the ISA server to be used. In part four of this blogcast series, we configure DNS and DHCP on our internal network for a feature called WPAD, or Web Proxy Autodiscover Protocol. Once WPAD is configured, we change our Firewall Client application to automatic proxy discovery to verify our changes have been successful.
Our mini-infrastructure is started to look good. However, we haven't touched on email yet. In the next part, we'll configure an Exchange mailbox for our user, a matching Outlook profile and verify we can send and receive emails internally. Check back soon!
Series Index:0. Network configuration and series background.1. Getting started2. ISA Server configuration to allow basic web browsing capability3. ISA Firewall Client basic configuration