ISA 2000 Web Publishing Rules Issue
I am running ISA 2000 SP1 FP1 on a Windows 2003 SP1 server. I am having a problem with web publishing rules. My testing shows that none of the web rules are getting past the ISA server. I have a pointer that directs traffic to my front door for use with OWA, OMA, & ActiveSync. The traffic is coming to my door but it appears that the ISA server is not forwarding the request. I put up a temp web page on the ISA server and am able to get it but can go further.
FYI:
I recently reloaded this box due to hardware failure. Prior to the reload ISA was running on a Windows 2000 SP4 server and everything was working fine. I have applied one hotfix, KB897651, since the reload to correct a VPN issue I was having. Also all of the website are working in-house as well as all Server Publishing Rules.
Any thoughts?
FYI:
I recently reloaded this box due to hardware failure. Prior to the reload ISA was running on a Windows 2000 SP4 server and everything was working fine. I have applied one hotfix, KB897651, since the reload to correct a VPN issue I was having. Also all of the website are working in-house as well as all Server Publishing Rules.
Any thoughts?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Applied the service pack, no change. Thanks.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thank you for your comments busbar, I have no proxy or firewall set for the server itself. As for the the internal IP, I am able to get to the internal site from the server with no problems.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
ok, thanks.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I want to say that I saw an article on that and tried it but tlet me check. Thanks.
ASKER
I want to say thank you to everyone that posted comments trying to help me. I ended up calling Microsoft about an Exchange issue that turned out to be DNS related. It appears the problem I was having had to do with DNS as well. Things are now passing from ISA to Exchange.
ASKER