In an effort to become an even better domestic network administrator, I
finally managed to setup a VPN this
afternoon. The VPN lets me call up any other computer’s monitor on the
local network or, put another way, I no longer have to traipse my lazy bones to
another room if I want to spy on what Ph. is doing on the internets.
Spying, parenting, call it what you want (split hairs only if you must).
The VPN is terrific for other stuff, too. For example, given that Ph.’s
clunky old computer is password protected, I can simply veepen (VPN) his
mo-chine (his desktop pops up on my desktop) and type in the password without
ever leaving my seat. Nifty. Also good for remotely running maintenance,
like ad-aware and spybot apps.
I should probably acknowledge that the setup was possible only with a
generous lent-hand from my
we were in Detroit last weekend, he recommended VPN as a solution to a few of
the headaches I was describing to him. I downloaded it and tried to
install it myself late last week: a plentitude of time-out errors. I could get
the local system to ping, but the VPN wouldn’t work. And I could not isolate the
cause of the error. Tried everything I could think of. Today, I
called my brother (he was at my nephews soccer match and so had to call me
back.) After a half hour on the phone this afternoon, both of us were still
stumped. And then J. asked me whether Windows Firewall was on.
Me: "Um. No. I’m sure it’s off. I use something else." But I checked it
anyway because nothing else was fixing the mess, and sure enough, Windows,
kindly bowling over its numb-skull users, had quietly reactivated the firewall
during the last update. Once I turned it off, the VPN worked, magically
porting Ph.’s computer monitor onto my own.
Added irony: I was reading and making notes on Norman’s
Everyday Things before and after the debacle.