RE: OWA 2000 on a different IIS5 ?

  • From: "nimrod" <nimrodc@xxxxxxxxxxx>
  • To: "'[ExchangeList]'" <exchangelist@xxxxxxxxxxxxx>
  • Date: Wed, 6 Feb 2002 15:12:35 +0200

hi
i think there is very simple way to to it
just point the url on the /exchange site (on your iis) to m:/<your
domain>/mbx
where "m" disk is the virtual disk on the exchange server , you can replace
"m" with what drive leter you map to "m"


nimrod

-----Original Message-----
From: Lars Juliussen [mailto:Lars@xxxxxxxxxxxx]
Posted At: þâ 05 ôáøåàø 2002 20:49þ
Posted To: Inbox
Conversation: [exchangelist] OWA 2000 on a different IIS5 ?
Subject: [exchangelist] OWA 2000 on a different IIS5 ?


http://www.MSExchange.org/


Do anyone have a hint about this puzzle ???

This is the scenario.  Win 2000 network, 3 servers. 1 DC, 1 Exch2k, 1
IIS5.

There are only 4 ports open on the ADSL router(62.xxx.xxx.xxx). Requests
on port 21 is redirected to 192.168.1.4(DC) Requests on port 53 is
redirected to 192.168.1.4(DC) Requests on port 25 is redirected to
192.168.1.2(Exchange 2kSP2) Requests on port 80 is redirected to
192.168.1.3(IIS5)

My question is:

How do i make the Exchange 2000 SMTP virtual server on the 192.168.1.2
computer respond, when i logon from Internet Explorer on the
Webserver(192.168.1.3), from Outside the local network ?

I have tried a lot of different tings. The puzzle seems to be, that the
virtual SMTP server runs perfectly on the Exchange2000
machine(192.168.1.2). But one cant just COPY the content from the IIS 5.0
snapin on the Exchange2000 server(192.168.1.2), to the IIS 5.0 snapin on
the Webserver(192.168.1.3)

I have searched the internet for litteracy, describing just this scenario.
But i cant find anything on this specific scenario. Are there some
Exchange2K experts out there, who can solve this ??

Thanks in advance.

Lars J. Denmark


------------------------------------------------------
You are currently subscribed to this MSExchange.org Discussion List as:
nimrodc@xxxxxxxxxxx
To unsubscribe send a blank email to
$subst('Email.Unsub')

Other related posts: