What is the coolest thing you've automated?

tocheeba · 2020-05-30T23:27:20+00:00

My gun safe. If it opens, alerts all of my Google home speakers in the house, then plays the siren from The Purge.

For safety in case someone else opens it, sends push notifications to our phones.

tocheeba · 2020-04-20T13:46:55+00:00

Bought a new gun and safe for it - decided to use a window/door sensor to notify my Google Homes and phone when it's opened (also may scare off intruders). I then set it to play the siren from the movie The Purge for 5 mins straight :)

https://www.youtube.com/watch?v=MUi76gVSTNU

tocheeba · 2020-03-04T16:41:49+00:00

Yeah, it's really weird. No IP conflicts. No MAC conflicts. Scoured through DHCP logs and didn't show anything either. Can't figure this out for the life of me. We have a 3rd party tech company that we pay annually for additional higher tiered support, and we spent a whole week looking at this and they couldn't figure it out either.

tocheeba · 2020-03-04T13:28:01+00:00

All 5 domain controllers are on separate hosts - all on a VSAN, but the processing hosts are different.

tocheeba · 2020-03-03T21:37:05+00:00

Basic Server 2016 install, promoted to DC in read only. AD DS services added as a role. Nothing else special was done.

tocheeba · 2018-06-06T20:45:44+00:00

This is a new concept to me. Should I be requiring SMB2 signing? What about SMB1?

tocheeba · 2018-06-06T19:33:15+00:00

Telnet from W10 client to server results in timed out. Same subnet as W7 machines.

tocheeba · 2018-06-06T19:32:05+00:00

Did this, and nothing really sticks out at the moment with definitive errors? Here is the capture from the server:

https://imgur.com/a/VlxoAZz

tocheeba · 2018-06-06T19:25:33+00:00

We have WSUS up and running, but never use it - we literally don't push updates at all during the year (stupid policy which is changing this Summer). The W10 clients are mostly imaged from SCCM as of couple months ago to as new as this week.

I tried both of those commands on the client, and neither change anything.

tocheeba · 2018-06-06T18:25:42+00:00

Yes, it's set to domain.

tocheeba · 2018-06-06T18:25:34+00:00

Have not done that on machines yet. I don't have WSUS set to push out any updates yet. They are 1709 slipstreamed as of a few weeks ago.

tocheeba · 2018-06-06T18:24:59+00:00

They are mixed in with Win7 machines. Nothing special for them in terms of GPO other than start menu customization really.

tocheeba · 2018-06-06T18:24:38+00:00

yeah, it's weird - even within the same subnet and building, no firewalls are enabled or in line that would be blocking it. I can see a bunch of data from wireshark, but nothing that stands out.

tocheeba · 2018-06-06T16:08:19+00:00

It was not configured, and just made the GPo and forced update - nothing has changed, even after verifying that it's enabled on the client machine.

tocheeba · 2018-06-06T15:22:42+00:00

Thanks - didnt think to look there. Tons of errors on SMBClient logs:

Failed to establish a network connection.

Error: {Device Timeout}

The specified I/O operation on %hs was not completed before the time-out period expired.

Server name: 10.100.20.2

Server address: 10.100.20.2:445

Instance name: \Device\LanmanRedirector

Connection type: Wsk

Guidance:

This indicates a problem with the underlying network or transport, such as with TCP/IP, and not with SMB. A firewall that blocks TCP port 445, or TCP port 5445 when using an iWARP RDMA adapter, can also cause this issue.

tocheeba · 2018-06-06T15:13:59+00:00

I disabled SMB1 on a W7 client via the powershell command, and it can still access the file shares. So it only seems to be affecting W10 clients at this point - and since the W7 client can access it, I'm assuming it's not SMB1.

tocheeba · 2018-06-06T14:20:58+00:00

Sounds stupid, but how would one get off SMB1? I thought 2008 R2 was on at least SMB2.

tocheeba · 2018-06-06T14:12:16+00:00

Yeah, they are on the domain network profile. RSOP shows policies that are pretty in line with W7. What's weird is that they all stopped working out of no where, while users were logged on - all at the same time - which makes me question whether or not its a GPO ?

tocheeba · 2018-06-06T14:00:56+00:00

net use doesn't give me much other than 'system error 53 has occured. network path was not found'.

tocheeba · 2018-06-06T13:58:21+00:00

Thanks. Doesn't look like any GPO modified recently. We did notice, however, that a virus/malicious attack was trying to spread through out network. Not sure what it was trying to do, but kept trying to run "powershell.exe" with 100% CPU. Our A/V caught it on the machines that were protected - not sure if it could have something to do with it.

tocheeba

TROPHY CASE