Here are the areas that are covered on this page.

• Routers
• Hubs
• Terminals
• Locks
• Authentication Servers
• Wireless Transmitters
• Wireless Receivers
• Modems
• Isolation Bridges
• Subnets
• File Servers and Log Servers
• Main Servers
• Viewing the LAN
• Navigating LANs
• Attacking LANs

Router
The first system you will see on any LAN, it connects the LAN to the rest of the Internet. You can do nothing with these systems

Hub
Connects multiple systems on the LAN together. They have no security, and there is no need to do anything to them, they simply connect more than one system to another, e.g. a Router to the rest of the LAN.

Terminal
A basic computer connected to the network, that the employees of the company you are hacking work at. These servers serve certain purposes, though normally they are there to distract you, and waste your time.
On a system that contains a Wireless Transmitter, a Terminal might contain the frequencies of the Wireless Receivers on the LAN. By hacking the Terminal, the frequencies will be displayed to you.
Sometimes, Terminals also form Subnets that protect certain other systems. In order to be able to access these systems, you will need to fool that system into thinking you are part of the Subnet. To do this, you will require the LAN Spoof software. By running LAN Spoof on a Terminal that's part of a Subnet, you can then access systems protected by the Subnet.

Lock
Locks prevent you from moving further into a LAN. Before you can progress past the Lock, you must deactivate it. There are 2 ways of doing this. The first is to use the LAN Force software on the Lock. This is the quickest, easiest way to get past a lock, but as soon as you do this, the systems Administrator will log on and begin hunting you through the LAN, and a trace will begin on your connection.
The second way is to find the correct Authentication Server for the Lock, hack into it, and turn off the locks your self. This method is more time consuming, as you must first find the Authentication Server, and they are often protected by Subnet's or hidden on other parts of the LAN. You can tell which Authentication Server is correct by the dotted yellow box that appears around it when you have the lock selected, along with the words 'Controller'.

Authentication Server
Protected Servers that control Locks on the LAN. You can tell which locks a particular server controls by the dotted yellow box that appears around each lock, along with the words 'Locks/Unlocks'.
The servers themselves are usually protected by a Password and Elliptic Curve Cypher, both of which will need to be broken before you can deactivate any locks controlled by the system.

Wireless Transmitter
Radio Transmitters are used when sections of the LAN are separated from each other. When you connect to a Transmitter, you will be presented with a screen requesting a radio frequency. When you enter a correct frequency, you will be connected to the relevant receiver and be allowed to continue on the other part of the LAN. You can find the frequencies required to operate the Wireless Transmitters on the LANs Terminals.

Wireless Receiver
These do little other than receive connections from Wireless Transmitters. There is nothing to do when connecting to them and simply serve as connections to other points in the LAN.

Modem
Modems act in a similar way to Transmitters and Receivers, by separating sections of the LAN so you can't directly connect from one to the other. In order to connect to a Modem, you will first need to find its phone number. This is stored on a Terminal on the LAN. Once you have the phone number, you will need to disconnect from the LAN, enter the phone number EXACTLY as it appeared on the system into the IP Lookup tool. This will give you a link to the modem. By clicking this link, you will enter the LAN from the Modem, and can continue on the system.

Isolation Bridge
An Isolation Bridge works in a similar way to an Authentication Server, except that instead of controlling one lock, it controls 2. One of these locks will always be open, and the other will always be closed. When you use the Isolation Bridge, the closed lock will open and the open one will close.

Subnet
Subnets aren't actually types of system, but groups of Terminals used to protect other systems. A system protected by a Subnet will not accept connections from anything that isn't a part of that Subnet. When you click on a system, 'Valid Subnet' will appear on any systems forming a Subnet that's guarding that system, along with a dotted yellow box. To connect to one of these protected systems, you will need to use LAN Spoof to fool the system into thinking you are part of that Subnet. Once you have used LAN Spoof, you will be able to connect to the system normally.

File Servers and Log Servers
These do very little in the system, except for, as their names suggest, store file and logs.

Main Server
Your eventual target on the LAN. This is the system that runs the LAN, and any missions you have on a LAN will most likely be targeted at this machine. They are heavily defended, require a Password and Voice ID to connect to them, and when you do connect to them, the System Admin will log on automatically and begin hunting you, as well as starting a trace on your connection. They are laid out the same as Central Mainframe systems when you connect to them; they have a File Server, Console and Log section. Working your way through the LAN will always lead to this system.

Viewing the LAN
When you first open the LAN Viewer while connected to a LAN, you might find things a little confusing, but things will become simpler as you get used to it. First of all, you have the main window, which shows the LAN itself. Displayed here are any systems you have currently found on the LAN. The dotted line represents your current connect path, and a white box around a system means you are currently connected to that system. To the right is the information box, which will show some info on the system you currently have selected. This box also has 3 options: Back, Reset and Connect (These will be explained later). If you should do something that's attracts attention to what you are doing, the System Administrator will log on. A Red warning message will appear, and a siren will sound. The System Admin is represented by red dotted lines (his connection path) and a red box around a system (the system he is currently connected to). When you connect to a system on the LAN, the LAN viewer will close, and the System will be shown on the main screen. Once you have finished with it, you simply click on the viewer again to continue on your way.

Navigating LANs
In order to connect to systems on a LAN, you will need to make a connection path through the LAN to that system first. When you first connect to a LAN, you will only be able to see the router. The first thing you should do is run LAN Scan. This will show all the systems on the LAN that aren't protected by closed locks (If nothing appears, you will need to buy a higher version of LAN Scan). Once this is finished, you should run LAN Probe on the Router to show where it connects to. Run LAN Probe on a few systems to give you an idea of the layout of the LAN. Now you need to make a connection to the first system. From the Router, click the first system connected to it (usually a Hub). A dotted line will appear over the connection line to the Hub. This line is your connection path. Clicking on another system connected to the Hub will extend your path to that system. Continue this process till you reach the first system you need to hack. This is where the 3 options to the right come in. The first option is 'Back'. Use this to move your connection path back to the previous system. The next one is 'Reset'. This will move your connection back to the Router, and reset any access you had on the system (though any opened locks will remain open). The 3rd is 'Connect'. This is what you use to connect to a system you currently have a path to. Click the system, then click connect and the contents of the system will be displayed.

If at any point, the System Admin should log on, he will try and hunt you through the LAN by following your connection. If he reaches the system you are connected to, he will disconnect you from the LAN.

Attacking LANs
The first thing you should remember about LANs is that, just like other systems, they have Proxies and Monitor, which will need bypassing or disabling if you intend to be successful. You should also make sure you have the voice print for the companies Administrator before you connect, as you will need it to enter the Main Server. Since every LAN will be different, there is no set way of attacking them, as you don't know what types of security will be on the LAN. Use the above information to tackle each system as it comes. Remember that Using LAN Force or Connecting to the Main Server will cause the Systems Admin to log on, and that a trace will start on your connection. As long as you have the right software, and don't rush and make mistakes, you shouldn't have many problems hacking a LAN. You should also remember that, if the system admin reaches your location in the LAN, you will be cut off, regardless of how long you have left on the trace. You can tell when he logs on because the siren will sound.