I'm doing the mission where i have to steal some files from the ARC LAN for arunmor. I hacked the LAN, got a phone number, hacked that, got another phone number, and when i dial that the only other computer in the LAN is the mainframe. When i enter the mainframe, the "administrator" is alerted and my trace tracker says i've got about 180 secs or so, but after 5-10 sec i am disconnected (connection terminated by remote host or something like that). I don't even have time to copy 1 file (or maybe i could barely make it if i tried it many times). I've put all the security on bypass so i have no idea why this happens (i know the admin always logs in but why does he terminate my connection so fast, when my trace tracker says i've got tons of time)?
I even tried putting the admin to jail, but they just got a new one right away.

Tracer time and time until the admin kicks you are unrelated. You keep getting kicked because the admin doesn't have to "travel" very far to reach your position in the LAN.

-- Griffinhart

What am I supposed to do? There's only a modem and the mainframe in the LAN, nothing else.. And I can't copy all those files in such little time...
Am I supposed to access some other system? In the mission from Arunmor it says "Once inside, you should be able to find the restricted file area." - does it mean the mainframe? There's only that, a bunch of hubs, Terminals and modems, nothing else.

If the mission is the one I think it is, you need to get through the LAN to the mainframe and steal data. You'll have to do multiple connections if the LAN is too small for you to copy everything in a single go. (Alternatively, you can reset your intra-LAN connection repeatedly. This eliminates the hassle of rebouncing and reconnecting to the LAN multiple times, but puts you at a bigger risk of being traced.)

If the admin keeps kicking you because the LAN is too small... well, tough luck.

-- Griffinhart

Huh, if that's true I think you should fix it - there's nothing good about having to connect individually for each file. It worked fine in the 'legacy' uplink.

No it didn't. I didn't touch that code block in 0.1.x

0.2.x however will have a program that "spikes" the connection, causing it to stay open.

Trust me, it did. I played the whole game trough at least 2 times before, and I never had this problem. Besides the fact that something like this is insane and I'm sure the devs would never slip something like that into a production version.

So you're going to debate a facet of a game with a developer who has specifically stated he has not, in fact, altered the facet in question, and has the code to prove it?

Meh, okay.

I'd just like to state that, AFAIK, all LANs are randomly generated - and I have had this problem. It's the reason why I never take LAN jobs, no matter how good the pay is. Dunno if it was the ARC LAN, though.

-- Griffinhart

LANs are randomly generated.

you've just got bad luck and the randomizer gave you barely anything to work with.

Of course, just to get though it, here's a tip:

If you don't crack all the systems on the login page, they don't reset. Do the voice first, which takes the longest, then disconnect, reconnect, and login with the password, then scramble like hell.

It'll allow you to hobble along till 0.2.x is out with the spike.

that happened to me, too, the arc lan was a big mess to get to the farthest terminal, and then i got a modem number that led to a modem 1 step away from the main server. i just used the trick outlined to get all files.