RE: publishing a DCOM application
- From: Nicholas Palmer <NICK@xxxxxxxxxxx>
- To: "'[ISAserver.org Discussion List]'" <isalist@xxxxxxxxxxxxx>
- Date: Wed, 21 Nov 2001 09:34:40 -0800
Actually, its quite simple to publish a DCOM application behind a firewall.
You just have to use the correct protocol. Search Technet for some called
Com Internet Services (CIS). There is a white paper by someone named Mark
Levy I believe that describes in detail all that is required. Basically,
instead of using the normal TCP protocol for DCOM, you use a special
Tunneling TCP protocol that puts the DCOM info into HTTP/HTML. So the only
thing that needs to be open on your ISA server is port 80, which if you are
already publishing a web site, will already be open. Please note, that you
cannot use Web publishing, but only Server publishing to publish the server
that is the DCOM server. This has to with the fact the ISA and Web
publishing appear to examine these packets and even though they are HTTP
packets, it considers them invalid and the process does not work. Server
publishing just passes the packets right on thru. I learned this the hard
way after spending almost three weeks working with MS tech support trying to
figure this out. Also, you need to make sure that you have name resolution
to the published server working correctly, as DCOM is very picking about
names of servers. There is a little DCOM test utility that you can download
from MS called DCOMTEST that you can use to test your setup. If this guy
works, your app should also work.
Nick.
P.S. While this will work fine, my understanding from MS is that the whole
CIS thing is going to get replaced by the .NET stuff eventually.
-----Original Message-----
From: Craft, Steve [mailto:SCraft@xxxxxxxxxxx]
Sent: Wednesday, November 21, 2001 8:08 AM
To: [ISAserver.org Discussion List]
Subject: [isalist] RE: publishing a DCOM application
http://www.ISAserver.org
The short answer is don't do it. Because of the "chatty" and synchronous
nature of DCOM, you will have to open a few hundred ports on the ISA box.
Actually no matter what firewall product you use you would have to do this.
If clients really just need rows of data, you will get more mileage out of
enabling SQLXML on your MS SQL Server and just web publishing the server and
they can get the data back as an XML document (very cool and *faster* than
ADO!).
If clients need to get at objects, go with the SOAP Toolkit 2.0; there is
some functionality in there to make SOAP wrappers for your COM objects, and
instead of doing a CreateObjectEX your clients make a HTTP call which of
course you can publish with web publishing on ISA.
Search on MSDN or MSKB for DCOM and PORT and you will see the list of stuff
that you will have to open in both directions; it's a lot.
-----Original Message-----
Subject: publishing a DCOM application
From: "Richard Robert" <richard.robert@xxxxxxxxxxx>
Date: Tue, 20 Nov 2001 06:56:36 -0700
X-Message-Number: 11
publishing a DCOM application
Does anyone know if it is possible to server publish a DCOM application
behind ISA?
what protocol definitions
would need to be set up for the server publishing rule?
------------------------------------------------------
You are currently subscribed to this ISAserver.org Discussion List as:
nick@xxxxxxxxxxx
To unsubscribe send a blank email to $subst('Email.Unsub')
Other related posts:
