WWTBAM Bored

I've been trying to get access to a shared drive (one I didn't need before, but I do now) since late last week.

Of course, I've gone through the standard IT helpdesk emails/protocols/phone help to get it done.

So finally, I get an email this morning with the fix -- type in a command in the start|run part which will activate a routine to give me access to the drive.

And it doesn't work...

..because the @#)@# routine is on the very drive I need to access, and can't get access to!

grrrrrrrrrrrrrrrrrrrrr.............

SpacemanSpiff wrote:I've been trying to get access to a shared drive (one I didn't need before, but I do now) since late last week.

Of course, I've gone through the standard IT helpdesk emails/protocols/phone help to get it done.

So finally, I get an email this morning with the fix -- type in a command in the start|run part which will activate a routine to give me access to the drive.

And it doesn't work...

..because the @#)@# routine is on the very drive I need to access, and can't get access to!

grrrrrrrrrrrrrrrrrrrrr.............

Heh, heh! That's a modern version of Catch 22.

Bob Juch wrote:

SpacemanSpiff wrote:I've been trying to get access to a shared drive (one I didn't need before, but I do now) since late last week.

Of course, I've gone through the standard IT helpdesk emails/protocols/phone help to get it done.

So finally, I get an email this morning with the fix -- type in a command in the start|run part which will activate a routine to give me access to the drive.

And it doesn't work...

..because the @#)@# routine is on the very drive I need to access, and can't get access to!

grrrrrrrrrrrrrrrrrrrrr.............

Heh, heh! That's a modern version of Catch 22.

Trust me, Catch 22 came to my mind on this one.

At least it isn't as catchish (if there is such a word) as at my previous job, where we had trouble with a new company handling the email. Unfortunately, the company had service that makes cable companies look great by comparison. One morning, he sent an email out to tell us to bail out of the email system, had service problems, and would let us know later when to get back on. Four hours later, someone in the office calls him to ask what's going on, and he said "It's been fixed. I sent you an email to let you know."

SpacemanSpiff wrote:At least it isn't as catchish (if there is such a word) as at my previous job, where we had trouble with a new company handling the email. Unfortunately, the company had service that makes cable companies look great by comparison. One morning, he sent an email out to tell us to bail out of the email system, had service problems, and would let us know later when to get back on. Four hours later, someone in the office calls him to ask what's going on, and he said "It's been fixed. I sent you an email to let you know."

Our IT people (contracted out, not government employees) have been known to do that from time to time.