Re: Publishing Rules

  • From: "Jay Schwarzkopf" <jschwarzkopf@xxxxxxxxxx>
  • To: "[ISAserver.org Discussion List]" <isalist@xxxxxxxxxxxxx>
  • Date: Tue, 31 Jul 2001 10:49:38 -0400

My answer was in response to the later question from Mark.

What you might want to do, is use the Microsoft backup/restore vbscript that 
Jim Harrison made available to create a ImportISAsettings.vbs script.

Then create a service on your ISA box to:
1) read assigned IP
2) modify the importISAsettings.vbs script (just the IP address)
3) execute that script
4) start the ISA services (make them Manual startup)
5) stop its own service

This worked for me.





  ----- Original Message ----- 
  From: Mike 
  To: [ISAserver.org Discussion List] 
  Sent: Tuesday, July 31, 2001 5:38 AM
  Subject: [isalist] Re: Publishing Rules


  http://www.ISAserver.org


  I use TZO, but thats is not the problem...

  Again, the problem is that publishing a server rule, does not allow you to 
select "external interface" instead you must identify the  IP address. 

  Mike Clow
    ----- Original Message ----- 
    From: Jay Schwarzkopf 
    To: [ISAserver.org Discussion List] 
    Sent: Monday, July 30, 2001 8:53 PM
    Subject: [isalist] Re: Publishing Rules


    http://www.ISAserver.org


    Install a dynamic DNS client (Direct Update, Dynsite), and register with a 
Dynamic DNS service provider (I use Zonedit).


      ----- Original Message ----- 
      From: Mark Strangways 
      To: [ISAserver.org Discussion List] 
      Sent: Monday, July 30, 2001 7:30 PM
      Subject: [isalist] Re: Publishing Rules


      http://www.ISAserver.org


      Make's sense... how would you map www.domainname.com to a dynamic IP 
anyways :)

        ----- Original Message ----- 
        From: Mark Strangways 
        To: [ISAserver.org Discussion List] 
        Sent: Monday, July 30, 2001 7:28 PM
        Subject: [isalist] Re: Publishing Rules


        http://www.ISAserver.org


        Well,

        If you are using ISA Server to publish Web servers and other servers, 
making them available to Internet clients, you must obtain one or more static 
IP addresses in addition to registering your domain names. Internet users will 
access your internal servers by accessing these IP addresses or names.

        If you have registered an Internet domain name, you may decide to have 
your Internet service provider handle the details of how to administer the 
listing of your domain name in DNS for use by others on the Internet.

        When you publish internal servers, you must obtain static IP addresses 
with which to associate the domain or server name. When external clients access 
your web site or domain, local server, the ISP's DNS name resolution server 
will find the IP address associated with the requested Web site name 
server-usually an IP address on your ISA Server or on a perimeter network (also 
known as a DMZ, demilitarized zone, and screened subnet).

        Alternatively, you can use an internal DNS server to resolve requests 
from external clients. This DNS server should be published like any other 
published server. For more information, see Server publishing rules.



        I guess they could be :(

        perhaps you could put a router or something in front of the isa to 
translate dynamic ip's to static ones... What do you think ... Jim ?

        regards,

        Mark

          ----- Original Message ----- 
          From: Mark Strangways 
          To: [ISAserver.org Discussion List] 
          Sent: Monday, July 30, 2001 7:24 PM
          Subject: [isalist] Re: Publishing Rules


          http://www.ISAserver.org


          Good point, there must be a solution to that . Microsoft wouldn't be 
THAT close minded, would they ?

          Regards

          Mark
            ----- Original Message ----- 
            From: Mike 
            To: [ISAserver.org Discussion List] 
            Sent: Monday, July 30, 2001 7:07 PM
            Subject: [isalist] Publishing Rules


            http://www.ISAserver.org


            Does anyone know why Microsoft decided not to allow you to select 
the external interface versus the actual IP address in the publishing server 
rules. If you receive your IP DHCP, and the IP address changes then none of 
your publishing rules will work.

            Any work arounds?

            Mike CLow
            ------------------------------------------------------
            You are currently subscribed to this ISAserver.org Discussion List 
as: strangconst@xxxxxxxx
            To unsubscribe send a blank email to $subst('Email.Unsub') 
          ------------------------------------------------------
          You are currently subscribed to this ISAserver.org Discussion List 
as: strangconst@xxxxxxxx
          To unsubscribe send a blank email to $subst('Email.Unsub') 
        ------------------------------------------------------
        You are currently subscribed to this ISAserver.org Discussion List as: 
strangconst@xxxxxxxx
        To unsubscribe send a blank email to $subst('Email.Unsub') 
      ------------------------------------------------------
      You are currently subscribed to this ISAserver.org Discussion List as: 
jschwarzkopf@xxxxxxxxxx
      To unsubscribe send a blank email to $subst('Email.Unsub') 
    ------------------------------------------------------
    You are currently subscribed to this ISAserver.org Discussion List as: 
jclow@xxxxxxxxx
    To unsubscribe send a blank email to $subst('Email.Unsub') 
  ------------------------------------------------------
  You are currently subscribed to this ISAserver.org Discussion List as: 
jschwarzkopf@xxxxxxxxxx
  To unsubscribe send a blank email to $subst('Email.Unsub') 

Other related posts: