Problem with Socket (connect to domain name or server name)

Question

0.00/5 (No votes)

See more:

Hi, I am trying to use Socket object in my application. The code can simply seen below.

//Using TcpClient Class
TcpClient tcpClient = new TcpClient();
tcpClient.Connect("http://myserver.com", 123);
// we can also say 
tcpClient.Connect(IPAddress.Parse("125.54.10.25"), 123);

//Using Socket Class
Socket client = new Socket(AddressFamily.InterNetwork, SocketType.Stream, ProtocolType.Tcp);
client.Connect("http://myserver.com", 123);
//or

client.Connect(IPAddress.Parse("125.54.10.25"), 123);

When using Socket I can't connect to the server over the Internet with such configuration

(AddressFamily.InterNetwork, SocketType.Stream, ProtocolType.Tcp)

So, what is the right way of AddressFamily, SocketType and ProtocolType?

Posted 9-Dec-11 22:04pm

adadero

Updated 9-Dec-11 22:50pm

v2

Add a Solution

2 solutions

Solution 1

You could try giving a valid IP address:

125.54.10.0.0

is not valid - it has too many number blocks for IPV4 (which has four blocks, "125.54.10.0") or it needs colons for IPV6 (which has six number blocks "125:54:10: 0: 0: 0")

Posted 9-Dec-11 22:37pm

OriginalGriff

Comments

adadero 10-Dec-11 4:53am

I have improved my question, the IP Address has five blocks and now it remains four. With TcpClient I can connect over the internet using a domain name and IPV4. What's the problem with the Socket Object?

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)

Robin Rizvi · Accepted Answer · 2011-12-10T07:34:00

Solution 2

client.Connect("http://myserver.com", 123);

try changing this to:

client.Connect("myserver.com", 123);

I don't think that this would prove of any use, its just that there is no need to specify http there when we are explicitly mentioning the port.

Posted 10-Dec-11 7:34am

Robin Rizvi

Comments

adadero 11-Dec-11 2:26am

Thanks for the reply. It's now solved. Thanks for helping me.

Robin Rizvi 11-Dec-11 4:23am

Happy to help