I am trying to configure ISA server publishing and when I try to publish a server, there are no external IPs for me to select from.
We did not configure the external IP on the external NIC before installing ISA since we wanted to install ISA "offline" and then drop it into our live environment.
So the question is, how do I get ISA to recognize the external IP addresses "after the fact"?
Hi, I am actually having the same problem and my external nic is "alive". When I manually type in the IP of my external nic card, I get a dialog box telling me that my specified ip address is not external (I don't get any choices for ips in the list box either). I must not have my external ip address configured correctly?? I noticed that the "external" ip that I am using is included in the internal ip range on my LAT table. Could this be the issue? Do I have to manually take this ip out of my internal ip range in my LAT table? (not sure how to do that - get errors when trying.)
Any help is greatly appreciated - I'm a newbie too. thanks so much!
I will check out those links! thanks! (I just registered with a different login name...)
Q for you: I want ISA to accept a request on port 8001, then redirect this request on port 8000 to another server. Here's what I think I need to do:
-Open port 8001 via a packet filter rule (I have packet filtering enabled) -Create a server publishing rule to redirect this request to appropriate backend server on port 8000 (I'm hoping that there's a "bridging" tab (like in web publishing rules) where I can redirect the request from ISA to backend server on 8000 instead of 8001).
Am I on the right track - do I want a server publishing rule for this? Is there any good basic tutorials that I could find to help me with this? I'm having a tough time finding basic tutorials.
Ah...I think I figured out my problem. I also had the external IP addresses in the LAT table. Need to make sure they are not in the LAT table, also program the IP address in the TCP/IP configuration for the external NIC.
The key then is to reboot the computer so that the services are restarted and then the external IP address show up when creating the rules.
You seldom need to create packet filters! So, don't create packet filters yourself if it is not strictly necessary. The protocol, site&content and publishing rules will create them dynamically for you.
To publish an internal service not based on HTTP/HTTPS you need to use server publishing rules. In server publishing rules you can *not* redirect to a different port number. So, the external and internal port number *must* be the same.
How did you delete your external ip address from your lat table? In my lat table I have a range of internal ip addresses (my "external" ip is included in this range) and I cannot alter this entry at all - it tells me it can't "save the properties". Any help is appreciated. I'll look into this more, just wanted to see if you had a quick answer. thanks for any help.
Update: I could not create a server publishing rule because ISA wouldn't recognize my "external" IP address as really being bound to my "external" nic card. The reason that it couldn't recognize it as "external" was because this IP address was listed in my LAT table (LAT table lists all "internal" addresses only.) I couldn't delete my "external" IP from the LAT table though for a quirky reason: you have to make sure that you always have an entry for your internal ip in the lat table. I was trying to modify my internal ip range (which included both my internal and external ip addresses and was having trouble because I was also trying to temporarily delete my internal ip.) anyway.. hopefully that's useful to someone.