Discussion Locked

ISA Internal clients will not connect to

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

Before installing ISA i was using NAT on Win2K server, internal clients connect fine with no problems, when i ran the ipconfig, ipconfig /release ipconfig /renew, no problems i get all the info dns-suffix, ipadr, subnet, and default GW.
Before installing ISA i disable NAT on the server and left the static internal NIC adr as is 192.168.0.1,(adr) 255.255.255.0,(subnetmask) 192.168.0.1(default Gateway)
Then i installed ISA, did the LAT to point to the internal NIC, completed the install, enable the enable ip routing, allowed protocols rules, the ISA server can connect but not the internal clients, but i noticed the internal clients does not get the full ipconfig renew info only the adr and subnet mask i cannot get the full information on the ipconfig renew.
please advise.....

5 replies

by leon_guerrero

Can you ping outside addresses from the clients from the command line?

Did you try configuring the web browsers to use a proxy server? Tools\Internet Options\Connections\Lan Settings\Proxy Settings and check the use a proxy server....then put thename or ip of the ISA server and the port you configured it to use (I think default is 8080)

Another thing to try is installing the firewall client and see if you can get your clients to connect that way.

by blue screen

it work! thanks for your help!i noticed that the clients didn't get the full ipconfig /renew info, it only got the ipadr, and subnet, but i guess that's the way the isa server works.
thanks!

by elemzy

hi,
i presume ur main reason for installing isa server is to protect ur clients/wkstations from external intrusion. so setting up ip forwarding might put them at risk. the only criteria for isa setup is to install the isa server. set the permit protocol rules and "importantly" check the isa directory on the server, there is a client program called the "firewall client" install this on all the clients. and set there internet explorer proxy setting to use port 8080. disable automatic detect proxy. that should make all ur clients browse thge web and also outlook express to work properly.

by blue screen

it work! thanks for your help!i noticed that the clients didn't get the full ipconfig /renew info it only get the ipadr, and subnet, but i guess that's the way the isa server works.
thanks

This discussion is closed to new replies.