Quote
Originally posted by DarkStar:
**Okay, I'm new here, but here goes...
Eh, how does one go about breaking into LAN's. I've got all my bypassers and LAN junk, but I'm not quite sure how or what I'm supposed to do to get into various systems without the SysAdmin coming in and hunting me down. I've looked through a fair portion of the boards, the FAQs and the "Utimate Uplink Guide" without finding anything very useful. Any advice?
**
Sure. You have all the LAN junk? Good. Here's one tip you should always keep in mind: Never, ever use LAN_Force unless the puzzles forces you to (locks without controllers). Here's a general step-by-step guide you can follow which should help you through most LANs.
1. Connect to the LAN, and run bypassers. Not necessary, but if you can afford LAN gear you can afford bypassers.
2. Pull open your LAN view, and run LAN_Scan. This should being several systems in view.
4. Go through the lan, system by system, running LAN_Probe on each one. In order to get past a lock, click on it. It should point out where the "Controller" is. This is the system you will need to hack in order to deactivate that Lock. After opening a lock, run Lan_Probe. This will bring the Lock's connections into view.
5. If you find a system that says "Valid Subnet", then you must run LAN_Spoof on a certain system of the set of systems labelled "Subnet". I've found that running Spoof on the middle one always works, while sometimes the top one doesn't work.
6. Radio Transmitters/Receivers have a certain frequency you have to set it to in order to move anywhere further. This frequency can often be found on terminals nearby.
7. Modems are different connection points into the LAN, but you won't find those entry points anywhere but ont he LAN. You'll have to find the phone number on a terminal somewhere.
8. When you connect to the mainframe (your ultimate goal), you will, without fail, have the sysadmin poke his head up and start tracking. The time it takes for him to find you and disconnect you depends on how far you are from the initial router.
Unfortunately, many LANs get set up so the mainframe is 2 steps away from the router, with Locks without controllers guarding it. This is mostly frustrating when you have to disable that system, since you'll have to do the voice-playback, then type in the password (once you crack it once, it never changes), then pull up console, yada yada yada... a lot of times you end up getting disconnected before you can finish.
In my experience, Locks without controllers are in groups of 3 spread across the LAN. Also In my experience, you have to use LAN_Force on them. Thankfully, if you get kicked off the LAN, they'll be unlocked when you come back.
Hope that clears up any questions you had!
------------------
(edited by mrxak: There are younger members on these forums. Please do not post that URL.)
(This message has been edited by mrxak (edited 06-19-2003).)