[RESOLVED] Client / Server issue

Ello,

I've came across a little problem with my tcp / ip server.
My client can connect to it with 127.0.0.1 ( localhost ), and 192.168.0.X, but every remote connection fails to connect. Any suggestions?

Here's the connection rituals:

Server

Code:

---

            listener = New System.Net.Sockets.TcpListener(System.Net.IPAddress.Any, Port)
            listener.Start()
            listenThread = New System.Threading.Thread(AddressOf doListen)
            listenThread.IsBackground = True
            listenThread.Start()

---

Client

Code:

---

            client = New System.Net.Sockets.TcpClient(IP, Port)
            client.GetStream.BeginRead(readBuffer, 0, BYTES_TO_READ, AddressOf DoRead, Nothing)

---

If there's any more necessary details that might help solve the problem, please let me know and I'll post them up.

Thanks in advance :)

What is the error that you get when you try the remote connection?

Connection timeout. No answer from the host between some period of time.
I've tried this with me having the client and server and connecting to my ip but not through localhost (62.78.XXX.XXX), me having the client and my friend having the server and visa verce, shutting down both firewalls completely, yet the problem persists. I'm using vista32 (unfortunately).

Is the computer running the server behind a router?

I've never took the effort to learn about routers and their purposes, but I seem to have a router at least since http://192.168.0.1/ redirects to http://192.168.0.1/index.asp with some motorola page asking me for pass / name I really don't have.

So if that's the problem, how to solve it? If solving it includes knowing the router password, is there a way around?

You need to forward the port you're using in the router. And yes it would require you to know the router password. Here is a thread on the same problem, it'll tell you what you need to do.

There is no other solution if you're going to run the server on a computer behind a router.

Atheist is correct, however most people dont change there default router passwords. I'd google your router make and see if you can find the default password.

Pino

Problem solved by reseting the router, and by doing that reseting the default password as well. Works a treat now, cheers.