Posted: Sun Sep 28, 2003 8:31 pm
I am having trouble hacking LANs.
First of all, before you hurl abuse at me for asking a newbie question, I want you to know that I did all the right things first: read the FAQ, downloaded & read the Ultimate Uplink Guide (a treasure-trove of info -- I highly recommend it -- get it at http://www.modlink.net/guides.php), used the Search button on this server multiple times with different search parameters on LANS/hacking/etc (not so useful, mainly a bunch of arrogant jerks screaming at people to read the FAQ), but I could not find the answer to my problem, which was this: the LAN hack was not working as advertised. I never got the blue lines connecting the router to any of the other components on the LAN. I could never connect to anything by pushing the "Connect" button. Yes, I used LAN Scan. Yes, I ran LAN Probe on the router and everything else I could see. Yes, I have the highest versions of all the software (robbed the bank a while ago -- have a maxed-out Trinity and all software, etc). In desperation, I tried LAN Spoof and LAN Force on everything as well; of course, nothing happened.
I even took on several LAN hacking jobs to see if it varied from LAN to LAN. The first two were the same (Voxel & Transcendant). But then the third (Biogenic) was different. When I probed its router, I got blue lines to the hub! Everything worked like they said it would on the FAQ and in the Guide. It was great! I hacked the whole thing, including going through a modem. I got through the entire LAN to the main server (OK, not on the first try -- but eventually) and successfully completed the mission. So, I'm not a COMPLETE loser.
Thinking that I had solved the problem, I went back to the first two LANS, but nothing had changed -- I still could not get any connections from the router. What gives?? I am using the most recent version of the software (1.3.2). Is this a bug?? I am posting this on the Mac forum, because if it is a bug, it may be specific to the Mac port. (However, in my abortive attempt to sift wisdom from the other forums, I did see at least one PC user with a similar problem.) I really like to solve these kinds of problems myself (as you can see), but I am stumped here. I cannot think of anything else to try. Any suggestions would be appreciated. Thanks.
First of all, before you hurl abuse at me for asking a newbie question, I want you to know that I did all the right things first: read the FAQ, downloaded & read the Ultimate Uplink Guide (a treasure-trove of info -- I highly recommend it -- get it at http://www.modlink.net/guides.php), used the Search button on this server multiple times with different search parameters on LANS/hacking/etc (not so useful, mainly a bunch of arrogant jerks screaming at people to read the FAQ), but I could not find the answer to my problem, which was this: the LAN hack was not working as advertised. I never got the blue lines connecting the router to any of the other components on the LAN. I could never connect to anything by pushing the "Connect" button. Yes, I used LAN Scan. Yes, I ran LAN Probe on the router and everything else I could see. Yes, I have the highest versions of all the software (robbed the bank a while ago -- have a maxed-out Trinity and all software, etc). In desperation, I tried LAN Spoof and LAN Force on everything as well; of course, nothing happened.
I even took on several LAN hacking jobs to see if it varied from LAN to LAN. The first two were the same (Voxel & Transcendant). But then the third (Biogenic) was different. When I probed its router, I got blue lines to the hub! Everything worked like they said it would on the FAQ and in the Guide. It was great! I hacked the whole thing, including going through a modem. I got through the entire LAN to the main server (OK, not on the first try -- but eventually) and successfully completed the mission. So, I'm not a COMPLETE loser.
Thinking that I had solved the problem, I went back to the first two LANS, but nothing had changed -- I still could not get any connections from the router. What gives?? I am using the most recent version of the software (1.3.2). Is this a bug?? I am posting this on the Mac forum, because if it is a bug, it may be specific to the Mac port. (However, in my abortive attempt to sift wisdom from the other forums, I did see at least one PC user with a similar problem.) I really like to solve these kinds of problems myself (as you can see), but I am stumped here. I cannot think of anything else to try. Any suggestions would be appreciated. Thanks.