cb_it
asked on
bypass ISA 2006, no internet
We have a pretty standard Windows network setup here. Windows 2008R2 AD, DNS, etc.
I also have an ISA 2006 server setup in single adapter mode, it has web filtering software installed, that's all it's really used for. It only has 1 nic.
Clients default gateway points to our Cisco router. Browsers have proxy settings pointing to the ISA server, and all works well.
In IE if I uncheck "Use a proxy server..." I am unable to get online. What if our ISA server goes down, or I want to remove it from the network?? Clients will be unable to get online?
Any help would be greatly appreciated, thanks.
I also have an ISA 2006 server setup in single adapter mode, it has web filtering software installed, that's all it's really used for. It only has 1 nic.
Clients default gateway points to our Cisco router. Browsers have proxy settings pointing to the ISA server, and all works well.
In IE if I uncheck "Use a proxy server..." I am unable to get online. What if our ISA server goes down, or I want to remove it from the network?? Clients will be unable to get online?
Any help would be greatly appreciated, thanks.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
it will works if isa down now question how
you should identify dns setting on cisco router and as you mentioned the gateway is ur router it means that cisco provided internet traffic in case of tmg failure you can easily divert your ur client toward to use internet but you need to mentioned dns of cisco router on client machine.
Regards,
Osama Mansoor
you should identify dns setting on cisco router and as you mentioned the gateway is ur router it means that cisco provided internet traffic in case of tmg failure you can easily divert your ur client toward to use internet but you need to mentioned dns of cisco router on client machine.
Regards,
Osama Mansoor
Yes, I would object based on my comment to you above.
Thanks - appreciated.
ASKER
Problem solved, firewall was blocking outbound web traffic.