Yep copyed the setup from my ISA 06 box which works fine
i didnt import it i have them running side by side to get the config but the isa has no nics in it as there disabled and tmg is live so i can test rules out.
it doesnt make any sense to me why this dont work
my lan nic is wan
no G/W 10.35.248.1
10.35.248.31 (both internal dns) no dns
that is how it was setup with isa 2006 our ips county counicl have nat and forwards to wan for for our web sites so isa 06 had web listners listening on that 10.35.251.3 for our sharepoint, owa etc... which worked fine
That's where my setup is slightly different, our LEA is on a 172.18.180.xxx address where as internally i have 10.0.8.xxx Address.
As you have near enough the same ip for internal and wan then what i would say is check that on your internal network it has not added your wan ip address's to that range.
The Internal Network may have put that range in there, which might be where it is getting confused, just check what range's it has allocated for your internal network.
All sorted thanks James and everyone else. It was a problem with making sure the windows firewall was off and the firewall service that kept stopping also me getting the right info in the right nics does help.
do you know if clients need to use the client firewall in order for the url filtering to work?
I have added a new nic on the server for the guess wireless system and want to put url filtering on that.
Debunking the Myth that the ISA Firewall Should Not be a Domain Member
For the last two years I’ve been trying to communicate to ISA firewall admins that a domain member machine is more secure and more flexible than a non-domain member machine and that they do themselves and their companies a disservice by not joining the ISA firewall to the domain. This is a significant issue and not something to be taken lightly because there is a serious security hit you take when you don’t join the ISA firewall to the domain.
There are currently 1 users browsing this thread. (0 members and 1 guests)