Re: ms sec fix caused SocketException: An attempt was made to access a socket in a way forbidden by its access permissions
- From: Les Caudle <DotNetWannabe@xxxxxxxxxxxxxxxx>
- Date: Thu, 13 Mar 2008 12:40:57 -0500
Actually, it fails on the TcpServerChannel chnl = new
TcpServerChannel(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 <DotNetWannabe@xxxxxxxxxxxxxxxx>
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.Sockets.SocketException: 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["rejectRemoteRequests"] = "true";
props["bindTo"]= "127.0.0.1";
BinaryServerFormatterSinkProvider srv = new BinaryServerFormatterSinkProvider();
TcpServerChannel chnl = new TcpServerChannel(props,srv);
ChannelServices.RegisterChannel(chnl, false); // fails at this point
How can I resolve this?
.
- Follow-Ups:
- References:
- Prev by Date: Re: EventWaitHandle.OpenExisting oddity
- Next by Date: Re: Factory method question
- Previous by thread: ms sec fix caused SocketException: An attempt was made to access a socket in a way forbidden by its access permissions
- Next by thread: Re: ms sec fix caused SocketException: An attempt was made to access a socket in a way forbidden by its access permissions
- Index(es):
Relevant Pages
|
