Bibor
Doomsday Machine
I saw some posts about problems with setting up lan games so here are some useful tips:
LAN GAMES
Connecting the computers:
1. There are two types of cables for LAN connection. If you are using computer to computer connection without a Hub, use a CROSSLINK cable.
If you use a hub or switching hub, use an ETHERNET cable. These two types of cables are basically the same, except that the end connectors (RJ-45) have the colored cables set in different layout.
The easiest way do tell a crosslink cable from an ethernet one is to take the two ends of the cable (the connectors) and look at them. If the small cables are of the same pattern (example: red-white-blue-brown etc.) then it's a ethernet cable. If not - its a crosslink cable (or someone messed up while making the cable
).
2. HUBs. Just plug in the ethernet cables, connect the switching hub to AC power, and for the hardware part - you are done. It's irrelevant in what order are the cables connected.
Note #1: remember that in a hub, one port is usually reserved for hub to hub (or router) connection, so don't use it for computers. Effectively, with a 8-port hub you have 7 ports for computers. This one port will be shown at least in the hub manual (usually marked with "X" or "UPLINK".
Note #2: The layer 3 (and many level 2) can be configured by entering its ip address into internet explorer. The layer # (type) and possible setup address of the hub will be in the manual. Example: I type in http://192.168.2.1 for my hub in Internet explorer.
3. DHCP-enabled LAN with shared internet connection
A DHCP service is a service (system program) running on your computer (and eating up some resources) that gives your computer an ability do designate IP addresses to other computers on your network.
The easiest way to set up a DHCP service automatically is by sharing an internet connection. This is the only way to create it on WinXP Home without messing up something.
If you want to share your internet connection with other computers under Windows XP you have to "enable internet connection sharing" by right-clicking your internet connection on the computer that has the modem. What Windows XP will now do is set up a DHCP service, set up a NAT machine, share the connection and change your LAN CARD IP address (not the modem's or cable modem's IP) to 192.168.0.1.
Now at all other computers put "get IP address automatically" in the LAN card TCP/IP settings.
Note: Hub has nothing to do with IP addresses. It will work whether you use DHCP or static IP address System. The only exception of this rule is if it is a Layer3 switching hub, which has its own IP address (see below). If this is the case, you must use static ip addresses or mess with the hub settings.
Very important: only ONE of the computers can have the internet connection shared and ONLY ONE computer can be the DHCP server. Fail to take care on this one and you will be crying hysterically for the rest of the night.
4. you are using a wireless network (via access point or directly)
This is just too complicated to explain it right now. If anyone has questions about this, feel free to PM me.
5. Using a static set of IP addresses.- If you use a combination of WinXP and Win98 or win98-only network, use static IP addresses. This is the easiest way to do it. Just decide which computer will have which IP address and put these numbers into the TCP/IP configuration under "IP address".
The IP address is a set of 12 numbers split into 4 three-number groups. Each group of numbers can have a value from 0 to 255. Example: 182.25.0.255. A really important thing to note here is that the IP addresses must lay on the same subnet - for beginners - the first three groups of numbers must be the same for all computers. Example: 192.168.0.1, 192.168.0.2, 192.168.0.3 etc.
The number of IP address has nothing to do with speed of computers, who's turn will be first etc. its just a number describing your network adapter.
Note: Some hubs (layer 3) have their own static ip address. If this is the case, it will be shown in the manual. If so, your computers have to *obey* the hub's subnet. Example: I have an Wi-fi access point/switching hub in one. Its address is 192.168.2.1. Unless i want to mess with its settings, i have to give my computers the following IPs: 192.168.2.2, 192.168.2.3 etc. or else the connection with hub won't work.
Note: A subnet is a numerical "key" to the IP address it is bind to. Its basic purpose is to designate which number group of the IP address that can "see" each other. Example: the address is IP 192.168.0.1. Its subnet is 255.255.255.0. This means that the following IPs can see each other192.168.0.2, 192.168.0.3... 192.168.0.255. If the subnet would be 255.255.0.0 the following IPs would see each other 192.168.0.1, 192.168.1.1, 192.168.0.2, ... 192.168.255.255. Tha'ts why it is called a subnet mask - it creates a sub-network which is masked from all other sub-networks.
6. Setting up a static IP address LAN with Internet connection
Under WinXP, if you share the internet connection, the DHCP service will still be up, and the IP address will be changed to 192.168.0.1. However, if you want to use a static ip address system, it's okay (DHCP service will still be running though, you can't help it). Just follow the above configuration in section 5.
AND
Tell your coleagues the DNS (Domain Name Server) and Default Gateway IPs. Not surprisingly, the DNS and Default Gateway IP is exactly the same IP that the Internet connection shared computer has.
Thus, if the internet connection shared computer's lan card IP (not the modem's IP) is: 192.168.0.1, all other computers must open their TCP/IP setup at their Lan card settings and enter the following:
Primary DNS: 192.168.0.1.
Default Gateway: 192.168.0.1.
The best way to tell if the shared internet connection is working is by opening the "command prompt" on all computers and typing in "TRACERT www.google.com". It will start popping out some ip addresses, miliseconds and names of servers. If miliseconds are all numbers, never the sign * (asterisk), the connection is cool.
How all this affects the CIV3 game?
IF you are the system administrator of the LAN party, tell your coleagues whether the server is DHCP or static ip. If latter is the case, tell them their IP address.
If you are not a system administrator of the LAN party, double check your IP (just in case). The best way to do so (even if you used fixed IP) is to open the command prompt or and type in "IPCONFIG". the IP address will be shown there. If you have multiple network adapters, the one with the 192.168.X.X is probably the right one. This is true for both DHCP and static IP address systems.
Second, if you are not connected to internet, CIV3 will say "connecting to Gamespy" but will eventually give up. When it gives up, click the "refresh" button" or type in the IP address manually. The game *will* work without connecting to Gamespy.
Note: If your connection is FIREWALLED, CIV3 will show the room, settings, let the players in, but the game will not start (it will freeze). Since there's no need for LAN to be firewalled (only the Internet connection should be) - turn OFF the firewall on your LAN card. Internet games will not start when firewalled with default settings from Windows XP. See Chieftess' sticky post on this one
Note: Don't use Gamespy software for LAN games.
Hope this helps
- bibor aka Kirby
P.s. corrections, comments are most welcome
LAN GAMES
Connecting the computers:
1. There are two types of cables for LAN connection. If you are using computer to computer connection without a Hub, use a CROSSLINK cable.
If you use a hub or switching hub, use an ETHERNET cable. These two types of cables are basically the same, except that the end connectors (RJ-45) have the colored cables set in different layout.
The easiest way do tell a crosslink cable from an ethernet one is to take the two ends of the cable (the connectors) and look at them. If the small cables are of the same pattern (example: red-white-blue-brown etc.) then it's a ethernet cable. If not - its a crosslink cable (or someone messed up while making the cable
).2. HUBs. Just plug in the ethernet cables, connect the switching hub to AC power, and for the hardware part - you are done. It's irrelevant in what order are the cables connected.
Note #1: remember that in a hub, one port is usually reserved for hub to hub (or router) connection, so don't use it for computers. Effectively, with a 8-port hub you have 7 ports for computers. This one port will be shown at least in the hub manual (usually marked with "X" or "UPLINK".
Note #2: The layer 3 (and many level 2) can be configured by entering its ip address into internet explorer. The layer # (type) and possible setup address of the hub will be in the manual. Example: I type in http://192.168.2.1 for my hub in Internet explorer.
3. DHCP-enabled LAN with shared internet connection
A DHCP service is a service (system program) running on your computer (and eating up some resources) that gives your computer an ability do designate IP addresses to other computers on your network.
The easiest way to set up a DHCP service automatically is by sharing an internet connection. This is the only way to create it on WinXP Home without messing up something.
If you want to share your internet connection with other computers under Windows XP you have to "enable internet connection sharing" by right-clicking your internet connection on the computer that has the modem. What Windows XP will now do is set up a DHCP service, set up a NAT machine, share the connection and change your LAN CARD IP address (not the modem's or cable modem's IP) to 192.168.0.1.
Now at all other computers put "get IP address automatically" in the LAN card TCP/IP settings.
Note: Hub has nothing to do with IP addresses. It will work whether you use DHCP or static IP address System. The only exception of this rule is if it is a Layer3 switching hub, which has its own IP address (see below). If this is the case, you must use static ip addresses or mess with the hub settings.
Very important: only ONE of the computers can have the internet connection shared and ONLY ONE computer can be the DHCP server. Fail to take care on this one and you will be crying hysterically for the rest of the night.
4. you are using a wireless network (via access point or directly)
This is just too complicated to explain it right now. If anyone has questions about this, feel free to PM me.
5. Using a static set of IP addresses.- If you use a combination of WinXP and Win98 or win98-only network, use static IP addresses. This is the easiest way to do it. Just decide which computer will have which IP address and put these numbers into the TCP/IP configuration under "IP address".
The IP address is a set of 12 numbers split into 4 three-number groups. Each group of numbers can have a value from 0 to 255. Example: 182.25.0.255. A really important thing to note here is that the IP addresses must lay on the same subnet - for beginners - the first three groups of numbers must be the same for all computers. Example: 192.168.0.1, 192.168.0.2, 192.168.0.3 etc.
The number of IP address has nothing to do with speed of computers, who's turn will be first etc. its just a number describing your network adapter.
Note: Some hubs (layer 3) have their own static ip address. If this is the case, it will be shown in the manual. If so, your computers have to *obey* the hub's subnet. Example: I have an Wi-fi access point/switching hub in one. Its address is 192.168.2.1. Unless i want to mess with its settings, i have to give my computers the following IPs: 192.168.2.2, 192.168.2.3 etc. or else the connection with hub won't work.
Note: A subnet is a numerical "key" to the IP address it is bind to. Its basic purpose is to designate which number group of the IP address that can "see" each other. Example: the address is IP 192.168.0.1. Its subnet is 255.255.255.0. This means that the following IPs can see each other192.168.0.2, 192.168.0.3... 192.168.0.255. If the subnet would be 255.255.0.0 the following IPs would see each other 192.168.0.1, 192.168.1.1, 192.168.0.2, ... 192.168.255.255. Tha'ts why it is called a subnet mask - it creates a sub-network which is masked from all other sub-networks.
6. Setting up a static IP address LAN with Internet connection
Under WinXP, if you share the internet connection, the DHCP service will still be up, and the IP address will be changed to 192.168.0.1. However, if you want to use a static ip address system, it's okay (DHCP service will still be running though, you can't help it). Just follow the above configuration in section 5.
AND
Tell your coleagues the DNS (Domain Name Server) and Default Gateway IPs. Not surprisingly, the DNS and Default Gateway IP is exactly the same IP that the Internet connection shared computer has.
Thus, if the internet connection shared computer's lan card IP (not the modem's IP) is: 192.168.0.1, all other computers must open their TCP/IP setup at their Lan card settings and enter the following:
Primary DNS: 192.168.0.1.
Default Gateway: 192.168.0.1.
The best way to tell if the shared internet connection is working is by opening the "command prompt" on all computers and typing in "TRACERT www.google.com". It will start popping out some ip addresses, miliseconds and names of servers. If miliseconds are all numbers, never the sign * (asterisk), the connection is cool.
How all this affects the CIV3 game?
IF you are the system administrator of the LAN party, tell your coleagues whether the server is DHCP or static ip. If latter is the case, tell them their IP address.
If you are not a system administrator of the LAN party, double check your IP (just in case). The best way to do so (even if you used fixed IP) is to open the command prompt or and type in "IPCONFIG". the IP address will be shown there. If you have multiple network adapters, the one with the 192.168.X.X is probably the right one. This is true for both DHCP and static IP address systems.
Second, if you are not connected to internet, CIV3 will say "connecting to Gamespy" but will eventually give up. When it gives up, click the "refresh" button" or type in the IP address manually. The game *will* work without connecting to Gamespy.
Note: If your connection is FIREWALLED, CIV3 will show the room, settings, let the players in, but the game will not start (it will freeze). Since there's no need for LAN to be firewalled (only the Internet connection should be) - turn OFF the firewall on your LAN card. Internet games will not start when firewalled with default settings from Windows XP. See Chieftess' sticky post on this one
Note: Don't use Gamespy software for LAN games.
Hope this helps
- bibor aka Kirby
P.s. corrections, comments are most welcome
