When BYOD is no longer allowed. L Tech Support |
- When BYOD is no longer allowed. L
- Just do what the screen says
- Can you reset my password? Again?
- Don't Mind Me ... I'm Just Tech Support
| When BYOD is no longer allowed. L Posted: 01 Oct 2021 02:09 AM PDT Hello everyone. I have an interesting story for you folks. User: hello IT, this is finance. I can't access the network at all. Not even the internet. Me: strange, okay I'm coming. I go down and I see that she's not getting an IP address. I'm thinking okay, strange. So I ask did anyone come and use this docking station? She's like yes, the finance director bought his personal laptop and he connected this blue cable to it but it didn't work. Then I realised what has happened. Port security kicked in, shutting down the port. I go back to my desk and reset the port allowing the user to continue her work. But now, I need to raise an incident report and get the finance director to sign it, but he refuses. I call my manager and he tell him that he's refusing to sign. My manager goes to the CEO and gets him involved. After informing of what happened, BYOD was no longer allowed.. EDIT: WiFI was added after the incident, but it was only for Mobile phones and staff members had to sign forms to allow them to connect. [link] [comments]  |
| Posted: 30 Sep 2021 10:12 AM PDT TL;dr below. I changed careers a few years ago. I have a couple of degrees in computer maintenance and networking technology. I got tired of doing that and made a career change into industrial maintenance. I work for a major food producer now and work on everything from bearings and grease to electrical and printers. I've only done this for about 3 years now. Most of you reading this in the US have my product in your refrigerator right now. One of the machines goes down this morning. It is a very advanced machine. Kind of crazy all of the technology used on it. I come over to the call late to see if I can help. One of my fellow mechanics is there along with our lead. I'm just a bystander at this point. They call in our supervisor, he calls his supervisor, and another lead shows up. There are 6 of us working on this machine. I poke around a bit based on the error on the screen. I talk to my lead and tell him what I think it is. I'm kinda brushed off, ignored. I watch a little longer. I speak up again and am ignored They're pulling the machine apart checking on different things. We've been here for an hour at this point and I'm freezing my ass off. Plus the company is losing between$15-20k an hour that the equipment is down. I look at my buddy and say "hand me your dykes bro" I reach down and clip a zip tie off some cables while everyone else is looking at something else. I look up and everyone is staring at me... the big boss incredulously asks, "what did you do???" At first I'm thinking I f**ked up and accidentally cut something I shouldn't have... "I cut a zip tie..." "All the errors just went away, show me what you did!" I proceed to show them that I cut a zip tie off of a multi-mode fiber jumper that was causing a kink (not really a kink, but a sharp bend). Then I had to explain that fiber shouldn't have a bend > 30 degrees. This machine has about 8 drives that control servo motors, each drive is in series with the drive next to it linked with MM tx/rx jumpers between them. Errors on the screen: "checksum failed" "check fiber optic cables"... "x1 drive checksum error" "check fiber optic cables"... "x2 drive checksum error" and so on... This isn't to degrade them in any way, they are all extremely intelligent and they would normally run circles around me. If fact, I'll probably end up calling them for help by days end! TL;DR screen showed checksum error, look at fiber optic cables. Zip tie caused kink. [link] [comments]  |
| Can you reset my password? Again? Posted: 30 Sep 2021 10:36 PM PDT While I don't work in IT, it never seems to fail that I become the "Tech Guy" and get asked to do all the tech stuff on top of my regular job. I work in public safety, so we weren't exactly hired for our computer skills and our agency is not really big enough to justify a dedicated IT position. I was given the task (among several other things) of creating and deleting user accounts and resetting passwords for our records software. My biggest headache of course was re-setting locked accounts. Some people forget to type their username when logging in and end up locking the last user's account quite often, while others seem to just always forget their password. But one user always seemed to have trouble. Also, most people do not have one computer they always use. There are many computers and users won't likely use the same computer one day to the next. This will come up later. I get an e-mail from a user one morning that their password isn't working. I log in and see that they have 9 failed password attempts, which meant not only did they type the wrong password 3 times and disable their account, they tried six more times after being told "Contact your system administrator." Not unusual and it might not even be their fault as mentioned above. I unlock the account, give them a generic temporary password, and go on about my day. A few hours later I get a call from the same user. User: That password isn't working. I typed "some_generic_passowrd", and it isn't working. Me: That's the correct password. I'll reset it right now and you can try to log in. User: Nope, still not working. I see the failed log in attempt under his profile so at least I know they got their username right. Since I have them on the phone, I give them a super simple password and have them log in. User: [lots and I mean LOTS of typing and clicking] It's still not work… oh wait, there we go. It says my password expired. I thought you just reset it for me. Me: Yes, but it is only temporary. You have to create your own password now and it has to have be [list of requirements]. Make sure it is something you will remember. User: OK, thanks. I don't think much of it and go about my day. A few days later I get an e-mail from User asking to reset their password. They're super apologetic about it but honestly, it's just a forgotten password; I've had worse calls [like someone deleting an entire person by accident]. Oddly the account is not locked out and there are no failed log in attempts, so I give them a call. Me: Hey I got your e-mail, it's ok. Your account shows it isn't locked and I don't see any failed log in attempts. Are you using your username? What is it telling you when you try to log in? User: [lots of typing and clicking] It says "Could not establish a connection to the server" I typed my username and password and that's all that happens. That's not unheard of. Me: That's not unheard of. Close the log in prompt and try again. Make sure you let me know what you are doing and what messages show up. User: [walking me through each step they're taking] And I'm in, you fixed it! Me: Ok, sounds good to me, have a good day! This happens a few more times over the next several weeks and they are never able to really explain what happens before I get involved. Inevitably by time they get me on the phone it seems to be working again. There are several times where I again notice they don't have any failed log in attempts and their account is not locked. I do reset their password a few times but never end up having too much trouble getting them in with a little patience. Fast forward a few months and my co-worker and I are asked to assist with a server migration. One task is to go to each computer in the building and enter the new server configuration, update the software, and re-name the old server settings. This is accessed from a settings button on the log in screen. A new dialogue box allows you to select an existing server configuration or create a new one. I set up the first few computers without an issue, but then I come to a computer that I know User uses quite often. I open the server configuration settings and there are TEN servers listed. The legacy server, the test server and 8 servers with variations of User's username or full name. I open the settings for the first one and I find something like: Server Address: [user's username] Port: [super_simple_password] I find variations of this for every additional server entry in the list. This explains everything; the loads of clicking and typing and the "Could not establish a connection to server" was User going into settings and creating, and saving, a new server each time. I chuckled and called User over. We chalked it up to they were never shown how to properly log in and they had a laugh too. User was happy, they didn't have to keep asking for new passwords, and we didn't have to keep resetting them. By the end of the update, I found around 5 more times where this was done on other computers. [link] [comments]  |
| Don't Mind Me ... I'm Just Tech Support Posted: 30 Sep 2021 01:39 PM PDT Here's a story from my last deployment to Iraq (I used to be a 'SIGO,' which is kind of like a help-desk manager for the Army) - Received a call from the Operations Officer (no, I'm not going to explain what an Ops Officer does, or explain any other Army acronyms, abbreviations, or jargon. This post would be ridiculously long) telling me he needed a new VoIP phone (we used VOIP phones on our classified network, POTS phones for unclassified calls), because his was broken. Since I took care of all officer issues personally, I grabbed a spare phone of the shelf and headed over to his office. When I arrived, he was on the POTS phone talking to a buddy from another unit. He gave me a disdainful look, and pointed to his VOIP phone, which was sitting on the printer in his office. When I picked it up, bits of plastic fell off, the screen was cracked in multiple places, and the handset was held together by the wires inside. Jeezus? WTH happened to this poor phone? Oh well, phone surely doesn't work. I plugged in the spare, and checked that it worked correctly. I was waiting for the Ops O to get off the phone to tell him the new VOIP phone was ready for him when I overheard this: "Yeah, I am getting a new VOIP phone. I got mad at what I heard and threw the old one against the wall." [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