RE: Usage Reporting via SQL Server



Hi Chris,

Just a thought:
Have you tried allowing the SQL protocol from your HR machines to your ISA
Server.
i.e:

Allow
Protocol: SQL Server (port 1433)
From: HR (computer/computer set)
To: Localhost
Users: All users

(or you could even make a user based rule allowing only HR "users" to
initiate SQL sessions to ISA - instead of the HR computer set - recommended
if your HR is on DHCP
Eg:
Allow
Protocol: SQL Server
From: internal
To: localhost
Users: HR Users (user set/group)

).


Hope this helps,

--
Shijaz
www.shijaz.com/isaserver


"Chris Mitfield" wrote:

Before I get to my issue, I thought I might share my config:

I have a single ISA 2004 Enterprise server running on a dual CPU 2.4 Ghz
system with 4GB of RAM. The system is set to have an internal and external
interface. The internal interface is a hard coded 1GB Full connection. I have
this system publishing 6 internal webservers and am hosting an avg of 1800
total sessions.

The ISA server is logging to a SQL backend server which is a dual CPU 3Ghz
with 4GB of RAM and running SQL Server 2005.

Both systems are running Windows Server 2003 R2 with all patches applied for
both the OS and the applications (ISA and SQL).

And now on to my problem. We have an HR department here that wants to be
able to run reports on users at will to find out where they are going. We
have a web group that wants to run reports on who is hitting their sites. And
we have administrators who need to know how the server is doing. My intent
had been to use SQL Reporting Services to provide each of these groups access
the info they need via a web page and call it a day. Unfortunately the only
place that I can run queries is from ISA itself as ANY query I run against
the DB using TSQL no matter how restricted brings the DB to it's knees. What
is the ISA doing for it's queries to avoid this issue?

Thanks in advance for any help you can provide.
--
Chris Mitfield
.



Relevant Pages

  • Re: "Opening ports"
    ... When filtering log on port 5656, ... Create Protocol: ... Understanding the ISA 2004 Access Rule Processing ... Microsoft Internet Security & Acceleration Server: ...
    (microsoft.public.isa)
  • Re: How to Configure ISA 2004 for remote access like vnc, pcanywhere
    ... ISA has several protocols pre-defined, but it isn't uncommon for us to need to define custom protocols to allow certain traffic. ... ISA will route this traffic to a specific IP address, so your target server always needs to have the same IP address. ... Then in ISA we need to create our PCAnywhere Server protocol if it doesn't exist, then create a new Server Publishing Rule to forward PCAnywhere traffic to the target machine. ...
    (microsoft.public.windows.server.sbs)
  • vpn over nat through isa server
    ... ISA 2000 server with SP1 ... Start the ISA Management snap-in. ... Under Policy Elements, locate the Protocol Definitions ...
    (microsoft.public.isa.vpn)
  • Re: Database Server based on SQL database
    ... SQL is a language, not a protocol - they are two different things. ... TDS originated with Sybase and is used by SQL Server (earlier versions were ... both the client and the server side. ...
    (microsoft.public.win32.programmer.networks)
  • Re: From Cisco Pix to ISA.
    ... Static NAT which is not the same as 1:1 NAT. ... ISA does not ... Microsoft Internet Security & Acceleration Server: ... Just remember to choose the Protocol "SMTP Server", ...
    (microsoft.public.isa.publishing)