Hey Johnny, how 'bout some coffee?
I had to setup remote access for the software guys from the Niles place to their server up in AWS. I tried yesterday via their firewall, which turned out to be the wrong way, after I broke down and asked Taco for help. He is with Lezzo at a client in California, so I really didn't want to bother him. He gave me the steps I needed to do the setup in AWS, which I just did now.
Though the place he told me to look for the security groups did not have the ones he'd created during the initial setup. I refused to just stop and ask him for help, as I knew it couldn't be that complicated. So I spent about 30 minutes clicking around the various menus until I found the groups he was talking about, in a different place. I tested it out, was able to RDP from my home IP and did the setup for the software guys.
I let Taco know I got it done and mentioned I found the security groups in a different location, and I think this irked him. I wasn't trying to say he was wrong, but wanted him to know I couldn't find it in the place he told me to. He replied back that they *were* in fact where he said they were (which they aren't as far as I could see), but that they "also" could be found in the location I figured out.
I wasn't trying to measure dicks, but I know for a fact they were not *obviously* in the spot he said they were. I clicked around forever. They simply aren't in that menu.
My trip up north today was fine. Though I accidentally caused a feedback in the network when I was unplugging and removing the old server. I found a cable from the firewall dangling and in a panic I thought I'd accidentally unplugged it from the network switch so I plugged it back into one of their two switches, so there were then two connections from the firewall into the network. A few seconds later I heard people grumbling about their computers "being down".
Someone in back blew a fuse though, so they were very focused on that being the issue that caused the network disruption. I went back by the server closet to see what was up and that is when I discovered my little mistake. Oops!!! They'll never know though. They think the blown fuse turned off something.
This did cause chaos for me for a few minutes, as I was trying to help this sales guy get his VPN setup and I had people texting and freaking about losing their connections.
I am hoping the remainder of the week is quiet, but with this software guy there looking into issues with their website I am SURE it is going to come back to haunt me. No doubt they will blame the server moving to AWS as the issue with the ecommerce site on the server not working. It's all Greek to me though, and I will play stupid if they say some changes need to be made... 'Okay, what changes? I'm no webmaster.'
The Sparrow works till six tonight. He'll get home and it'll be time for bed already. We've both been so tired this week. I know my sleep has been constantly disrupted.
Though the place he told me to look for the security groups did not have the ones he'd created during the initial setup. I refused to just stop and ask him for help, as I knew it couldn't be that complicated. So I spent about 30 minutes clicking around the various menus until I found the groups he was talking about, in a different place. I tested it out, was able to RDP from my home IP and did the setup for the software guys.
I let Taco know I got it done and mentioned I found the security groups in a different location, and I think this irked him. I wasn't trying to say he was wrong, but wanted him to know I couldn't find it in the place he told me to. He replied back that they *were* in fact where he said they were (which they aren't as far as I could see), but that they "also" could be found in the location I figured out.
I wasn't trying to measure dicks, but I know for a fact they were not *obviously* in the spot he said they were. I clicked around forever. They simply aren't in that menu.
My trip up north today was fine. Though I accidentally caused a feedback in the network when I was unplugging and removing the old server. I found a cable from the firewall dangling and in a panic I thought I'd accidentally unplugged it from the network switch so I plugged it back into one of their two switches, so there were then two connections from the firewall into the network. A few seconds later I heard people grumbling about their computers "being down".
Someone in back blew a fuse though, so they were very focused on that being the issue that caused the network disruption. I went back by the server closet to see what was up and that is when I discovered my little mistake. Oops!!! They'll never know though. They think the blown fuse turned off something.
This did cause chaos for me for a few minutes, as I was trying to help this sales guy get his VPN setup and I had people texting and freaking about losing their connections.
I am hoping the remainder of the week is quiet, but with this software guy there looking into issues with their website I am SURE it is going to come back to haunt me. No doubt they will blame the server moving to AWS as the issue with the ecommerce site on the server not working. It's all Greek to me though, and I will play stupid if they say some changes need to be made... 'Okay, what changes? I'm no webmaster.'
The Sparrow works till six tonight. He'll get home and it'll be time for bed already. We've both been so tired this week. I know my sleep has been constantly disrupted.