It is plotted over time. I haven't found a way to make it bigger though. Sort of gives you a birds-eye view. The good news is that the ISA firewall's built in reports gives a very nice graph for Web usage over time of day.
i have a server installed windows 2003 enterprise edition and isa 2004.
i have installed gfi mon 2(the new version for isa2004). my servers ip is 192.168.1.1 and 192.168.0.1. it has two ethernet cards.one to adsl modem (192.168.0.1) and one to the internal network (192.168.1.1).
i give the both ips during installation.but i cant access monitor.isa. could you help me?
I installed GFI WebMon 2.1 on ISA 2000 yesterday. When I used the tool, it seemed to bog ISA down, and I even had to stop and restart the web proxy service.
Today I received widespread complaints from proxy clients that they were receiving random "page cannot be displayed" errors that included the following: "HTTP 502 Proxy Error - Not enough storage is available to process this command. (8)" I Googled, but couldn't find anything about this specific flavor of the HTTP 502 error.
The interesting thing is that when I disabled the GFI WebMon filter, the client-access problem immediately went away. I had not even used WebMon today when the problem was happening, but the filter was enabled on the ISA server.
What can you tell me about that particular 502 error, and do you think it could relate to GFI WebMon?
We're running ISA 2000 in cache-only mode on top of Windows 2000 Server on a pretty robust platform. It's not unusual for ISA to be handling 200 to 300 requests per second during busy periods, with as many as 2,000 current users, as reported by the ISA performance monitor.
Thanks for your help and the excellent ISA resources you provide.
[ February 11, 2005, 10:40 PM: Message edited by: Steve Huntress ]
I'am getting the same 502 Proxy errors and I am running a ISA 2004 SP 2 on a Windows 2003 SP1, the machine is robust to say the least. I am not using the GFI but I am using two other plugins, Optenet and an AV. Does anybody have an hard info on this error.