When using .net remoting over tcp what could cause the non blocking socket
exception error. I receive the error at diffrent times.

Ricky

the exact message I receive is
A Non-blocking socket operation could not be completed immediately
I am using remoting over a tcp channel, this error does not occur on all
machines just a select few.

Ricky



Show quoteHide quote

Hi Ricky,

Thanks for posting!

For the current issue, my understanding is that the "A Non-blocking socket
operation could not be completed immediately" error is encountered when you
using the .NET Remoting application. If I have misunderstood anything,
please let me know.

As far as I know, the error belongs to WinSock error. Actually, the Winsock
error relates to communication errors encountered with Ethernet Devices or
the setting of these devices. It is good way to contact your MIS/IT
department for resolving these errors. For example, some specific firewall
issues or networking issues will lead to the error. However, the error
isn't caused by the .NET Remoting application itself.

I appreciate your understanding!

Regards,

Yuan Ren
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

resource leak issues in win xp sp2 w .net 2.0
2.0: Nested configuration data
checksignature always returning false
.NET 1.1 created event log has only "Not available" properties
HashTable stores whole object as Key NOT the result of calling GetHashCode on the object when you do