Take the 2-minute tour ×
Arqade is a question and answer site for passionate videogamers on all platforms. It's 100% free, no registration required.

I have a mission that requires me to copy 90 Gqs of data from a server on a LAN. The server is behind a dial-up poxy, and only by a few hops.

The shortest path to the server goes:

MODEM -> LOCK -> MAIN SERVER

The path I have to follow (and I've seen the sysadmin track) is:

MODEM -> HUB -> AUTHENTICATION SERVER -> LOCK -> MAIN SERVER

Even with the network's Monitor and Proxy bypassed, the sysadmin still jumps on the network the minute I even touch the main server. I don't even have to start cracking the password or spoofing his voice authorization - just connecting to the main server is enough to trigger this.

With the short path, and the amount of work still ahead of me, there's not enough time for me to do what I need to get done before the sysadmin reaches me.

Is there some way around this that I'm not realizing? This is a storyline mission, so I imagine there has to be - unless the random LAN generator just totally screws the player now and then.

Am I out of luck here, or should I be doing something particular to overcome this?

share|improve this question
    
one thing is you can bounce around other servers. Banks and Government servers work well as long as your last one before the main server is the "lock" you will be ok as it recognizes you are on the lan, bounce that thing like 14 times. –  Mike Jul 25 '12 at 14:02
    
@Mike I'm not sure I follow. I'm bouncing off of every server listed on InterNIC already. –  Iszi Jul 25 '12 at 14:27
    
I am not entirely sure of it but I do remember having read that bouncing through machines owned by the company whose system you want to hack (except for the last bounce) reduces the trace time. I never bothered to confirm, since around five admin account machines always seemed to provide enough trace time, without bouncing through too many ones –  Zommuter Aug 2 '12 at 19:58
    
@Zommuter This isn't a matter of trace time. That only affects the trace between the company's network and your Gateway. This issue is about the Admin tracking you down inside of their LAN. That's not affected by the route you take to get to their network. –  Iszi Aug 3 '12 at 0:08
    
@Iszi I'm not sure the trace time doesn't also have an influence on the time the admin logs in to start tracking you down in the LAN. But it's been a while since I last played Uplink, so this may be a fishy memory... I just mentioned it because you said you bounce through every other server, which seems a bit overkill to me (However, one can find even more servers to bounce through by checking public terminals and hacking into mainframes.) –  Zommuter Aug 3 '12 at 6:30

4 Answers 4

up vote 8 down vote accepted

When you're dealing with short LAN paths, one trick is to connect to the server, crack the non-password protections first, and then disconnect (and remove InterNIC logs, as usual). The cracked protections will stay unlocked when you reconnect, meaning you only have to crack the password, and then copy files.

You can save additional time by opening both the password cracker, the file copier, and the memory view before reconnecting, and also bump up the CPU usage for the cracker so it can work faster (do the same with the file copier when the cracker is done). This should allow you to get at least one of the files in time, and from there, repeat until you have everything you need.

On rare occasions, this might still not be enough. If that happens, then there is unfortunately little you can do about it, except possibly upgrading your gateway to the 10Gq/s modem - which might also require downgrading your gateway overall, since IIRC, only the file server gateway can use it, but in my experience it hasn't been much of an issue.

share|improve this answer
    
Good suggestions here. It sounds like you're saying there is the odd random occasion where the player is indeed just plain screwed by the random LAN generator? –  Iszi Aug 2 '12 at 13:45
1  
@Iszi: Yes; I once had a LAN where my path was insanely short - I can't remember exactly how long it was, but it was at most a single node between the modem and the mainframe - it might even have been a direct connection between the two. While it might still be possible - I can't remember what my mission was, or if I completed it - you might still run against the limit of what you yourself can actually handle, and in those cases, you're pretty much screwed. –  Michael Madsen Aug 2 '12 at 15:28
4  
@Iszi It's never completely impossible - IIRC, it's entirely possible to mod the game and add new computers for sale that have even faster modems and much more computing power. If reality isn't working for you, hack reality :) –  Tacroy Aug 2 '12 at 15:49
    
@Tacroy +1 for that last sentence. Is it a quote from somewhere? –  Iszi Aug 2 '12 at 16:07
1  
@Iszi I have no idea, but it's mine now. Muahahaha. –  Tacroy Aug 2 '12 at 16:26

You will likely have to do several trips to pull all the information you need, both because of limited time and limited memory. Do you need to use any tools that are CPU-bound to infiltrate the server? If you do, upgrading your CPU could help, and upgrading your modem will help download the data faster.

You could also try working on your own speed: have the necessary tools ready to go and click like the wind in order not to waste any seconds idling.

Stealing data from a mainframe is one of the most annoying mission types, but I've never seen a mission that was downright impossible.

share|improve this answer
    
The gateway I'm using is pretty beefy in terms of CPU, and has the second-highest modem. Still, I don't think there's even enough time for one file. –  Iszi Aug 2 '12 at 11:06
    
Added another suggestion. –  kotekzot Aug 2 '12 at 11:10

As Solus mentioned in his answer, navigating through the LAN works like a charm. The other options seemed too much work, so I kept reading to find his answer. But you do not need to mash up the back button, just go back as soon as the admin has just one step to get to you... then just wait for him to go back to the router and start again.

I got this on the first try after reading this answer, thanks Solus!

share|improve this answer

Once you get connected to the main server, start mashing the back button. Then move yourself as far away from your connection point as possible. DO NOT CONNECT TO ANYTHING ELSE. Connecting to anything else will break your connection to the main server. The admin will then proceed to follow that path. Then, you can close the LAN view, and you'll still be connected to the main server. Download/destroy/whatever it is you need to do, and check occasionally on the LAN view. If he's close, mash back again, pick another path, and close LAN view once more to continue working the server.

Becomes so much easier when you do that.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.