Windows Forum

Ask something
Discussion Locked

Win 2K BO Server & a pesky ISA server...

0 helpful
2 replies

by johnny51 1 view

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

OK - I've got a windows 2000 back office server and seem to get the darn ISA server to work correctly. The Win2k server has 2 NICs, one for WAN, one for LAN. Per the instruction in the readme file they say "just leave the default gateway blank" onthe LAN NIC...did it. The server provides DHCP with the only option set being the default gateway which is the LAN NIC...192.168.1.2. I run through the install of ISA and set the protocol rules to allow any IP traffic from any request and the onlything that ends up working the way I would expect it to is the http proxy. With Proxy 2.0 I could get normal winsock IP traffic to pass through by installing the proxy client software on the clients...http proxy as normal. ISA says that it should be able to provide "secureNAT" clients with connectivity by only changing the DG of the client to the IP of the LAN NIC...

Considering that I think I have the protocol rules set correctly, is there any obvious reasons why my setup won't forward anything but http requests. No mail, no NNTP, no name resolution etc....

2 replies

by johnny51

Ooops first line should reead that I "can't" get the darn ISA server to work correctly..

by rkelly

The big difference between ISA and Proxy 2 is the fact that ISA allows NO traffic to pass at all by default, where as Proxy allows ALL outbound traffic.

Check your protocol rules to see that you have enabled OUT bound access rules and IN bound access rules. The most common mistake made by people migrating skills to Proxy is that they only allow the inbound rules.

The SecureNAT client is fine BUT the traffic goes through the firewall service on ISA, and there must be an outbound rule that allows the traffic, otherwise the firewall will drop it. You also DON'T get user level access control using SecureNAT, if you want this for loggion purposes then you need to use the firewall client.

This discussion is closed to new replies.