quote:

---

Originally posted by isafan:
Just for kicks, try disabling that protocol filter and making a new one. Set that up for "selected protocols" and select all the HTTP and FTP protocols listed, apply it, and make sure it's running. Stop and start the ISA services (cache, firewall, and download I believe), then try connecting again. First from ISA itself, then from the client.

---

I tried the above and got the same results. I can browse from the ISA Server but not the client. Itsa-making-me-crazy.... But I bet I have set a record for number of ISA installs on one server.

Hey, Thanks for trying. - DBH

That's interesting. Did your setup try to make the internal NIC listed as second in the binding order by default? Ours did. We were wondering about that, it seemed sort of odd. Especially in our case since our internal NIC is embeded. But even though it shows up as connection #2 everything still works fine.

DBH,

Have you tried enabling packet filtering and IP routing? This is something that I'm fairly certain should not have to be done, but it's worth a try. If you haven't, expand Access Policy, and right-click on IP Packet Filters the select properties. On that first properties sheet check the Enable Packet Filtering box, and the Enable IP Routing box. Then try getting out from the client again. This will also allow pings to work from inside the firewall too.

isafan

quote:

---

Originally posted by isafan:
DBH,

Out of curiosity, why do you not want to use the web cache on ISA? It's good, and fast. In general I'd say that it's best to have it on (using the web proxy settings in the browser).

I did experiment on a 2K Pro machine to make sure it works and it does.

I wonder if port 80 TCP is being blocked somehow. It should not be though with your protocol filter.

The really odd thing is that you said it worked when you set up the proxy settings in the browser, but FTP would not work.

Just for kicks, try disabling that protocol filter and making a new one. Set that up for "selected protocols" and select all the HTTP and FTP protocols listed, apply it, and make sure it's running. Stop and start the ISA services (cache, firewall, and download I believe), then try connecting again. First from ISA itself, then from the client.

I'm curious to see what happens after that.

isafan.

---

I you tried your suggestion of enabling packet filtering and IP routing. I didn't make a difference. What the heck am I missing? This should be working. It is a dial-up connection. Are there any tricks that we did not cover earlier on this thread?

Thanks again, DBH

------------------
MicroSoft Fan
UNIX Fan
Linux Fan
*************************
True System Administrator

Thanks, DBH