WinSock Internet

Well i need to make a chat program work on LAN which isn't a problem.

However, I need to be able to log into the chat room off-site. The chat works by having one server and the clients connect to the server as needed. Then they can all chat.

Well i figured i could set up port forwarding to allow me to connect remotely to my chat server, but I do not know the router information to log into it.

Is there any way I can remotely connect to my server without setting up port forwarding through the router settings?

Thanks,
Philly0494

PS: my chat program is written completely in vb6

If the ports aren't open/forwarded on your router then, no. You will also need to ensure a firewall isn't running or blocking that port.

What kind of router is it?

Most router IPs are: http://192.168.1.1, and default login is something like: admin/admin, administrator/admin, etc.

You can find your router's IP address by opening a command prompt and typing "ipconfig /all". Then look at the Default Gateway.

If your server is a web server, port 80 should already be open.

well how do i make my winsock server a web server?

is that how trojans do it?

If the port isn't forwarded on the server machine, or DMZ option isn't enabled (opens all ports) then they will not be able to connect to the server, doesn't matter what port you use.

Quote:

---

Originally Posted by Philly0494

well how do i make my winsock server a web server?

is that how trojans do it?

---

Post 3 already told you.

Just have your server Winsock listen on port 80. However, only one application at a time can use the same port number so if your server is on port 80 then your browser won't be able to go to the Internet

Just to elaborate on JMS's comment. With TCP there are 2 Port numbers, the Local Port on the Server, and the Local Port on the client. TCP uses those two ports to identify the applications for communications. The Client connects to a Remote Port which is the Server's Local Port. The Server then uses the Clients Local Port as its Remote Port.

So if the Server is listening on Port 80 the Client connects to Remote Port 80, TCP will automatically allocate the Local Port for the Client. So the Cliient is not actually using Local Port 80 and will still be able to access other servers listening on Port 80 (eg Web Servers)

eg Once communications are established:

Client: Local Port= 20134, Remote Port= 80
Server: Local Port= 80, Remote Port= 20134