"Everything is configured properly." Tech Support |
- "Everything is configured properly."
- Well... F*ck...
- "It won't let me edit the file."
- Clone wars
- User can't sign in
- Oh, passwords, how I wish I could quit you...
"Everything is configured properly." Posted: 02 Sep 2019 11:11 AM PDT I'm working a case for my customer for intermittent service, and I'm going through the usual checklist for the service type. We've been seeing a common issue lately with a certain provider and their modem settings causing issues for our VPN tunnels and managed services. I have the process down so well I can call and have the whole process done in a few minutes. This one was not so easy. I ask the provider about the usual: line history, stats and outages, nothing of interest. Here comes the big question. IFIX: "So there's a few settings on the modem that can cause issues for us sometimes, I was hoping you could check for those." VENDOR: "Everything is configured correctly." . . . Um VENDOR: "I see the line is up and the modem uptime is 5 days, so the customer did not restart it. Since the troubleshooting was not performed, we will close this ticket." IFIX: "Hold on, actually yes they did restart it, 5 days ago. the problem started a week ago. It did not solve the problem. I told you that 3 minutes ago." VENDOR: "Ok we are seeing no issues with the service, can I help you with anything else?$ IFIX: "Yes, you can check the modem for the settings I asked you to. I don't care if you see it configured "correctly", what is correct to you may not be correct for me." VENDOR: "Okay let me log into the modem." IFIX: "Wait, so you haven't even logged into the modem yet?" VENDOR: "No, I'm logging in now." . . . . . FACEPALM Guess what? 4 out of the 5 big no no settings were turned on. This guy should just send me his paycheck. It must be huge if he can download the modem config to his mind. [link] [comments] |
Posted: 03 Sep 2019 12:53 AM PDT Verschlimmbessern German - verb Breaking something further while trying to fix it. This is a story about me, trying to fix something and nearly fuck up. Disclaimer: non nativ english, on mobile, only the management approved go to in-house tech-savvy unofficial it guy Everything started with a coworker complaining that she isn't able to send anything to the plotter. Of course this, story has to involve a printer, hasn't it? After she left for the day, I sat down at her Desk and tried to fix, this printer issue. After some tries to get it running by fiddling around in its settings, I decide to remove the printer and it's driver to reinstall it. Error: "Can't do this. Resource is being used by printspooler." Okay, simple. Restart PC into safe mode and try it from there. Win + r msconfig Entering admin credentials Check "Boot to safe mode minimal" Reboot PC rebooted and I tried to get to the system configuration. As it wouldn't accept the admin credentials, it dawned to me that it wasn't the best idea, to cut the connection to the network, where the admin user was located. I had no idea, if there was a local admin user. And as it only would reboot into safe mode, I had manage to brick this pc, 'cause without the local admin credentials I could not get back into the msconfig window. I was, considering my options. Declaring defeat and call our "actuall IT guy" to fix it, which could take from a few, hours, up to a, week or two before he would show up, or I could try to fix it my self. I opened up Google on my pc and started searching. I found something about registry editing via cmd which it wouldn't let me do. And after some time and trying I read that you could change the safe mode by getting into the system, recovery screen. Boot - forced shutdown Boot - forced shutdown Wiping the sweat of my forehead Boot - please wait - system recovery There I clicked "safe mode with network", rebooted and was able to get out of safe mode eventually. While doing this all, I remembered that the print spooler is a service, which should be listed in the task manager. After logging in, I stopped the spooler, went to the print drivers, clicked remove and Error: "can't remove driver - print spooler not running" Shutdown -> go home... [link] [comments] |
"It won't let me edit the file." Posted: 02 Sep 2019 05:41 PM PDT I work as a security guard while working on my IT degree. We finally got some more guards which was a god send because we were crazy understaffed. My supervisor and I were pulling 70 hour weeks. Unfortunately our client isn't very fast at setting up new accounts for our guards. It ends up taking 1-2 weeks before they have access to the network drive. All our daily logs and reports are done through the computer. I show up to relieve my new coworker the other day and he tells me he's having issue using the blank Daily Activity Report (DAR) my supervisor sent him so he wouldn't have to do hand written ones till he gets full access. I ask him to show me what was happening. He pulls up outlook and opens up the preview of the DAR. "See! It won't let me edit the DAR", as he starts clicking randomly on cells and typing. TL;DR Coworker tries to edit the preview version of the file in outlook. Very confused. [link] [comments] |
Posted: 02 Sep 2019 11:56 AM PDT I must admit - the following happened to me and it took me ages to find the trivial solution. At a teaching hospital, everybody had just gotten used to that newfangled computer stuff when the grown-ups decided to upgrade to a networked structure, which before the turn of the century was not really common. The network was installed, and on Day X the supplier dropped approx. 200 preconfigured PCs at the loading Dock to distribute to their designated locations. Being just a lowly IT support engineer, I got to do most of the physical job, whereas my more senior colleagues gathered around the PDC (primary domain controller, like a login authentication server) to greet each new machine appearing on the network with cheers. After all the hardware was accounted for and every single PC seemed to work just fine, we even got thanked by the clinic manager. A few days later, calls started coming in about people not being able to log into their user accounts, but there was no systematic behaviour we could pinpoint - on some days, a user at position A had a problem but his login credentials worked just fine on position B, whereas the opposite was true a few hours later. Users kept moving through the building to find computers where they could log in, quite often ending up in neighbouring departments. Management was not concerned, as they expected teething problems for the new systems anyway, so no systematic approach to fault isolation was requested. Careful plotting of the problem reports showed a pattern after some time - there were always the same clusters of computers involved. If A worked, B and C would always have the problem and vice versa. Same with D, E and F respectively. Finally it dawned on me - the supplier had preconfigured three batches of 60 odd computers each, changing the hostname between batches but not the IP (network) addresses - so whichever PC from a group of identically configured started first "won" as the switch would reject the others as being duplicated IP addresses. As those were smart clients, no fancy network boot etc., the only indication was the inability to log in as the PDC was unreachable to the "clones". The actual fix was easy, less than a day of manually deconflicting the IP addresses and everything was done. Supplier was sooo embarrassed... Edit: made solution unambiguously clear [link] [comments] |
Posted: 02 Sep 2019 01:42 AM PDT This all happens just as i sit at my desk Monday morning, before any breakfast or coffee and i technically don't start work for another 15 minutes User: I cant sign in, help me! Me: Whats the error message? User: IDK? Me: Ok then, where is your PC? User: At my desk Me: Well go get it then, i cant look at the error message with it there now can i... User: Goes to get PC and returns Me: Well sign in then and let me read the message Users computer: Password needs to be changed, click OK to proceed Me: ... [link] [comments] |
Oh, passwords, how I wish I could quit you... Posted: 02 Sep 2019 09:06 AM PDT I support a few different products, all of which have passwords that periodically expire. One is a web app that we can easily reset if their admin remembered to put an email in their profile, and which we can unlock if they just forgot their password; one is a product that uses the same credentials as the company's primary product, but because it's an auxiliary one doesn't let you reset your password from within it and doesn't have enough detail in the message to tell you your password expired. This is a brief sample of my normal calls (C is the caller, M is me, WA is the web app, AP is the auxiliary product): C: Hi, it says I'm locked out of WA. M: Okay, it looks like you're locked for invalid sign on attempts, I've unlocked you, you can log in with the same password. C: Okay, is the password (proceeds to tell me what they think their password is until I can talk over them and cut them off)? ... C: Hi, I'm locked out of WA. M: Okay, it looks like you're locked for invalid sign on attempts, happened yesterday. C: How is that possible? I wasn't here yesterday. M: That's exactly why it locked you out. (Unlocks them and they can log in again) ... C: Hi, I'm locked out of WA. M: Okay, it looks like you're locked for invalid sign on attempts, I've unlocked you. C: I don't know my password, can you reset it? M: You don't have an email in your profile, so you'd need to talk to your admin. C: Oh, my email is... M: I can't add it, you need your admin. OR, after I unlock them: C: I tried to reset my password but I didn't get it. M: (checks their profile and sees that their email is the SMS address for a Verizon phone... which has a character limit that cuts off the actual temporary password... So they effectively have no password now...) You'll need to talk to your admin. ... Bonus WA call C: I'm locked out of WA. M: (looks and sees that their admin did it and put a note that they've been fired) ... C: I can't log into AP, it says it's the wrong password but I've been using the same password for months. M: Okay, can you log into (main product)? C: Oh no, this login is just for AP. M: (tries not to physically bang my head against the desk as I explain that AP uses the login for the main product and to try it anyway) C: "Enter new password." M: Great, it expired, so just reset it and you'll be good to go. ... And last but not least C: I can't log into AP, it won't take my password. M: Okay, can you log into (main product)? C: Yes. M: (goes through normal troubleshooting) C: (gets frustrated and insists the program is broken) M: Okay, can I remote in? (watches them log into the main product and then fail to log into AP) C: See, it's not working! M: Okay, so you'll want to change the password after this call (they won't but I've now covered my ass and the company's if someone overhears and uses it), but can you tell me your password? C: Yeah, it's (short simple password they can't possibly forget) M: (types the password slowly to be sure that remote connection lag doesn't fuck it over, successfully logs in) C: How did you do that??? (If I'm feeling charitable at this point, I'll tell them there might be a stuck key somewhere and to just type it slowly and hit everything firmly. I have them log in themselves and they can now do it. This is not the hill you choose to die on and cuss out tech support about, you'll feel pretty dumb when it's over.) [link] [comments] |
You are subscribed to email updates from Tales From Tech Support. To stop receiving these emails, you may unsubscribe now. | Email delivery powered by Google |
Google, 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States |
No comments:
Post a Comment