retrieving multiple sockets from one TcpClient

Question

1.00/5 (1 vote)

See more:

If I have 2 connections being made to 1 TcpClient, is it possible to retrieve 2 different sockets from that one TcpClient? At the moment, as soon as the second connection is being made and getting the Socket from the client, the socket seems to get lost with the first connection, as I cannot send or receive over that socket anymore.

I am using the following code to retrieve the socket from the client.

C#

Socket socket = _tcpClient.Client;

Posted 18-Apr-12 4:35am

Andrew797

Add a Solution

Comments

Sergey Alexandrovich Kryukov 14-May-13 18:24pm

Please don't post non-answers as "solution". It can give you abuse reports which eventually may even lead to cancellation of your CodeProject membership.
Comment on any posts, reply to available comments, or use "Improve question" (above).
Also, keep in mind that members only get notifications on the post sent in reply to there posts.

Your inappropriate post as "solution" was removed due to abuse reports.

—SA

3 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Henning Dieterichs · Answer 1 · 2012-04-18T04:45:00

Solution 1

You cannot establish multiple connections from one client.
TCP is connection orientated, so the multiplicity is always 1:1 (Server-Socket : Client-Socket).

You should use two TcpClients for two connections.

Posted 18-Apr-12 4:45am

Henning Dieterichs

Comments

Nelek 19-Apr-12 19:10pm

The OP posted a solution to speak with you, the text is:
okay, so for instance if I have 2 instances of a class that is created, and both of them is required to connect to the same remote tcp client, it is not possible to retrieve a socket for both instances from that client? Is there any way to work around this? I do not constantly want to disconnect the one object to allow the other to connect and retrieve a socket for communication.

Henning Dieterichs 20-Apr-12 5:32am

I think you have misunderstood the concept of clients/servers (since my explanation is very short, I recommend you reading some network tutorials):
You cannot connect to a TcpClient, as a client is only a client. Use a TcpListener ( = Server), which can be bound to a port and is able to accept multiple clients (AcceptClient or something like this).
Then multiple TcpClients can connect to the same endpoint.

wizardzz · Answer 2 · 2012-04-19T06:03:00

Solution 3

You need to create another instance of the client. The ratio is 1 : 1 as Henning described, so you need as many instances on each side as connections you will have.

Posted 19-Apr-12 6:03am

wizardzz

Sergey Alexandrovich Kryukov · Answer 3 · 2013-05-14T12:29:00

You would need to make two connections (or any other number of connections you may need) using two separate instances of TcpClient, which is, basically, a wrapper around an instance of a Socket. Besides, you can do development either on the level of Socket objects, or TcpListener/TcpClient objects. You can mix both approaches in one project or solution, but in most cases there is no need for it. Those approaches are very close, with TcpListener/TcpClient approach being just a tiny bit of higher level, provided by .NET FCL for some extra convenience.

—SA