Direct Connection For Dummies

This page provides instructions on how to start a game using direct connection and information about common problems when trying to host a direct connection game.

Hosting Directly

A direct connection game is usually hosted on port 8080 with port 8085 for spectators. You may use other ports if you like.

• Determine your public IP address. It can be found on your coach overview page, alternatively visit a site such as http://whatismyip.com/.
  Note: For users who are behind a proxy, this may not be the correct IP address.

• Start the game with the Game Launcher (the (Play) button next to your team) or start the client manually.

• Tell the IP address and port to your opponent.

Using the Game Launcher

• Select No Proxy
• Set the Port
• Click on Launch as Server

Manually starting the client

• Select Net Server
• Set the Port
• Leave the Proxy option UNCHECKED
• Type in your team URL
• Click on Host Game

Connecting Directly

Connecting to a directly hosted game is basically no different from connecting to a game hosted via a proxy.

• Start the game with the Game Launcher (the (Play) button next to your team) or start the client manually.

Using the Game Launcher

• Select No Proxy
• Enter the host IP address as the Server
• Set the Port
• Click on Launch as Client

Manually starting the client

• Select Net Client
• Enter the host IP address as the Host
• Set the Port
• Leave the Proxy option UNCHECKED
• Type in your team URL
• Click on Join Game

Problems

Unfortunately hosting a direct connection game is not always as simple as it sounds. Listed here are a few common problems that can be the cause if your opponent cannot join to the game you hosted. The problems are almost always with the host.

This section is more technical, so it might be a bit difficult to understand unless you know some networking basics. Do not worry about the examples too much, they are only examples after all. Your router most likely has an entirely different looking user interface anyway.

Firewall

Your firewall must allow inbound access to the port you selected for hosting and to the spectator port if you want the spectators to connect. Most software firewalls on Windows ask you for permission to accept connections the first time you host. For example, the Windows XP/Vista Firewall asks if you want to unblock the application. Turning off your firewall is never a good option, but you might try to disable it temporarily to see if that was the cause for the problem.


Example firewall configuration on a TeleWell TW-EA515 ADSL modem/router.

• Rule Name: Used to describe the rule
• Time Schedule: When the rule is active
• Source/Destination IP and Netmask: All zeroes means any IP address
• Protocol: TCP, the protocol JavaBB uses
• Source/Destination ports: Any source port, 8080 and 8085 as destination ports for hosting
• Inbound/Outbound: Allow both inbound and outbound connections.

Port Forwarding

Port forwarding is necessary if you are behind a device (router), which employs NAT (Network Address Translation). NAT, in short, is a technique that hides usually private IP addresses behind a single public IP address. It is commonly used on home routers to set up a private home network.

If your computer is on a private network, you cannot host directly until you set up port forwarding in the router. You can verify this from your computer IP settings, by checking if your IP address is in the following ranges 10.x.x.x, 172.16.x.x – 172.31.x.x or 192.168.x.x. In Windows, you can do this by going to the Command Prompt and typing 'ipconfig'.


Example ipconfig output taken from a computer running Windows XP.

What you have to do is to configure your router to forward the traffic coming to ports 8080 and 8085 to your computer. Consult the router manual on how to do this. Another good resource is portforward.com, which has instructions on how to do port forwarding for a lot of different routers.


Example port forwarding configuration on a TeleWell TW-EA515 ADSL modem/router.

• Application: Used to describe the rule
• Time Schedule: When the rule is active
• Protocol: tcp, the protocol JavaBB uses
• External Port: Forward the traffic coming to ports 8080 and 8085
• Redirect Port: Forward the traffic to ports 8080 and 8085
• IP Address: The IP address to which the traffic is forwarded
• Interface: Assign the rule to the WAN interface