Make sure that you are actually
generating the reports and not just looking in the 'Monitoring/Reports'
To generate reports, do the following:
Fill out the wizard (Start report generation: Immediately)
Wait a few seconds.
Now go back to the 'Monitoring'
-> 'Reports' section and there should be reports. One under each
(Summary, Web Usage, etc...)
When i installed ISA RC1 in cache mode i couldn't get my web pages and then i installed it in integrated mode and everything worked fine and i didn't any of my configuration! Why would this be so?
This is probably because if you install ISA in cache mode only, it does not do the transparent proxying, which you need if you do not manually setup the proxy on a client. However, in Integrated mode secure-NAT will automatically proxy all requests without the need of configuring a client.
I want to be able to connect to the ISA server through MMC, which works fine on the server where it is installed but I would like to control it from my Windows 2000 professional PC. Is this possible?
You need to run the ISA install on the Win2k Prof PC and choose only to have the administration portion installed. Also the user that is logged in
must be a VERY privileged account. Including Enterprise Admin and Schema.
In the situation where you have a T1 hooked up to a router, then to an ISA Firewall enabled Server, then a switch, and then various servers & other pc's, what would happen if the ISA machine went down (i.e. pull the power plug). Do the servers and pc's still get internet traffic, or does the ISA server being down prevent any machines behind ISA from getting any internet traffic?
If the configuration is router
----> ISA ----> switch ----> other servers, etc. then if the ISA
computer goes down, the network card loses
power, and therefore cannot route packets back and forth any more.…
How to install the 'ISA-server' snap-in on a non-isa server for remote administration?
Just run the setup, choose custom and only check the management console.
You automatically have the snap-in installed, you have already a shortcut in the 'programs folder'.
I have Proxy 2.0 on W2K AS with SP1. I want to upgrade to ISA server. I have a VPN running on the Proxy box and an Exchange server (5.5) behind the Proxy. When I upgrade what filters and allows am I going to have to define? Will I have to upgrade all the clients as well since we have the WSP client on the machines?
What gets kept, and what gets whacked, depends on what mode the ISA Server is installed in, and the group membership of the user installing the ISA Server. Check out the upgrade guide on the ISA Server CD to get the details. It *does* make a big difference, so you have to know what the specifics are before performing the upgrade.
The Winsock Proxy client will work with ISA Server. I haven't seen, and haven't heard of any problems with using it.
You don't need to make the Exchange Server a Winsock (Firewall) client, as it will work if it is configured as a SecureNAT client. It should still work as a Firewall Client, though, if you have made some special configuration changes in the wspcfg.ini file.
However, I would suggest removing the Winsock Proxy client software from the Exchange Server can configure it as a SNAT client first, and see if that works.
I need to configure isa server on my network. I've 3 servers (1 for firewall, 1 for web, 1 for database). Ne1 have documentation about configure network between their and isa server?
Put the ISA Server at the edge of the network. Put the web server on the DMZ between the Internet and your internal network. And put the database server on your internal network and create a packet filter on the ISA Server between your internal network and the DMZ to restrict communications to the internal database server so that only the Web Server can access it through the downstream firewall.
What is the most practical method of upgrading the beta version we have installed to the full version of the Standard edition of ISA Server without losing any configurations already in place?
There are no *official* recommendations on this published on the MS site, so we can't say what is the preferred method for making the upgrade.
We have upgraded the RC1 directly, and we have done the same with the trial version. Most things seem to be "OK", but you really never know what's left in the registry and the system32 folder after doing this sort of thing.
If you're talking about a production machine, you best bet is to wipe the entire machine, reinstall Win2k, and then install the final version of ISA on that machine. By doing this, no "sins of the past" are left on the machine, which might complicate support and troubleshooting issues.
My dsl router has a static ip and my isa server external interface also has a static ip. The isa server's external interface's default gateway is the dsl router's ip. Now these 2 ip addresses belong to a subnet with 16 ip addresses. of which 2 are used as described above, and 2 r used by the network number and the broadcast ip. The subnet mask of the router and the external interface of the isa server is 255.255.255.240 . Now i wan't to know that how can i assign the remaining ip addresses to machines in my internal network. for my internal network i am using the 10.0.0.0 network with a subnet mask of 255.255.255.0. All the computers run in one network segment thru a hub and a switch.
You can't assign the IP addresses to clients on the internal network, but you can put a third network card in the ISA Server and make a perimeter network (DMZ) with those addresses. You'll have to subnet the addresses because they can't be on the same network ID as the external interface.
Initial vanilla install of ISA did not allow me to ICMP through my server. Both external and internal nics respond to ICMP's but will not pass through
the server. I followed the instructions on ISAServer.org and created rules opening everything up, all services (telnet, ftp, etc..) work with the
exception of ICMP.
Enable IP Routing
Configure the client as a SecureNAT client.
Then you'll be able to ping through the ISA Server.