Sockets firewall problem

[Boni]

Dear all,
I am trying too use sockets for IPC communication on one and the same
machine. When following code is executed windows firewall pops up. Is there
any possibility to use sockets without a risk to be blocked by firewall.
private void ListenIPC( ){

while(true){

TcpListener tcpListener = new TcpListener(10);

tcpListener.Start();

Socket socketForClient = tcpListener.AcceptSocket();


if (socketForClient.Connected) ...

 

[Carl Daniel [VC++ MVP]]

Dear all,
I am trying too use sockets for IPC communication on one and the same
machine. When following code is executed windows firewall pops up. Is
there any possibility to use sockets without a risk to be blocked by
firewall.

You need to use the Windows firewall API to open a port to yourself to make
it work in all cases.

See
http://msdn.microsoft.com/library/en-us/ics/ics/exercising_the_firewall.asp?frame=true

Yes, it's a pain.

-cd

 

[Boni]

Hi Carl,
is there any simple sort of IPC between managed and unmanaged on local
machine which is bidirectional, fast and don't care firewalls?
Thanks a lot,
Boni

 

[Carl Daniel [VC++ MVP]]

Hi Carl,
is there any simple sort of IPC between managed and unmanaged on local
machine which is bidirectional, fast and don't care firewalls?

Named pipes would seem a logical choice. Another option would be something
custom built using shared memory.

-cd

 

[Guest]

Named pipes would seem a logical choice. Another option would be something

custom built using shared memory.

These articles might help you.
http://www.codeproject.com/csharp/dotnetnamedpipespart1.asp
http://www.codeproject.com/csharp/dotnetnamedpipespart2.asp
http://www.codeproject.com/threads/NamedPipesTracing.asp
http://www.codeproject.com/threads/anonpipe1.asp

The .NET articles are in C#. if you use MC++ or C++/CLI for your managed app
you can simply translate them. the classes and methods stay the same.

--

Kind regards,
Bruno.
(e-mail address removed)
Remove only "_nos_pam"