![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
Unexpected Benefits
Aug. 17th, 2002 10:49 pmYesterday I get a email from one of the network guys sending me the settings file for the new VPN software we're planning on implimenting. He calls and begins to explain what's going on and me, not remembering our conversation from a week and ahalf ago, am a little slow on the uptake. After the lightbulb comes on, we talk about various stuff (mainly installation, setup issues and authentication stuff). But, even after our conversation, I'm still not sure what to expect. Will the user be able to get network stuff w/o having to log in under the same id/pw they use at work? And what'll happen if they hork their ID?
So, armed with too little information and a freshly imaged machine from the workstation group (which no one questioned when I took out of the building; security is such a joke around here), I set about to test my connection. Installed the software, set it up and logged in. So far so good. Tried to access the network. No dice.
Uh oh. I think I know what the problem is and I hope it's not too late as I try to connect to the terminal server.
"You cannot log in because you have been locked out."
Crap. As I suspected and feared, the authentication from the PC (which is currently not my correct work id and password was required and I'd just locked myself out. Which, as I had been told by Mr. Network Guy, would also prevent me from logging in again (which was also true.) So, until I get my account unlocked (which can only be done by people who don't work on weekends), my weekend testing is over.
To make a long story short, I did manage to get my account unlocked. And I'm proceeding with the testing as planned. However, I discovered a side-effect that is going to make web development on my home machine so much eaiser.
When I'm at home, I cannot view my home web server using the outside-world URL; the IP request hits my router and stops because (long involved technical details which I'll spare you, my gentle readers). But, when I connect via the VPN, I can see my web site just like everyone else.
Ok, so this may not seem like a big deal to you. but I'm all giddy about it. So there!
So, armed with too little information and a freshly imaged machine from the workstation group (which no one questioned when I took out of the building; security is such a joke around here), I set about to test my connection. Installed the software, set it up and logged in. So far so good. Tried to access the network. No dice.
Uh oh. I think I know what the problem is and I hope it's not too late as I try to connect to the terminal server.
"You cannot log in because you have been locked out."
Crap. As I suspected and feared, the authentication from the PC (which is currently not my correct work id and password was required and I'd just locked myself out. Which, as I had been told by Mr. Network Guy, would also prevent me from logging in again (which was also true.) So, until I get my account unlocked (which can only be done by people who don't work on weekends), my weekend testing is over.
To make a long story short, I did manage to get my account unlocked. And I'm proceeding with the testing as planned. However, I discovered a side-effect that is going to make web development on my home machine so much eaiser.
When I'm at home, I cannot view my home web server using the outside-world URL; the IP request hits my router and stops because (long involved technical details which I'll spare you, my gentle readers). But, when I connect via the VPN, I can see my web site just like everyone else.
Ok, so this may not seem like a big deal to you. but I'm all giddy about it. So there!
