|
I was driving along, and the car started wobbling rapidly left to right. Slowed right down and crept home, had a look, and the top wish bone has detached itself from the hub upright. The nut just plain fell off. I noticed it knocking a bit recently but didn't get round to checking! 
Still, I found a spare one and put it back, but its very odd, its a self locking nut.
|
|
|
|
|
Was the terrorist attack near you?
|
|
|
|
|
Just glad it didn't come off half an hour earlier when I was doing about 70 mph!
|
|
|
|
|
Yeah Prawn Cocktail is probably better.
|
|
|
|
|
Quote: its a self locking nut.
This particular one is called the "Houdini Nut".
- I would love to change the world, but they won’t give me the source code.
|
|
|
|
|
The most dangerous nut in a car is the one behind the steering wheel
=========================================================
I'm an optoholic - my glass is always half full of vodka.
=========================================================
|
|
|
|
|
How do you manage to have just one nut behind the wheel? Do you stick your leg out the window?
|
|
|
|
|
The other two are below the steering wheel
=========================================================
I'm an optoholic - my glass is always half full of vodka.
=========================================================
|
|
|
|
|
Munchies_Matt wrote: its a self locking nut
Er .. no .. it's not ... evidently!
|
|
|
|
|
Munchies_Matt wrote: its a self locking nut
Apparently, also a "self unlocking nut"
"Fairy tales do not tell children the dragons exist. Children already know that dragons exist. Fairy tales tell children the dragons can be killed."
- G.K. Chesterton
|
|
|
|
|
Yesterday morning I had a call from a client's IT person requesting help with one of our applications. The application and supporting files are kept on a network share and are used by two users in this case. Users typically have 'full rights' to the program folder. For this client, this arrangement has worked flawlessly for many years...until last week. Suddenly both users started getting 'Access Denied' windows security warnings when trying to start the program. (naturally, they assumed these were our error messages!) I spent half an hour on the phone trying to walk this junior IT person (everyone else is out on vacation) through troubleshooting the permissions issue. From the server, it appears as though the users have the required privileges, but still navigating to the program folder through explorer prompts for credentials.  I have the tech enter her credentials, she gains access, and the application works as expected. Problem solved?...not so fast...she mentioned that she would reboot, try again and let me know the results. Knowing that the issue was not going away, I mentioned a few other possible things to check while trying to drive home the fact that my application is not the problem. Troubleshooting windows AD security/permissions problems are not fun, but it's part of your job. I've received another email this morning telling me that she has tried everything but is still getting the 'Access Denied' message from our program. 
"Go forth into the source" - Neal Morse
|
|
|
|
|
Well - you might be able to pass the buck by telling her that she should call the manufacturer of the server?
or, being a bit more serious,
Is it possible to send her off on an honest (but merry) chase as to what changed on the system between the last successful run and the first failure. Window Update, for example? TC/VM update? I've had two perfectly good applications get put to death by an update to the VM's.
You could pleasantly insist that this is vital information in order for you to diagnose the problems. Buck passed (virtually).
| "The difference between genius and stupidity is that genius has its limits." - Albert Einstein | | "As far as we know, our computer has never had an undetected error." - Weisert | | "If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
Good advice! Thanks!
"Go forth into the source" - Neal Morse
|
|
|
|
|
Did she try to turn it off and on again?
while (true) {
continue;
}
|
|
|
|
|
Well, of course I asked if the file server could be rebooted...who knows with AD...maybe acl on the server is not current with client token??? I'm a coder not a network security expert! 
"Go forth into the source" - Neal Morse
|
|
|
|
|
That was just a reference to The IT Crowd[^] 
while (true) {
continue;
}
|
|
|
|
|
Cool! I'll have to check it out!
"Go forth into the source" - Neal Morse
|
|
|
|
|
Who...who are you, and why don't you already know about The IT Crowd?
|
|
|
|
|
I suppose I need to add BBC to my fav list then!
"Go forth into the source" - Neal Morse
|
|
|
|
|
Well you probably should but "The IT Crowd" was on Channel 4 (aka 'not the BBC')
|
|
|
|
|
I found it on netflix. It was funny but it couldn't hold my adhd attention span.
Jack of all trades, master of none, though often times better than master of one.
|
|
|
|
|
We've had problems with AD being a butthead in the past as well. Usually a reboot of the domain controller (and any secondary controllers) fixes the issue.
Most recently for us, the primary DC had temporarily failed over to the secondary, then the secondary refused to relinquish once the primary was ready again. The secondary wasn't serving rights requests properly either, and half the clients on the domain either were getting denied messages like you're seeing, or just plain didn't know which controller to ask. Rebooting both fixed the issue (primary first, I believe, but INANA.)
|
|
|
|
|
Sounds like you already told them and since they didn't hear you, it probably won't go away till the issue is fixed (or you don't answer the phone ). You might mention to them to add/re-add the server and/or pcs to the domain. It happens to us fairly regularly, shouldn't but it is Microsoft. I think the security tokens get screwed up and doing that seems to straighten it out.
Jack of all trades, master of none, though often times better than master of one.
|
|
|
|
|
Thanks! I'll pass on this good advice!
"Go forth into the source" - Neal Morse
|
|
|
|
|
You sell the software and service and support ?
You (your company) should help fix the problem, even if it is not your fault, according to pre-defined support procedures (and more so if it is a paid support).
If you find a solution and or acceptable (by both parties) workaround, then publish it and report the issue as fixed (in your bug/support call tracker).
If you cannot find an acceptable solution or workaround, escalate the issue with you own manager; tell him what you did and what the client did and check with him what would be the next steps in regards to fixing the issue.
Good luck.
I'd rather be phishing!
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
