Why bother getting the BSOD unless you’re actually trying to know exactly what the problem is? All BSOD’s are not created equal. The information pulled out of the event logs is worth good money 20 years later.
This is definitely a very similar problem to DNS zombie’s and I would suggest disabling the dns cache and flushing it using DNS name servers without a cache. Depending on your router it may be possible to configure it to force a DNS re-query. I would try that and dig out the IP address of that DNS server and feed it into another machine in the second network.
simple: get a packet capture tool like tcpdump, follow a tcp connection to it’s destination, locate an ip in that list and request the user netflix.com. another place to start might be with an mtr –help command, and you might start by mtr -n -vv -c 10 10.27.0.1. mtr does a ping and time from your machine to the remote, and places a marker on the line in the capture file so that the replay of the network can be a bit easier.
If you’re seeing the scan results, it would suggest the user is likely not aware of what’s going on. Maybe they’re running a suspected bot, maybe they’re running there own browser, maybe they’re running a program.
Adobe Photoshop is an incredible application that gives users the ability to make and edit images. However, Adobe’s software is typically protected […]
