Hi, I have installed ISA 2006 standard and right before the install completes my terminal service session disconnects and I cannot reconnect to the server. I have to actually log on at the server console, then open ISA 2006 and add my IP address to the system policy that allows terminal services. My workstation is using network address translation. Is there any way around this disconnect? I have read that ISA 2006 during the install is supposed to add the ip address of the client that is ts'ing to it...
This is the staging environment, i will be installing this in production in 2 weeks, but i would like to do it from home but i cannot because i would have to drive to the datacenter to add my ip to the allow list in ISA 2006.
I suppose that scenario would work if we used windows firewall which we do not. That service is stopped and disabled as part of our basebuilds prior to installation of ISA. I suppose that I could enable and start the windows firewall, then put the exception in place then run the isa installation...would that circumvent my problem?
The second step-by-step was very helpful to me when I initially installed ISA and the MMC. Thank you for the guide!
However, I still have an odd problem. While I can easily connect using the MMC and manage all aspects of ISA 2006 it will NOT display any logging. It just sits there saying "Fetching results...". I have verified that there are plenty of events being logged by physically logging into the ISA server, and the client fw (standard XP fw) shows no denies from the ISA server box.
David C., CISSP/CISM/SnortCP/MSP ISA 2006 Std. Edge Firewall Mode / W2K3S R2 AMD Athlon 2.4GHz / 2GB Ram / Dual GIG NIC