Allowing connections outside of LAN

[ben1996123]

OK, it is listening for connections on any interface.

From your server can your client connect to 127.0.0.1 on port 1234?
No: The client or server code is faulty
Yes: Carry on

From a machine on your LAN other than the server can your client connect to server's LAN IP address?
No: The problem is quite probably your server's own firewall. Windows firewall or anti-virus perhaps?
Yes: Carry on

Install Wireshark or a similar tool on your server machine. Start a capture. For a machine outside your network can your client connect to the server?
Yes: Problem solved
No: Carry on

Did you see the attempt to connect to port 1234 in Wireshark?
No: Problem is the firewall or port forwarding from your external connection.
Yes: Problem may still be a firewall on the server itself if it restricts by source IP address.

Thanks for that information, I just tried to connect to my server on another computer on my network (using telnet in command prompt because my client program doesn't work on windows xp yet) and that worked when I connected to 192.168.0.4. I've installed wireshark so I can test with another computer outside my network (well, as soon as someone comes on skype for me to test it with ). I just noticed that my antivirus program was blocking some TCP connections, so I allowed port 1234 through. Hopefully I can get it to work soon :/

[ben1996123]

Yay it works

Only thing that's concerning me now is... is the connection safe? I've had to allow port 1234 to connect through my antivirus and firewall, and there's no password on the server. Is there a simple way of adding a password to the server so I can just tell the password to whoever I want to be able to connect?

[prof.ebral]

Once a client connects they are connected. The password method would limit their functionality until the correct password is sent by the client. Just force the client into a password loop until they send the correct password and then disconnect them after failed atempts.

For an added security layer you can create a 'too many attempts' feature that prevents an IP from going past the listening method if they have attempted too many passwords. I'd probably use an XML file for this so you can store the IP and a time stamp, and when a connection attempt is made run a check on their IP and if it is found close the connection. Using a similar feature you could allow IPs to bypass the password method for a limited time.

[ben1996123]

Once a client connects they are connected. The password method would limit their functionality until the correct password is sent by the client. Just force the client into a password loop until they send the correct password and then disconnect them after failed atempts.

For an added security layer you can create a 'too many attempts' feature that prevents an IP from going past the listening method if they have attempted too many passwords. I'd probably use an XML file for this so you can store the IP and a time stamp, and when a connection attempt is made run a check on their IP and if it is found close the connection. Using a similar feature you could allow IPs to bypass the password method for a limited time.

Ok, thanks for all the help