Originally posted by Clayton:
i've had the autodiscovery off on all the client computers i tried to get to work and it still did not work. i've even un-installed the client and re-installed it with the autodiscovery off about 5 times. it seems like i've been through every possible setting and i really don't understand why this won't work.
the only other thing i can think is that i have a ms proxy 2.0 server still in production that handles my production environment until i get this isa completely working. if i direct the firewall client to that server, it seems to work. but the purpose of me putting this isa server in place is to decomission this proxy 2.0 server, which i can't do until i get all the services moved to the isa server. i've tried stopping the winsock service on the proxy 2.0 server, but it didn't make a difference.
i setup my isa server in integrated mode...would that make a difference here? isa definitely seems buggy and i'm hesitant to move my entire production environment to this product right now. i've even followed some simple instructions off this website word for word, like opening up napster, and that didn't seem to work either.
anyway...i would really like to get this firewall client working. it doesn't seem like it should be this difficult.
thanks for your help
Are you using IP addresses or computer names in the Firewall Client configuration dialog box? Does it work if you use IP addresses? If so, it might indicate a name resolution problem. Do you have a WINS and DNS server on the network and are the clients using them?