QUOTE (darthmord @ Jan 20 2013, 01:15 PM)

Not to mention that the real world often has internal/private networks that are not connected to the outside world and on-site networks that DO connect to the outside world.
So extending that line of thinking to the SR world isn't a stretch at all. Makes sense to people so the few times I've gotten to run games, I've set up the computer networks like that.
One of the things that broke the Matrix believability (from the beginning) was the idea that EVERY SYSTEM was connected. There is no reason for every network to be connected. Same goes for Wireless Matrix. Companies and people would only use certain features:
1. if they were too lazy to disable them
2. did not know how to disable them
3. were unaware the features were on
4. or if they actually needed them
So if the place you are running against has a private disconnected network, you are going to have to jack in on-site, not from Mom's basement. That's always been a good thing. Deckers & Hackers need to get out more often.

Really the idea behind "everything connected" is that most systems need to be connected to perform their day to day functions. You can't disconnect the banking system's account network because to perform the thousands of basic transactions every hour of every day, it has to be hooked into the international grid (so the Stuffer Shack can charge your account, etc).
Beyond that, a corporate R&D lab might need to make hundreds of daily reports and transmit research logs, or even connect via dummy terminals to a central corp system offsite that serves a dozen such labs in multiple time zones and jurisdictions. Laws crafted to prevent certain kinds of work, research, etc, might be circumvented by renting out a cheap office downtown but having all the work and data are actually stored in an offshore oil rig in the Aleutians or in an extraterritorial corporate stronghold. Security breaches can be handled by security hackers scattered around the world to prevent a quick meatspace strike taking down all the matrix security in one shot, and physical security can make a small, difficult to access site at an undisclosed location virtually impenetrable to runner teams. In a total emergency, a system could be brought down easily and effectively with no one shooting at the sysops.
In fact, actually having the system offline, where all the work is done, where all the workers have to physically go, with the only security being 100% onsite would make a system terribly unsecure. Private disconnected networks make sense for some operations, blacked out networks for totally secret/illegal stuff, but those sites would be necessarily be nuclear strike survival bunkers themselves.
Where I run into the problem is wirelessly broadcast networks that don't have a reason to be. The old wired world had several layers of basic government security before you could get to the corp systems (through the RTG/LTG network). In most places, the UCAS especially, these were a joke, but having to break the LTG and then break up to the RTG and across to wherever and then back to another RTG and LTG so you could do the search operations to find the corporate site you were looking for wasn't an extreme roadblock, but it was theoretically enough to keep out the casual hacker or block the automated illegal data miner. In the wireless world you just have to get near your target location and go straight in -- and systems that ostensibly have to have wireless components to function (security communications, drone relays, etc) allow you to just step around any matrix chokepoints or roadblocks.
A system that looks like:
Lab Stations
^
|
v
Security node <----> Central Hub (port to the outside) <-----> Drone node
in the wired world would be a significant hurdle, because from the outside a hacker would have to break through the central node, and into Security and Drone locations from that central node -- the datatrail would be significant, and you'd have to get through at least 2 layers of security to do anything useful. Wireless, you'd have at least 3 entry points to attack the system, which means more expense (more IC, each node needs probes and tracers and attackers) and more frontage to cover by security hackers. Not to mention that cracking the Security or Drone nodes would only make it easier to breach physical security and plug straight into the Lab node. Your system might have a strong front gate, but the back and sides are plate glass (unless you multiply the cost of security).
In the wireless world, a system should really look like this:
Access Terminal <-----------------------------------------------------------> offsite Matrix fortress full of security hackers and IC
So to do work, workers just go into the local Access Terminal and bridge over into the offsite location where all the data is. If the physical site is ever breached, the offsite security shuts down the line from that access point.
EDIT: In the diagram above, Lab Stations is supposed to be branched off Central Hub (not Security) -- post formatting aligned it left.