• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

ISA Server and Plesk 8.6 - External IP Questions ...

O

OmegaQuest

Guest
I have an ISA Server 2006 setup as a 3-leg perimeter.

The Plesk Server is on the perimeter.

My question is, because the perimeter IP is an internal one (192.168.0.x) with the exteral ISA server's NIC being the public IP, how do I set Plesk up to use see and use the Public IP when it comes to hosting domains.

Obviously I can not set the NIC on the Plesk server to the external IP, because it's being used as the external for the ISA server itself.

This is how I have it set up to help make more sense (The public IP's have been masked):

ISA Server NICs:

External (Net) - 12.54.36.12 (public IP)
Internal (internal network) - 192.168.1.1
Perimeter - 192.168.0.1

Plesk Server NIC:

Perimeter - 192.168.0.10

-------

I have to run the Plesk thoruhg the ISA Firewall.

I have the roting and stuff complete, I just need to know the IP problem.

Thanks for any help you can provide.
 
I dont believe that you can - Plesk only knows about the IPs that are on the local area connection (local NICs) so it cant know about anything you are doing through a NAT or SNAT.

We ran into the same problem a year or so ago and never had a solution, Plesk always shows the private IPs in the display.
 
Back
Top