We've been developing a client/server app. using .NET remoting and we've 
finally reached the point where we're ready to deliver it to our QA guys. On 
the two development machines it is running well.

Our problem is that on any other machine although the server doesn't raise 
an exception it never actually opens the port.

netstat -an |find /i "listening"

 shows that the port (should be 49,152) isn't open on the problem machines.

The code we're using to open the channel is:

	IDictionary properties = new Hashtable();

	properties["port"] = ConnectionProvider.ourRegistryManager.Port.ToString();

	TcpChannel channel = new TcpChannel(properties,
				null,
				new IPAddressSinkProvider(new BinaryServerFormatterSinkProvider()));

	ChannelServices.RegisterChannel(channel, true);

Windows firewall pops up a message asking if we should allow the server to 
listen and we said yes. It's now listed in the exceptions tab.

So far the only commonality (we're checking this now) is that it seems to 
require Visual Studio to have been used to debug the applications. FWIW the 
applications don't need to be running under VS on the development machines.

Can anyone shed any light on this?