ms sec fix caused SocketException : An attempt was made to access a socket in a way forbidden by its access permissions

[Les Caudle]

I've got code that's been working for years.

This is running on Win2003 Server whiled logged in as the admin.

When the MS sec fixes were installed last night, this code now fails with:

System.Net.Sock ets.SocketExcep tion: An attempt was made to access a socket in a
way forbidden by its access permissions

IDictionary props = new Hashtable();
props["name"] = "tcp";
props["port"] = 1234;
props["rejectRemoteRe quests"] = "true";
props["bindTo"]= "127.0.0.1" ;

BinaryServerFor matterSinkProvi der srv = new BinaryServerFor matterSinkProvi der();

TcpServerChanne l chnl = new TcpServerChanne l(props,srv);

ChannelServices .RegisterChanne l(chnl, false); // fails at this point
How can I resolve this?
--
Thanks in advance, Les Caudle

[Les Caudle]

Actually, it fails on the TcpServerChanne l chnl = new
TcpServerChanne l(props,srv); - and only on Win2003 Server.

As the user has admin priv, I don't see how it can fail to have proper
permissions.

Anyone have a clue - I'm dead in the water until I resolve this?

Thanks, Les Caudle

On Thu, 13 Mar 2008 09:56:25 -0500, Les Caudle <Do***********@ newsgroup.nospa m>
wrote:

>I've got code that's been working for years.

This is running on Win2003 Server whiled logged in as the admin.

When the MS sec fixes were installed last night, this code now fails with:

System.Net.Soc kets.SocketExce ption: An attempt was made to access a socket in a
way forbidden by its access permissions

IDictionary props = new Hashtable();
props["name"] = "tcp";
props["port"] = 1234;
props["rejectRemoteRe quests"] = "true";
props["bindTo"]= "127.0.0.1" ;

BinaryServerFo rmatterSinkProv ider srv = new BinaryServerFor matterSinkProvi der();

TcpServerChann el chnl = new TcpServerChanne l(props,srv);

ChannelService s.RegisterChann el(chnl, false); // fails at this point
How can I resolve this?