Running ISA 2004 SP2 on Small Business Server 2003 Premium SP1. Installed ISA in May. From that point on I could not access the router via a browser. Didn't think anything of it at the time as I didn't need to get to it for anything. It came up now as I'm trying to move email from the ISP to our Exchange server and I need to check the port 25 settings. I can get to the login page, but I then get an ISA error page, error code 64, could not establish a connection. I can PING the router, so I think it may be an Access Rule that's blocking it. I've been through the access rules and can't find anything that would stop me (but I'm VERY new to ISA), so I'm hoping someone else has run into the same issue and knows how to fix it.
Thanks in advance,
_____________________________
Michael J. Webb Administrative Assistant/IT Administrator Platte River Whooping Crane Critical Habitat Maintenance Trust and the Platte River Whooping Crane Maintenance Trust, Inc. "We Speak for Cranes!" 501(c)(3) non-profit organizations 66
You'll need to find the denied packet to resolve this. In the ISA console go into Monitoring, move to the Logging tab. Click Start Query. Attempt access to your router. Go back to ISA. Click stop query. Look for the denied packets. Here you'll find which rule is blocking your request and why. You can then create a new rule allowing this traffic to pass.
I'm not sure I understand - are you talking about removing an Access Rule? Can you give me more details?
_____________________________
Michael J. Webb Administrative Assistant/IT Administrator Platte River Whooping Crane Critical Habitat Maintenance Trust and the Platte River Whooping Crane Maintenance Trust, Inc. "We Speak for Cranes!" 501(c)(3) non-profit organizations 66
Sorry about the delay in replying; have had a problem with the boss's laptop not receiving email.
I did as suggested, set up a simple log query, but could not get an Access Rule listed as the "blocking agent." I see in the log "Denied Connection" and the CLient ID as 192.168.1.10, which is the IP of the external NIC. Just as a hunch, I checked my DHCP scope for the internal network (192.168.16.0 - .255) and saw that "003 Router" is set to 192.168.16.2 - the internal NIC IP (all per advice received on www.smallbizserver.net).
I'm sure it's something simple; but at the moment I can't reach it by PING, NSLOOKUP, or HTTP. I ahve to connect a laptop directly to the router to "talk" to it. That's a pain as I ahve to go find one to use for a few minutes.
_____________________________
Michael J. Webb Administrative Assistant/IT Administrator Platte River Whooping Crane Critical Habitat Maintenance Trust and the Platte River Whooping Crane Maintenance Trust, Inc. "We Speak for Cranes!" 501(c)(3) non-profit organizations 66