Damn I'm vastly underpaid (also I still don't manage this shit with my phone).
I understand that there's lots of our tech uses flash still because $$$$ but I've never thought to myself "gee I need to log in to VMWare's web stuff on my phone" I'll just stop by a PC somewhere. Guaranteed there's one within a stones throw of me I can use.
If I'm out and about, I probably don't have good cell service anyways.
Wait, was this in response to what I said? I should have clarified that it's making $165,000 for the company. I'd see some compensation in the form of bonuses for something like that.
Honestly I'm grateful for the push to get to a newer version, but man it's irritating. Apparently the vendor who installed all of this used the built in ODBC driver, so now I need to change that for a supported driver.
This software straight crashes if it's installed on a PC with a name longer than 14 characters.
*flips a fucking table*
life's a game that you're bound to lose / like using a hammer to pound in screws
fuck up once and you break your thumb / if you're happy at all then you're god damn dumb
that's right we're on a fucked up cruise / God is dead but at least we have booze
bad things happen, no one knows why / the sun burns out and everyone dies
That program must be hella fucking old if it shits itself over a >=15 character netbios name
We have netbios disabled both in our gold image and with DHCP
It's probably doing something stupid like superimposing the computer's name into a variable that takes 14 characters because it was designed for that though.
Not enough space = crash on install. Even if it doesn't have a network component it probably has the functionality squirreled away.
14 character pc name is just too coincidental to not be that
not a doctor, not a lawyer, examples I use may not be fully researched so don't take out of context plz, don't @ me
+4
Apothe0sisHave you ever questioned the nature of your reality?Registered Userregular
edited August 2018
I have 1000 IP addresses
For which I need to determine the FQDN
I have AT LEAST 3 separate DNS infrastructures to query and some number of those IP addresses willl resolve but with no guarantee that each will resolve, that they will resolve the same way or that each IP will resolve only with one DNS environment
Oh and each IP resolves to at least 1, usually 2 and sometimes 3 PTR records
I have to select the winning FQDN (which isn’t clear yet but will probably be the longest one) for each IP.
OH and not all DNS infrastructure is accessible from a single machine and the scripting options are not uniform across those machines
This is a heckin’ complicated process.
Apothe0sis on
+2
mojojoeoA block off the park, living the dream.Registered Userregular
edited August 2018
remember that time you did a guy a favor as an admin and he has your cell phone number?
And remember how he now never calls the help desk, he instead calls you direct. At like all hours? For things that you don't even manage in the company?
Those were good times right?
mojojoeo on
Chief Wiggum: "Ladies, please. All our founding fathers, astronauts, and World Series heroes have been either drunk or on cocaine."
We don't have work cell phones for our IT staff here, save for the manager. among IT we've traded phone numbers, but I would never in a million years give out a personal number to a user.
We don't have work cell phones for our IT staff here, save for the manager. among IT we've traded phone numbers, but I would never in a million years give out a personal number to a user.
We won't even share our extensions for our desk phones.
+1
FFOnce Upon a TimeIn OaklandRegistered Userregular
This happened the other day.
Department has a server with an IP address of 10.x.y.z and FQDN blah.mywork.edu. The server's IP address has been 10.x.y.z for at least 2 years now, as has the FQDN. Clients machines start randomly not connecting to the server, but some still do so not a huge issue (server runs a render farm), but it's student projects so ¯\_(ツ)_/¯
Department contacts Networking group themselves, as my group doesn't admin that particular server. Department also says that when they ping the server IP address, they get no response, but the client machines can connect. Networking group doesn't respond for 3 days, sends a level 2 technician who works with them frequently.
Level 2 guy shows up, looks at the server says the problem is that it needs to be removed from our domain and re-added (we have two domains, one is admin'd by my group, the other is admin'd by core IT). Removes the server from our domain, but can't re-add it because the previous record still exists. (note: we have a ton of DC's and they're all a shit show, nothing syncs reliably) Level 2 guy changes the name of the server, re-adds the server to the domain. IP address of the server still doesn't ping. Level 2 guy gives up. Contacts Networking group.
Networking guy responds and says that the IP address, 10.x.y.z is out of the range for static IP addresses so it shouldn't have ever worked, tells them the IP address needs to be set to 10.x.y.9 before anything will work. Also recommends removing the server from the domain (again) and re-adding it.
Level 2 guy says to change the server IP to 10.x.y.9 and tells the department to contact my group about removing and adding the server to our domain because it's obviously a problem with our domain at this point.
Department still doesn't contact my group, mostly because they're dumb, but also because a lead in the department insists on only contacting Networking group. I hear about what's going on with the server via complaints to our group about the render farm + client machines, as the client machines are our responsibility.
Myself and one of my technicians go look at the server. Department lead insists that I can't fix the issue (because I started as a Mac guy, among other reasons), and insists on contacting Networking group again. While she's out doing that, I sit down with my tech and the tech from the department.
nslookup blah.mywork.edu
blah.mywork.edu
10.x.y.z
Ok, this is good, the forward DNS entry isn't boned. (This was also before they told me the level 2 guy said to change the IP)
nslookup 10.x.y.z
** server can't find z.y.x.10
Oh ho! Where'd the entry go? Department tech tells me that he had to set the IP address of the computer to 10.x.y.z the other day, because it somehow got changed to 10.x.y.123. Also, Networking group told us to set the IP of the server to 10.x.y.9. I tell them no, we're not doing that.
nslookup 10.x.y.123
123.y.x.10.in-addr.arpa name = blah.mywork.edu
Huh, ok cool. So the reverse entry is screwed up. Easily done, just tell Networking group that the reverse entry is broken and to fix the entry to match the forward entry (again, the IP had been 10.x.y.z for a couple years). Department lead rushes in, insists on taking a picture of the nslookup outputs and sending them. Runs back out of the room. Department lead comes back with good news! Networking group says all you have to do is set the IP address of the server to be 10.x.y.123 and that should fix the problem!
.....
I tell Department lead that no, that will not fix the issue, and it's a stupid thing to do as it'll just fix the reverse entry while breaking the forward entry. Department lead yells that Networking group always helps her fix issues and there's no way Networking group is wrong. Department tech makes the change, surprise, nothing works. I look up the forward and reverse entries again to show Department lead that it's now broken in the exact way I said it would be. She takes another picture and runs to send it to Networking group.
Department lead comes back with news! Networking group has definitely fixed the issue now. I ask what they did.
The forward and reverse entries for blah.mywork.edu are now set to resolve 10.x.y.123 and everything connects and works again.
I have AT LEAST 3 separate DNS infrastructures to query and some number of those IP addresses willl resolve but with no guarantee that each will resolve, that they will resolve the same way or that each IP will resolve only with one DNS environment
Oh and each IP resolves to at least 1, usually 2 and sometimes 3 PTR records
I have to select the winning FQDN (which isn’t clear yet but will probably be the longest one) for each IP.
OH and not all DNS infrastructure is accessible from a single machine and the scripting options are not uniform across those machines
This is a heckin’ complicated process.
I ended up with all but 81 FQDNs. No one can tell me if they are reliable or even how they came to exist on any of the DNS servers at all. But that was an exercise.
Because if you're going to attempt to squeeze that big black monster into your slot you will need to be able to take at least 12 inches or else you're going to have a bad time...
Today I had an operations manager tell me we didn't really have to worry about the system missing a message because "message queues are reliable and a failure would be an exceptional event".
Posts
Wait, was this in response to what I said? I should have clarified that it's making $165,000 for the company. I'd see some compensation in the form of bonuses for something like that.
https://forums.penny-arcade.com/discussion/comment/39982747/#Comment_39982747
Yeah this started with Cog saying Apple should put Flash on the iPhone.
Ah
the "no true scotch man" fallacy.
Yay.
Honestly I'm grateful for the push to get to a newer version, but man it's irritating. Apparently the vendor who installed all of this used the built in ODBC driver, so now I need to change that for a supported driver.
so the regularly scheduled sysadmin thread broadcasting then
XBL:Phenyhelm - 3DS:Phenyhelm
Oh deer.
*flips a fucking table*
the "no true scotch man" fallacy.
fuck up once and you break your thumb / if you're happy at all then you're god damn dumb
that's right we're on a fucked up cruise / God is dead but at least we have booze
bad things happen, no one knows why / the sun burns out and everyone dies
We have netbios disabled both in our gold image and with DHCP
the "no true scotch man" fallacy.
the "no true scotch man" fallacy.
It's probably doing something stupid like superimposing the computer's name into a variable that takes 14 characters because it was designed for that though.
Not enough space = crash on install. Even if it doesn't have a network component it probably has the functionality squirreled away.
14 character pc name is just too coincidental to not be that
For which I need to determine the FQDN
I have AT LEAST 3 separate DNS infrastructures to query and some number of those IP addresses willl resolve but with no guarantee that each will resolve, that they will resolve the same way or that each IP will resolve only with one DNS environment
Oh and each IP resolves to at least 1, usually 2 and sometimes 3 PTR records
I have to select the winning FQDN (which isn’t clear yet but will probably be the longest one) for each IP.
OH and not all DNS infrastructure is accessible from a single machine and the scripting options are not uniform across those machines
This is a heckin’ complicated process.
And remember how he now never calls the help desk, he instead calls you direct. At like all hours? For things that you don't even manage in the company?
Those were good times right?
Most folk know or have to be told only once, use the helpdesk unless its X.
then there's those other people. 5 am "the modem is down what do I do!?!?!?!?!?!?!"
Microsoft is crashing.
Might want to report that to the SEC just to make sure it's not insider trading.
We won't even share our extensions for our desk phones.
Department has a server with an IP address of 10.x.y.z and FQDN blah.mywork.edu. The server's IP address has been 10.x.y.z for at least 2 years now, as has the FQDN. Clients machines start randomly not connecting to the server, but some still do so not a huge issue (server runs a render farm), but it's student projects so ¯\_(ツ)_/¯
Department contacts Networking group themselves, as my group doesn't admin that particular server. Department also says that when they ping the server IP address, they get no response, but the client machines can connect. Networking group doesn't respond for 3 days, sends a level 2 technician who works with them frequently.
Level 2 guy shows up, looks at the server says the problem is that it needs to be removed from our domain and re-added (we have two domains, one is admin'd by my group, the other is admin'd by core IT). Removes the server from our domain, but can't re-add it because the previous record still exists. (note: we have a ton of DC's and they're all a shit show, nothing syncs reliably) Level 2 guy changes the name of the server, re-adds the server to the domain. IP address of the server still doesn't ping. Level 2 guy gives up. Contacts Networking group.
Networking guy responds and says that the IP address, 10.x.y.z is out of the range for static IP addresses so it shouldn't have ever worked, tells them the IP address needs to be set to 10.x.y.9 before anything will work. Also recommends removing the server from the domain (again) and re-adding it.
Level 2 guy says to change the server IP to 10.x.y.9 and tells the department to contact my group about removing and adding the server to our domain because it's obviously a problem with our domain at this point.
Department still doesn't contact my group, mostly because they're dumb, but also because a lead in the department insists on only contacting Networking group. I hear about what's going on with the server via complaints to our group about the render farm + client machines, as the client machines are our responsibility.
Myself and one of my technicians go look at the server. Department lead insists that I can't fix the issue (because I started as a Mac guy, among other reasons), and insists on contacting Networking group again. While she's out doing that, I sit down with my tech and the tech from the department.
Ok, this is good, the forward DNS entry isn't boned. (This was also before they told me the level 2 guy said to change the IP)
Oh ho! Where'd the entry go? Department tech tells me that he had to set the IP address of the computer to 10.x.y.z the other day, because it somehow got changed to 10.x.y.123. Also, Networking group told us to set the IP of the server to 10.x.y.9. I tell them no, we're not doing that.
Huh, ok cool. So the reverse entry is screwed up. Easily done, just tell Networking group that the reverse entry is broken and to fix the entry to match the forward entry (again, the IP had been 10.x.y.z for a couple years). Department lead rushes in, insists on taking a picture of the nslookup outputs and sending them. Runs back out of the room. Department lead comes back with good news! Networking group says all you have to do is set the IP address of the server to be 10.x.y.123 and that should fix the problem!
.....
I tell Department lead that no, that will not fix the issue, and it's a stupid thing to do as it'll just fix the reverse entry while breaking the forward entry. Department lead yells that Networking group always helps her fix issues and there's no way Networking group is wrong. Department tech makes the change, surprise, nothing works. I look up the forward and reverse entries again to show Department lead that it's now broken in the exact way I said it would be. She takes another picture and runs to send it to Networking group.
Department lead comes back with news! Networking group has definitely fixed the issue now. I ask what they did.
The forward and reverse entries for blah.mywork.edu are now set to resolve 10.x.y.123 and everything connects and works again.
Because, fuck you, that's why.
What the fuck
I assume it's a DNS problem because DNS.
the "no true scotch man" fallacy.
Well, did you?
The access was inside of them all along
the "no true scotch man" fallacy.
I ended up with all but 81 FQDNs. No one can tell me if they are reliable or even how they came to exist on any of the DNS servers at all. But that was an exercise.
Ours is fine, but it's an MFP style one. Scans drop right into a network directory as PDF.