RE: web redirection to a Linux server using ISA 2004



Hi Orlando:
Thanks for your reply.

In my point of view, it depends on situation. If you don't want to add a
port at the end of the URL such as http://www.domain.com:81, you can choose
the web publishing method. But this require you to register a new Host
Record to your ISP. If you don't mind the complicated URL, you may choose
the server publishing method.

Please feel free to let me know if you have any questions or concerns.

Have a nice day!

Best Regards
Edward Tian(MSFT)
Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security
======================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.

Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.

For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Any input or comments in this thread are highly appreciated.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
| Thread-Topic: web redirection to a Linux server using ISA 2004
| thread-index: AcXNnFnTmBmP7DPISSOtHi72GP+G/w==
| X-WBNR-Posting-Host: 220.234.172.107
| From: "=?Utf-8?B?T3JsYW5kbw==?=" <orlando_lister@xxxxxxxxx>
| References: <B966A3E9-2774-4A62-9E98-1467FE5F2F79@xxxxxxxxxxxxx>
<X7ISNIWzFHA.424@xxxxxxxxxxxxxxxxxxxxx>
| Subject: RE: web redirection to a Linux server using ISA 2004
| Date: Mon, 10 Oct 2005 06:13:05 -0700
| Lines: 152
| Message-ID: <55A17CCB-7FA5-4A9A-A7FD-2EAA086CA7D4@xxxxxxxxxxxxx>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.windows.server.sbs
| NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
| Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA03.phx.gbl
| Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.windows.server.sbs:211691
| X-Tomcat-NG: microsoft.public.windows.server.sbs
|
| Thanks for the response.One more question. Which way you think is better?
|
|
| "Edward Tian" wrote:
|
| > Hi Orlando:
| > Thank you for posting here. Nice to see you again!
| >
| > From the description, I understand that you want to publish an internal
web
| > site for external access using ISA Server 2004. The web site is hosted
on
| > the Linux Apache Server. If I am off base, please do let me know.
| >
| > To publish this internal web site, we can use either of the two
following
| > methods:
| >
| > Method 1:
| > Generally speaking, since SBS is a highly integrated server, the ports
| > 80/443/444 have already been occupied by the Default web site
(including
| > RWW/OWA and other components) and the companyweb. Here I assume the
default
| > web site can be accessed using http://www.domain.com on port 80. If you
| > want external users to be able to access this Apache web server also on
| > port 80, you can perform the following steps:
| >
| > 1. Click Start, point to Programs, point to Microsoft ISA Server, and
then
| > click ISA Management.
| >
| > 2. In the ISA 2004 management console, expand ISAServerName, where
| > ISAServerName is the name of your ISA 2004 server.
| >
| > 3. Click Firewall Policy. In the right-pane of the ISA 2004 management
| > console, click the Tasks tab, and then click Publish a Web Server under
| > Firewall Policy Tasks.
| >
| > 4. On the Welcome to the New Web Publishing Rule Wizard page, type a
| > descriptive name in the Web publishing rule name box, and then click
Next.
| >
| > 5. On the Select Rule Action page, click the Allow option, and then
click
| > Next.
| >
| > 6. On the Define Web site to Publish page, click Browse and then click
the
| > Web server that you want. Click to select the Send the original host
header
| > to the publishing server instead of the actual one (specified above)
check
| > box, and then click Next.
| >
| > 7. On the Public Name Details page, click This domain name (type
below): in
| > the Accept request for list. In the public name, type the domain name
for
| > example, abc.domain.com.
| >
| > Note: You may need to register a new Host Record for abc.domain.com at
your
| > ISP's DNS Server.
| >
| > 8. On the Select Web Listener page, select a Web listener from the list
| > that allows external networks access, and then click Next.
| >
| > 9. On the User Sets page, select All Users, click Next, and then click
| > Finish.
| >
| > 10. In the Firewall Policy pane of the ISA 2004 management console,
click
| > Apply to apply the changes.
| >
| > Then the external users will be able to access this website using
| > http://abc.domain.com, while the default website can be visited using
| > http://www.domain.com. Both of these two website are listening on port
80.
| >
| > Method 2:
| > If you want to use your default FQDN www.domain.com for the internal
web
| > site, you can use the server publishing rule. However, since the port
80
| > was already occupied, we may publish this Apache web site on port 81 or
| > whatever you like. That is to say, we can visit this web site using
| > http://www.domain.com:81. To do so, we should first create a new
protocol
| > based on port 81, and then create a new server publishing rule as
following:
| >
| > From: the External IP address of the ISA Server
| > To: the internal IP address of the Apache Server
| > Protocol: the new created protocol
| > Apply to: All users
| >
| > For your information:
| > Server publishing can be used to publish any kind of server which
| > followings the standard TCP/IP definition. For example, we can publish
FTP,
| > HTTP, HTTPS, SMTP, POP3, IMAP, SQL and such. Any kind of server build
based
| > on TCP/IP is possible to be published in this way.
| >
| > Hope the above information helps
| > Please feel free to let me know if there is anything I can do for you.
| >
| > Have a nice day! :)
| >
| > Best Regards
| > Edward Tian(MSFT)
| > Microsoft CSS Online Newsgroup Support
| >
| > Get Secure! - www.microsoft.com/security
| > ======================================================
| > This newsgroup only focuses on SBS technical issues. If you have issues
| > regarding other Microsoft products, you'd better post in the
corresponding
| > newsgroups so that they can be resolved in an efficient and timely
manner.
| > You can locate the newsgroup here:
| > http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
| >
| > When opening a new thread via the web interface, we recommend you check
the
| > "Notify me of replies" box to receive e-mail notifications when there
are
| > any updates in your thread. When responding to posts via your
newsreader,
| > please "Reply to Group" so that others may learn and benefit from your
| > issue.
| >
| > Microsoft engineers can only focus on one issue per thread. Although we
| > provide other information for your reference, we recommend you post
| > different incidents in different threads to keep the thread clean. In
doing
| > so, it will ensure your issues are resolved in a timely manner.
| >
| > For urgent issues, you may want to contact Microsoft CSS directly.
Please
| > check http://support.microsoft.com for regional support phone numbers.
| >
| > Any input or comments in this thread are highly appreciated.
| > ======================================================
| > This posting is provided "AS IS" with no warranties, and confers no
rights.
| >
| > --------------------
| > | Thread-Topic: web redirection to a Linux server using ISA 2004
| > | thread-index: AcXNLkK7nbyFt0jUQziFkgQ5nrO22Q==
| > | X-WBNR-Posting-Host: 220.234.172.107
| > | From: "=?Utf-8?B?T3JsYW5kbw==?=" <orlando_lister@xxxxxxxxx>
| > | Subject: web redirection to a Linux server using ISA 2004
| > | Date: Sun, 9 Oct 2005 17:05:02 -0700
| > | Lines: 5
| > | Message-ID: <B966A3E9-2774-4A62-9E98-1467FE5F2F79@xxxxxxxxxxxxx>
| > | MIME-Version: 1.0
| > | Content-Type: text/plain;
| > | charset="Utf-8"
| > | Content-Transfer-Encoding: 7bit
| > | X-Newsreader: Microsoft CDO for Windows 2000
| > | Content-Class: urn:content-classes:message
| > | Importance: normal
| > | Priority: normal
| > | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| > | Newsgroups: microsoft.public.windows.server.sbs
| > | NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
| > | Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA03.phx.gbl
| > | Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.windows.server.sbs:211536
| > | X-Tomcat-NG: microsoft.public.windows.server.sbs
| > |
| > | I have a new website hosted on a Linux Apache Server which is located
in
| > the
| > | internal network. it is now connected to my lan (cable modem - sbs
| > server
| > | 2003/isa 2004 with two nics, 1 external & 1 internal).I can access
this
| > | server internally using http://192.168.12.1, but how can I access it
| > | externally? TIA.
| > |
| >
| >
|

.



Relevant Pages

  • RE: w3wp.exe unable to start properly and mail delivery very slow
    ... I will be here waiting for your updates, please feel free to post back. ... Microsoft CSS Online Newsgroup Support ... This newsgroup only focuses on SBS technical issues. ... |> internal NIC as the DNS server on both client computer and SBS server. ...
    (microsoft.public.windows.server.sbs)
  • Re: Nagging Autorization issue for Companyweb after ISA04 install
    ... Check the companyweb CNAME entry in the DNS Server. ... Does the situation occur when you access companyweb from the ISA ... > 'Microsoft Firewall' service. ... > This newsgroup only focuses on SBS technical issues. ...
    (microsoft.public.windows.server.sbs)
  • Re: Email enable doc lib
    ... server to test the issue. ... Microsoft CSS Online Newsgroup Support ... This newsgroup only focuses on SBS technical issues. ... Please try to logon Public folder list using URL: ...
    (microsoft.public.windows.server.sbs)
  • RE: SMTPS - Exchange
    ... Microsoft CSS Online Newsgroup Support ... This newsgroup only focuses on SBS technical issues. ... If the Exchange server is listening on other port rather ...
    (microsoft.public.windows.server.sbs)
  • RE: Port Forwarding With 2 NIC Configuration
    ... Can SBS do 1-to-1 Natting? ... > and incoming/outgoing port, ... > automatically redirected from the SBS server to port 81 of the internal ... > Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)