[lnkForumImage]
TotalShareware - Download Free Software
Confronta i prezzi di migliaia di prodotti.
Asp Forum
 Home | Login | Register | Search 


 

Forums >

microsoft.public.dotnet.framework.remoting

actively refused exception

eliasstmailbox-google

10/9/2004 4:10:00 AM

Hi all,
I´m having a problem with remoting in my application, it is a Windows
service, when I install it in a new machine(Windows XP SP 1) and try
to connect to it I get the "actively refused" exception(it doesn't
even work locally), but when I install Visual Studio .Net 2003 in the
machine, the application starts responding and works great, locally
and remotely, could someone please tell me what I'm missing?
2 Answers

Sam Santiago

10/9/2004 7:47:00 PM

0

This usually happens for several reasons:

1) The server application is not running prior to the client application.
Verify the server (in this case a service) is truly started an operational.

2) Name resolution. Try an IP address vs. a machine name. If that works,
then you have a name resolution issue. You can have your network admin
check DNS or WINS or whatever you are using to resolve names. You can also
update the HOSTS file in the C:\WINDOWS\SYSTEM32\DRIVERS\ETC director as
well.

3) Socket permissions. Check out this link regarding setting socket
permission via configuration:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/html/cpconconfiguringclientappli...

or check out the SocketPermission class:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemNetSocketPermissionClas...

4) Remoting configuration. You client and server are not using the same
port.

Thanks,

Sam
--
_______________________________
Sam Santiago
ssantiago@n0spam-SoftiTechture.com
http://www.SoftiTe...
_______________________________
"Elias Sanchez" <eliasstmailbox-google@yahoo.com> wrote in message
news:a48b303a.0410082010.3c9af56e@posting.google.com...
> Hi all,
> I´m having a problem with remoting in my application, it is a Windows
> service, when I install it in a new machine(Windows XP SP 1) and try
> to connect to it I get the "actively refused" exception(it doesn't
> even work locally), but when I install Visual Studio .Net 2003 in the
> machine, the application starts responding and works great, locally
> and remotely, could someone please tell me what I'm missing?

eliasstmailbox-google

10/10/2004 2:01:00 PM

0

Hi Sam,
Thank you for your reply, it turned out to be a configuration issue, I
was using programmatic configuration(I know first mistake), I changed
it to a file configuration and now it's working again(I still don't
know exactly what was causing it because it's the same configuration,
and it was working before, but I guess that's why the recommend the
use of a file)


"Sam Santiago" <ssantiago@n0spam-SoftiTechture.com> wrote in message news:<eIEPwijrEHA.1036@TK2MSFTNGP10.phx.gbl>...
> This usually happens for several reasons:
>
> 1) The server application is not running prior to the client application.
> Verify the server (in this case a service) is truly started an operational.
>
> 2) Name resolution. Try an IP address vs. a machine name. If that works,
> then you have a name resolution issue. You can have your network admin
> check DNS or WINS or whatever you are using to resolve names. You can also
> update the HOSTS file in the C:\WINDOWS\SYSTEM32\DRIVERS\ETC director as
> well.
>
> 3) Socket permissions. Check out this link regarding setting socket
> permission via configuration:
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/html/cpconconfiguringclientappli...
>
> or check out the SocketPermission class:
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemNetSocketPermissionClas...
>
> 4) Remoting configuration. You client and server are not using the same
> port.
>
> Thanks,
>
> Sam
> --
> _______________________________
> Sam Santiago
> ssantiago@n0spam-SoftiTechture.com
> http://www.SoftiTe...