What Are You Doing Right Now
-
@dashrender said in What Are You Doing Right Now:
If the gateway is the DNS for the internal clients, try having one of them go direct for lookups.
OMG so much broken shit...
So the problem is that their AT&T is down due to a power failure at the DMARC that they have no access to. I popped the door open with a screwdriver. Nothing in there has power. Fire alarm, other monitoring gear, nothing.
Rest of the building has power though. So fun times.
On to what's so fucked up.
The private network 192.168.1.0/24 is working and DHCP is a Windows 2012 R2 DC. But it hands out and old SBS server that does not exist as the primary DNS, then itself as the secondary DNS. The gateway is a pfSense box on 192.168.1.5 and uses a Charter Coax connection to get to the internet.
But that's not all! The DC is not the owner of the FSMO roles. I can't access the DNS MMC because of that. The old SBS server is still the FSMO role holder of ALL the roles.
But the network not working was the warehouse. This network gets its DHCP from the pfSense box and is on 172.16.44.0/24 and routes out the AT&T pipe. This DHCP only had 1.1.1.1 and 8.8.8.8 as the DNS entries.
I had hit the firewall to route the warehouse to the charter network early on, but it was still failing. No idea.
Once I arrived on site and found out that the AT&T service was down, I changed the routing again and this time it worked. Everything is going out the Charter pipe. I did also disable some weird blocker service module that was installed in pfSense so that might have helped.
Enough said, they are online and I left to dela with the customer I was supposed ot be coming to St Louis to deal with.
-
@obsolesce oh no, not already.
-
Working on a video, then RHCE practice time.
-
@hobbit666 said in What Are You Doing Right Now:
Doing a Detailed DR Plan, like a step by step on how to recover from different scenarios.
Like Building burns down, or we loose both our clusters.
Another is Ransomware.
What would your first reaction/actions be if someone phones up and says "a pop up just happened saying everything is encrypted". Would you unplug and switch off everything, then look into it?
Or would be just switch their machine off and isolate it to investigate.Personally think my reaction would be switch all servers off VMs and physical. But is that a bit OTT?
What's worth more, a few hours of unplanned but controlled downtime or recovery?
-
@jaredbusch said in What Are You Doing Right Now:
@dashrender said in What Are You Doing Right Now:
If the gateway is the DNS for the internal clients, try having one of them go direct for lookups.
OMG so much broken shit...
So the problem is that their AT&T is down due to a power failure at the DMARC that they have no access to. I popped the door open with a screwdriver. Nothing in there has power. Fire alarm, other monitoring gear, nothing.
Rest of the building has power though. So fun times.
On to what's so fucked up.
The private network 192.168.1.0/24 is working and DHCP is a Windows 2012 R2 DC. But it hands out and old SBS server that does not exist as the primary DNS, then itself as the secondary DNS. The gateway is a pfSense box on 192.168.1.5 and uses a Charter Coax connection to get to the internet.
But that's not all! The DC is not the owner of the FSMO roles. I can't access the DNS MMC because of that. The old SBS server is still the FSMO role holder of ALL the roles.
But the network not working was the warehouse. This network gets its DHCP from the pfSense box and is on 172.16.44.0/24 and routes out the AT&T pipe. This DHCP only had 1.1.1.1 and 8.8.8.8 as the DNS entries.
I had hit the firewall to route the warehouse to the charter network early on, but it was still failing. No idea.
Once I arrived on site and found out that the AT&T service was down, I changed the routing again and this time it worked. Everything is going out the Charter pipe. I did also disable some weird blocker service module that was installed in pfSense so that might have helped.
Enough said, they are online and I left to dela with the customer I was supposed ot be coming to St Louis to deal with.
WOW sounds fun
-
Thinking of trying Linux as my main driver and have windows as a boot option
-
@hobbit666 said in What Are You Doing Right Now:
Thinking of trying Linux as my main driver and have windows as a boot option
Does it have to be a boot option? Making it a VM is way more convenient if you don't need to have a passthrough graphics card.
-
@travisdh1 said in What Are You Doing Right Now:
@hobbit666 said in What Are You Doing Right Now:
Thinking of trying Linux as my main driver and have windows as a boot option
Does it have to be a boot option? Making it a VM is way more convenient if you don't need to have a passthrough graphics card.
While I agree (because 'rip the bandaid off already!'), configuring a T2 VM on a personal computer kind of blows, even with as good as VirtualBox is.
Using Boxes on Fedora or Ubuntu doesn't work well either and feels clunky.
-
Plus when you're on a Linux Distro you get a better feel for how it works and what challenges may still remain.
-
@dustinb3403 said in What Are You Doing Right Now:
@travisdh1 said in What Are You Doing Right Now:
@hobbit666 said in What Are You Doing Right Now:
Thinking of trying Linux as my main driver and have windows as a boot option
Does it have to be a boot option? Making it a VM is way more convenient if you don't need to have a passthrough graphics card.
While I agree (because 'rip the bandaid off already!'), configuring a T2 VM on a personal computer kind of blows, even with as good as VirtualBox is.
Using Boxes on Fedora or Ubuntu doesn't work well either and feels clunky.
I just used KVM to make it a full T1 on my laptop.
-
@jaredbusch said in What Are You Doing Right Now:
@dustinb3403 said in What Are You Doing Right Now:
@travisdh1 said in What Are You Doing Right Now:
@hobbit666 said in What Are You Doing Right Now:
Thinking of trying Linux as my main driver and have windows as a boot option
Does it have to be a boot option? Making it a VM is way more convenient if you don't need to have a passthrough graphics card.
While I agree (because 'rip the bandaid off already!'), configuring a T2 VM on a personal computer kind of blows, even with as good as VirtualBox is.
Using Boxes on Fedora or Ubuntu doesn't work well either and feels clunky.
I just used KVM to make it a full T1 on my laptop.
Yeah, there is that option of course too (I didn't mean to say it wasn't). I personally find the experience weird and having two distinct environments seems be better. Obviously this is opinion.
Using separated systems seems to actually get you to use one or the other, and that is why I think having them separated by the bootloader makes for a smoother transition.
Granted I'm probably the only person that believes that....
-
Digging through group policy objects.
-
@eddiejennings said in What Are You Doing Right Now:
Digging through group policy objects.
I had that fun last week. Realized the biggest one isn't working like it should, and the client wouldn't want it to work how it was setup. Someone before me really buggered that one up.
-
@dustinb3403 said in What Are You Doing Right Now:
Using separated systems seems to actually get you to use one or the other, and that is why I think having them separated by the bootloader makes for a smoother transition.
Granted I'm probably the only person that believes that....
This is what i'm thinking, have it as a separate system will "force" me to find solutions for isssues.
-
@travisdh1 said in What Are You Doing Right Now:
@hobbit666 said in What Are You Doing Right Now:
Thinking of trying Linux as my main driver and have windows as a boot option
Does it have to be a boot option? Making it a VM is way more convenient if you don't need to have a passthrough graphics card.
I agree, much better that way. Then you only turn on Windows for a task, then disable. You don't have to reboot to go in between.
-
@hobbit666 said in What Are You Doing Right Now:
@dustinb3403 said in What Are You Doing Right Now:
Using separated systems seems to actually get you to use one or the other, and that is why I think having them separated by the bootloader makes for a smoother transition.
Granted I'm probably the only person that believes that....
This is what i'm thinking, have it as a separate system will "force" me to find solutions for isssues.
Not likely. It tends to make you "have to" go to Windows and once there, you have no way to find a solution because you turned Linux off.
-
I've done this many times over the years, I always end up back on Windows as that's what I support.
My advice would be to boot into the OS you support and have VMs of the OS's you want to learn.
I've done it the other way around, and found it too inefficient to work with.
For example, I needed to print something, so I had to go and google how to install a print driver, then chase up some hacks to get it to work. When if I was in the OS I knew, I could have printed immediately.
If you don't move around, it would be much easier, as you setup once and you're good to go. I move around, so it was a continuous hassle.
-
continuing the fun with wsus...
-
Finally done dealing with setting up new cable modem, cable box and bringing down the TV from upstairs.
Lightning struck a tree in the neighbors yard that touched the cable line, sending high voltage taking out the cable modem, shorting out the HDMI output in the cable box and eventually "frying" the TV.
Ugh what a night.
-
What Linux desktop os would people recommend?
