Ureader.com  
Microsoft software help and Community
   home   |   control panel login   |   archive   |  
 
platform
active.directory
adsi
adsi.iis-admin
base
com_ole
complus_mts
component_svcs
database
directx
gdi
graphics_mm
internet.client
internet.server
internet.server.isapi-dev
localization
mapi
messaging
msi
mslayerforunicode
multimedia
networking
networking.ipv6
sdk_install
security
shell
telephony.tapi_2
telephony.tapi_3
telephony.tsp
telephony.wte
tools
ui
ui_shell
win_base_svcs
win16
  
 
date: 6 Mar 2007 02:45:58 -0800,    group: microsoft.public.platformsdk.com_ole        back       


dadvise fails when client and server on different network   
Hi all,

I have tried running my client and server (on separate pcs) on the
same network, no domain without any problems. But when I place my
client(same pc) on a different network, trying to DAdvise (method
shown below), I get an error message stating that RPC Server is
unavailable.

Result = PIDataObject->DAdvise(&formatetc, 0, pSink,
&dwUpdateConnection);
	if(FAILED(Result))
	  throw "Failed to perform PIDataObject->DAdvise";

Is different configuration needed for client and server on different
networks? I have am using same user accounts and have given access and
launch permissions locally and remotely to Administrators, the chosen
user and System. I also give access permission to Anonymous Logon
because the client will complain that no permission is given to
Anonymous logon.

TIA for any help given.
Atiz
date: 6 Mar 2007 02:45:58 -0800   author:   Atiz

Re: dadvise fails when client and server on different network   
I have realised that it is the firewall that is causing the problem.
DCOM can work through different networks without any problems.
Even though the firewall allows all to pass through, you have to take
note of firewalls which do address translation because DCOM cannot
work if the firewall does that.

Quote:
" the client must be able to reach the server by its actual IP
address. You cannot use DCOM through firewalls that do address
translation (i.e. where a client connects to virtual address
198.252.145.1 that the firewall maps transparently to the server's
actual address of, say, 192.100.81.101). This is because DCOM stores
raw IP addresses in the interface marshaling packets and if the client
cannot connect to the address specified in the packet, it won't work."

You can find out more from
http://msdn2.microsoft.com/en-us/library/ms809327.aspx

Atiz
date: 7 Mar 2007 18:28:08 -0800   author:   Atiz

Google
 
Web ureader.com


    COPYRIGHT 2007, YARDI TECHNOLOGY LIMITED, ALL RIGHT RESERVE  |   contact us