Cannot connect to a remote object hosted in a window service

From: Julia (codewizard_at_012.net.il)
Date: 01/27/05


Date: Thu, 27 Jan 2005 13:40:09 +0200

Hi,

My client uses a remote object
when I host the remote object inside a windows application all seem to work
fine
but when I host the same object inside a windows service I get the following
error

" connection attempt failed because the connected party did not properly
respond after a period of time, or established connection failed because
connected host has failed to respond"

If the window service run on the same computer that it is running fine

Thanks.



Relevant Pages

  • Preventing computer name IP history storage
    ... connection window from storing the host computer name/IP ... Using an XP computer at a friend's house (client), ... connected to my home (host) computer using RD. ... computer was my windows logon password...the RD ...
    (microsoft.public.windowsxp.work_remotely)
  • Preventing computer name IP history storage
    ... >connection window from storing the host computer name/IP ... >Using an XP computer at a friend's house (client), ... >connected to my home (host) computer using RD. ... >computer was my windows logon password...the RD ...
    (microsoft.public.windowsxp.work_remotely)
  • Re: Windows 2000 Host and Windows ME Client ICS
    ... >Windows ME machine as a client using ICS. ... >On my Windows 2000 Pro host machine: ... >Ethernet adapter Local Area Connection: ...
    (microsoft.public.win2000.new_user)
  • Re: Windows 2000 Host and Windows ME Client ICS
    ... >Windows ME machine as a client using ICS. ... >On my Windows 2000 Pro host machine: ... >Ethernet adapter Local Area Connection: ...
    (microsoft.public.win2000.networking)
  • Cannot connect to a remote object hosted in a window service
    ... when I host the remote object inside a windows application all seem to work ... but when I host the same object inside a windows service I get the following ... " connection attempt failed because the connected party did not properly ...
    (microsoft.public.dotnet.framework.remoting)