My understanding is that DCOM is very sensitive to matching names and IP
addresses. In the first case, the two machines have the same names, so I
think this will cause DCOM problems. That's probably why the second case
succeeds.

Also, just for the your networks sake, having two machines with the same
name is probably not a good idea also.

Nick.

-----Original Message-----
From: Utthandi Thirunavukkarasu [mailto:utthandiPCDOH.WPC.FRCO.COM]
Sent: Wednesday, January 08, 2003 10:20 AM
To: DCOMDISCUSS.MICROSOFT.COM
Subject: DCOM and intranet question

I have a question concerning DCOM object resolution in a network
environment. Please consider the following network configuration.

-----------------------------------------------------------
-----------------------------------------------------------
                  Machine A
Machine B

   Machine Name : D200 Machine Name :
D200
   Workgroup Name : WORKGROUP Workgroup Name : WORKGROUP

   IP Address : 192.168.78.200 IP Address :
192.168.79.200
   Subnet mask : 255.255.255.0 Subnet mask :
255.255.255.0
   Default gateway : 192.168.78.29 Default gateway :
192.168.79.29

-----------------------------------------------------------
-----------------------------------------------------------
                    |
|
                    |
|
                    | -----------------------
|
                    ----------------------- ROUTER ------------
                                           ----------------------

In the above case, if the client on Machine A connects to a server on
Machine B, it succeeds. Unfortunately, when the client on Machine A
registers for callbacks via AtlAdvise, it fails with an error 0x80070776
(The object exporter specified was not found).

Now consider the following. That is just change the machine name and
workgroup name to be unique. No other network information is changed.

-----------------------------------------------------------
-----------------------------------------------------------
                  Machine A
Machine B

   Machine Name : W78D200 Machine Name :
W79D200
   Workgroup Name : W78 Workgroup Name :
W79

   IP Address : 192.168.78.200 IP Address :
192.168.79.200
   Subnet mask : 255.255.255.0 Subnet mask :
255.255.255.0
   Default gateway : 192.168.78.29 Default gateway :
192.168.79.29

-----------------------------------------------------------
-----------------------------------------------------------
                    |
|
                    |
|
                    | -----------------------
|
                    ----------------------- ROUTER ------------
                                           ----------------------

In this case, if the clinet on Machine A connects to a server on Machine B,
it succeeds. Also, when the client on Machine A registers for callbacks via
AtlAdvise, it succeeds.

NOTE: In both the cases, Machine A connects to the server on Machine B by
specifing the Machin B's Ip address (ie 192.168.79.200) in the
CoCreateInstanceEx fun.

What Iam wondering here is how by just making the machine name and workgroup
name to be unique, AtlAdvise succeeds. I don't see any where in my code
using
the machine name. Always ip address is used whenever DCOM apil needs those
information.

Are there any DCOM gurus out there have faced this kind of problem before?
Any kind of information are appreciated. Thanks in advance to your time and
response.

----------------------------------------------------------------
Users Guide http://discuss.microsoft.com/archives/mailfaq.asp
contains important info. Save time, search the archives at
http://discuss.microsoft.com/archives/index.html . To unsubscribe,
mailto:DCOM-signoff-requestDISCUSS.MICROSOFT.COM

----------------------------------------------------------------
Users Guide http://discuss.microsoft.com/archives/mailfaq.asp
contains important info. Save time, search the archives at
http://discuss.microsoft.com/archives/index.html .
To unsubscribe, mailto:DCOM-signoff-requestDISCUSS.MICROSOFT.COM

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]