Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you have been placed in read-only mode.
Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).
So the game is at the point where I have to hack a LAN to continue the storyline (Darwin LAN). I have all the hardware and software. Got access to the LAN, used LANanalyzer, probe all that stuff. I found 3 locks with controllers, 1 main server and an access terminal. I disabled all 3 locks, got access to the access terminal and that's it. I try to connect to the main server but nothing happens when I hit the connect button.
Help?
Lyle
------------------
Quote
Originally posted by lylemcd: **So the game is at the point where I have to hack a LAN to continue the storyline (Darwin LAN). I have all the hardware and software. Got access to the LAN, used LANanalyzer, probe all that stuff. I found 3 locks with controllers, 1 main server and an access terminal. I disabled all 3 locks, got access to the access terminal and that's it. I try to connect to the main server but nothing happens when I hit the connect button.
**
Sorry, nevermind the original question, I found two locks I hadn't hacked yet. Thing is, I can't get to them since the only connection is through another lock. I also can't find any controllers that appear to be connected to them.
Originally posted by lylemcd: **Sorry, nevermind the original question, I found two locks I hadn't hacked yet. Thing is, I can't get to them since the only connection is through another lock. I also can't find any controllers that appear to be connected to them.
Ok, figured that one out too, I think. There was still a lock I missed. But I had to LanForce all of them, one at a time.
but everytime I get access to the main server, the sysop is on my butt in a few seconds. I was getting, at most, 1 or 2 files per hit (and I never had time to delete my logs). I've got monitor and proxy bypasses, have no clue what I'm doing wrong.
Thanks as always. Lyle
There may be another part of the LAN that contains the controllers. Have you checked all the terminals to see if they mention a LAN access phone number? It will look like xxxxx-xxxxxx (5 numbers, then 6 numbers, separated by a dash).
(there can also be separate areas accessed by wireless transmitter, but I'm assuming that if you'd found one you'd have mentioned it)
------------------ r
Originally posted by Ricia: ** There may be another part of the LAN that contains the controllers. Have you checked all the terminals to see if they mention a LAN access phone number? It will look like xxxxx-xxxxxx (5 numbers, then 6 numbers, separated by a dash).
I only found one terminal on the system and hacking it did zilch for me so if there's another part of the LAN (this is the Darwin LAN, it's a story mission) I haven't found it.
Originally posted by lylemcd: **I only found one terminal on the system and hacking it did zilch for me so if there's another part of the LAN (this is the Darwin LAN, it's a story mission) I haven't found it.
You might be able to find another LAN site from the links at the internal services machine. Or checking the log on the central mainframe, looking for LANish phone numbers.
Having a short hop from your connection site to the main server makes it =very= hard to do anything on the server. I've noticed that if you get bounced off too soon, the files you deleted reappear on the server. There was one "trash the LAN" mission I had to give up on.
Originally posted by Ricia: **You might be able to find another LAN site from the links at the internal services machine. Or checking the log on the central mainframe, looking for LANish phone numbers.
Well, on this LAN (I know the are generated randomly) there is one hub between the LAN router and the main server. I literally get maybe 10 seconds before getting booted. Which sucks because I'm supposed to grab 9 files and delete the logs so I don't get caught.
Is there any way to log onto the LAN from somewhere else (like one of the terminals) or am I just screwed?
Originally posted by lylemcd: ** Is there any way to log onto the LAN from somewhere else (like one of the terminals) or am I just screwed? **
I've never found more than one connector to a main server on a LAN: not more than one little blue line connecting it to something else.
I =have= found LANs where this is more than one place to logon, both able to get to the server connector, one through a longer path than the other. I've also found LANs that have internal loops, allowing you to choose the longer way around.
It doesn't sound to me like either of these options is likely for you. Though your control-less locks make me think there must be another part of the LAN somewhere. If the links on the ISS or the logs on the CMF don't give you the access numbers, the only way I know to find them is to hack the usr file.
The LAN I had to give up on had only two hops from the router to the server. (I don't say "abandon" because I never actually did that, I left the mission cluttering up my inbasket <g> ).
I've run into the type of LAN your talking about a couple of times and hate them. My favorite are the ones with lots of radio transmitters. Anyway, this type of LAN always looks the same. Three locks which are vertically aligned but not connected. Meaning, the LAN kind of looks like a capital E, where each lock is at the end of one of the horizontal lines of the E. Also, I think they are always locks behind locks. I've never been able to do anything but use the LAN Force on them. If anyone else has run into these and has any suggestions please help.
As far as I can tell, lylemcd, you are not doing anything wrong. You just have to keep logging back onto the LAN and move as quickly as possible. Also, you don't have to delete the logs on the Darwin LAN, just your own on INTERNIC.
(quote)Originally posted by suydam: **I've run into the type of LAN your talking about a couple of times and hate them. My favorite are the ones with lots of radio transmitters. Anyway, this type of LAN always looks the same. Three locks which are vertically aligned but not connected. Meaning, the LAN kind of looks like a capital E, where each lock is at the end of one of the horizontal lines of the E. Also, I think they are always locks behind locks. I've never been able to do anything but use the LAN Force on them. If anyone else has run into these and has any suggestions please help. (/QUOTE(
Yeah, it's a lock behind a lock thing. So I've got one line going into a controller, attached to a lock, which is attached to another lock. It's the second lock that was giving me problems. I guess you just have to LAN Force, logout and reconnect.
Sort of like
hub <--> controller <--> lock <--> lock
(QUOTE) As far as I can tell, lylemcd, you are not doing anything wrong. You just have to keep logging back onto the LAN and move as quickly as possible. Also, you don't have to delete the logs on the Darwin LAN, just your own on INTERNIC.
**(/quote)
I did that, and a few minutes later, I saw movement on the motion sensor. Let it go and then I got busted. Thank god for backups.
Thanks to everyone for the advice.
You got busted by being kicked off the Main Server or, did Uplink actually take away your Gateway? Whenever I do that particular Darwin mission I delete both of my last two logs, the Uplink Test server and then Internic. Also, I take different routes to it each time. I used to get booted off of Uplink after hacking Darwin but, these measures seem to do the trick.
Originally posted by suydam: **You got busted by being kicked off the Main Server or, did Uplink actually take away your Gateway? Whenever I do that particular Darwin mission I delete both of my last two logs, the Uplink Test server and then Internic. Also, I take different routes to it each time. I used to get booted off of Uplink after hacking Darwin but, these measures seem to do the trick.
I got fully disavowed and the game was over. It was a "We have been informed by a major corportation that you were caught hacking..." end of game message.
Since I was getting, at most, 1-2 files per logon, I must have gotten kicked off the server a good 7-8 times.
Thanks for the advice, I'll try it.
As a side note, unless you are responding to a specific sentence someone said, try not to use the smaller "reply" button on a given person's post. Press the larger "Submit Reply" button, that way, the entire previous message won't be repeated. Thanks.