The problem with your code is that you will not get all the data if the data size is bigger than the buffer size (1024 bytes in your case) so you have to Read the stream inside the loop. Then you can Write all the data inside a MemoryStream until the end of the NetworkStream. … Read more
The no route error indicates that when the TCP connection was attempted, the connection failed because the underlying protocol software could not find a network node to network node route to the designated target node. The fix is somewhat operating system dependent but it mainly requires you to set up your routing tables so that … Read more
[UPDATE 17.03.2020: Microsoft has released SQL Server 2019 CU3 with an Ubuntu 18.04 repository. See: https://techcommunity.microsoft.com/t5/sql-server/sql-server-2019-now-available-on-ubuntu-18-04-supported-on-sles/ba-p/1232210 . I hope this is now fully compatible without any ssl problems. Haven’t tested it jet.] Reverting to 14.0.3192.2-2 helps. But it’s possible to solve the problem also using the method indicated by Ola774, not only in case of … Read more
First, I recommend that you use WCF, .NET Remoting, or some other higher-level communication abstraction. The learning curve for “simple” sockets is nearly as high as WCF, because there are so many non-obvious pitfalls when using TCP/IP directly. If you decide to continue down the TCP/IP path, then review my .NET TCP/IP FAQ, particularly the … Read more
Networking code is notoriously difficult to write, test and debug. You often have lots of things to consider such as: what “endian” will you use for the data that is exchanged (Intel x86/x64 is based on little-endian) – systems that use big-endian can still read data that is in little-endian (and vice versa), but they … Read more
Looks like the problem that you have is that threads will block while acquiring the lock, so your method is not completely async. To solve this you can use SemaphoreSlim.WaitAsync private readonly SemaphoreSlim readLock = new SemaphoreSlim(1, 1); public async Task UpdateDetailsAsync() { //I want every request to wait their turn before requesting (using the … Read more
I wouldn’t recommend you to try write just for testing the socket. And don’t relay on .NET’s Connected property either. If you want to know if the remote end point is still active, you can use TcpConnectionInformation: TcpClient client = new TcpClient(host, port); IPGlobalProperties ipProperties = IPGlobalProperties.GetIPGlobalProperties(); TcpConnectionInformation[] tcpConnections = ipProperties.GetActiveTcpConnections().Where(x => x.LocalEndPoint.Equals(client.Client.LocalEndPoint) && x.RemoteEndPoint.Equals(client.Client.RemoteEndPoint)).ToArray(); … Read more
Here is a generic example to send objects between client and server using Json.Net. It uses NewLine char as separator. So All you need is to create StreamReader and StreamWriter from network streams and to use ReadLine and WriteLine methods…. (PS: Since Json.Net escapes NewLine char in serialization, messages containing it doesn’t cause problems…) void … Read more
You would need to use the async BeginConnect method of TcpClient instead of attempting to connect synchronously, which is what the constructor does. Something like this: var client = new TcpClient(); var result = client.BeginConnect(“remotehost”, this.Port, null, null); var success = result.AsyncWaitHandle.WaitOne(TimeSpan.FromSeconds(1)); if (!success) { throw new Exception(“Failed to connect.”); } // we have connected … Read more
Since you’re using a TcpClient, that means you’re checking open TCP ports. There are lots of good objects available in the System.Net.NetworkInformation namespace. Use the IPGlobalProperties object to get to an array of TcpConnectionInformation objects, which you can then interrogate about endpoint IP and port. int port = 456; //<— This is your value bool … Read more