NetSetMan Support

A.Wellner

Member

Registered: 2010-09-30

Posts: 1

Autostart kills 127.0.0.1 (loopback)

Hi,

I am currently testing a programm that makes use of local TCP connections via 127.0.0.1. One part of the program runs as a services which starts a GUI exe whenever a user logs in. Afterwards, the GUI connects to the service component via 127.0.0.1. The problem is that if the comuter starts NetSetMan (with autostart option), the local TCP connction frequently dies. If NetSetMan ist disabled/uninstalled everything works as expected.

What exactly may trigger such a situation where local loopback connections are disconnected? Sometimes I have to retry to establish connection for about 2min. until it works...

Thanks,
Alex.

NetSetMan Support

Administrator

Registered: 2005-08-06

Posts: 1,878

Re: Autostart kills 127.0.0.1 (loopback)

To be honest, I doubt that this problen lies within NSM or NSM Service. I understand that it appears you've experienced some correlation. However, having the knowledge about how NSM works I assume it might have been just a coincidence.

Let me try to explain: NSM doesn't change any system settings nor affects them by being installed or running. The only moment when NSM changes system settings is the moment the user activates a profile. NSM doesn't install any drivers, nor does it link into or affect in any other way network layers.

Because you're mentioning a service component of yours the NSM Service comes into my mind. But still: even if NSM is used together with the NSM Service, they communicate over named pipes not disturbing any other system communication.

I hope this helps you in some way with your problem.