Problem connecting Server/Client, TCP

[MaxPersson]

Hi guys! My first post here is ofcourse a little problem of mine! =) ive been looking pretty mutch everywhere, asking my proffesor and such, and we cant figure this out at all. I even analyzed the network trafic with Wireshark to see what was going on. No luck. So now im turning to you hardcore guys here! =)

Well to the problem. Im doing a really, REALLY simple chat client. (intending to control the mouse over ethernet). Where everything stops is when im trying to connect to the server.

On the client machine im running Vista using standard IPv6, and the Server im running XP Pro with IPv6. When launching the code below i can see from the network analyzing that it is actully sending packets and reciving to and from the server machine.

Then it gives me the most odd explenation ever.
"No connection could be made because the target machine activley refused it".

Ive tried to open up the network as mutch as possible to do a trial and error thing, but still no luck.

I dont even need to have my server app up and running. it still gives me the same message.

This is the Client code:

public void RunClient()
{    
try    
{        
Client = new TcpClient();        
Client.Connect("192.168.1.33", 50000);        
outputStream = Client.GetStream();        
Writer = new BinaryWriter(outputStream);    
}        
catch (Exception e) { MessageBox.Show(e.ToString()); }    }}
 
 
This is the servercode:
 
private void RunServer()
{    
TcpListener listener;        
try    
{        
IPAddress local = IPAddress.Parse("127.0.0.1");        
listener = new TcpListener(local, 50000);                        
listener.Start();        
while (true)        
{            
Connection = listener.AcceptSocket();            MessageBox.Show("Someone got connected."); ...
 

The servercode doesnt even reach the MessageBox.Show code. Seems like it is something external that is keeping the connection away. Anyone have any idea or could kick me in the right direction?

Thanks in advance for occupying your time =)

[RedSon]

...So now im turning to you hardcore guys here at The Code Project

I'm not sure you have the right place. This is TheScripts not The Code Project.

When you step through your code at what point does it break down? Perhaps you do not have any timeouts for your connections so the server never drops the first connection if it does not receive a packet. You should also make sure that your server side is multi threaded so that it can accept more then one connection from a client.

Can you let me know at what point it fails like what line number? And also try to post up your locals. Maybe that will help?

[MaxPersson]

hehe i saw that =) changed it ;)
either way.
im using a threaded server side since i thought it would be some kind of problem with that. but nope, no luck.

        private Socket Connection;
        private Thread readThread;
 
        private NetworkStream socketStream;
        private BinaryReader Reader;

That is the locals for the server.

But it seems not to be the problem since i can shutdown my server app and still it gives me the same error.

=(

it fails on line 6, clientside

[TRScheel]

hehe i saw that =) changed it ;)
either way.
im using a threaded server side since i thought it would be some kind of problem with that. but nope, no luck.

        private Socket Connection;
        private Thread readThread;
 
        private NetworkStream socketStream;
        private BinaryReader Reader;

That is the locals for the server.

But it seems not to be the problem since i can shutdown my server app and still it gives me the same error.

=(

it fails on line 6, clientside

I believe its your firewall. I had the same issue when coding something similiar.

[RedSon]

I think you might be using the wrong method call.

http://msdn2.microsoft.com/en-us/lib...52(VS.71).aspx

[TRScheel]

I think you might be using the wrong method call.

http://msdn2.microsoft.com/en-us/lib...52(VS.71).aspx

I dunno, I used nearly the same code and it worked for me

[Plater]

Then it gives me the most odd explenation ever.
"No connection could be made because the target machine activley refused it".

That message usually occurs when the client can FIND the server (ie the server responds with "yeah Iexist") and means you made it through the firewall*. But the port you are connecting on does not have anyone listening on it.
Say I have a server at 192.168.1.45 and my program is listening on port 5000 and nothing else listening.
If I tell my client to connect to 192.168.1.45:5001 and there is no firewall issues it will tell me "connection actively refused" because it could find my server but there was nothing listening on that port.

* Firewalls generally will NOT respond with anything if the port is not opened, thus having the "connection timed out" in an attempt to trick possibly malicious clients from knowing there is a computer there.

NOW THEN, I just double-checked and saw another problem:

IPAddress local = IPAddress.Parse("127.0.0.1");        
listener = new TcpListener(local, 50000);                        
listener.Start();   
 

This is only listening on localhost's ip (127.0.0.1) which means ANY other address will not connect to it.
You will want to use IPANY (it's a static under like IPAddress I think)