> >http://www.ISAserver.org > > >sorry Danny >u miss understand me >i ask u if we can make conversation through msn me and you .. to solve this >problem ... > >regards > >Qusai Oh, ok ok, no problem. The point is that i don't use chat programs at all :-) Anyways, besides the fact that using port 100 instead of port 80 would mean to type www.yourdomain.com:100 to reach it, you also would have to configure your internal web server to listen on port 100. I suggest you to *reset* all your ISA configuration, i.e. by reinstalling ISA, and then to try to make it working with the "standard" configuration (listener on port 80), etc etc. That way you can see that it works as well :-) Then, after you make it work, you can try to make changes and see what happens... i think that you have some packet filters you don't need, and also the destination set should contain the hostname which correspond to your internal web server. In your case, you may create a destination set containing: webservermachine.yourdomain.com www.yourdomain.com It *must* work. All the problems you have since a month (!) ago aren't caused by ISA, but because you don't follow a simple method, which consist in making the baseline configuration. Danny