How to Fix: Unable to Join Windows Domain from a Laptop Connected over Wifi

I'll get to the solution first for this issue right off the bat.  To join a Windows domain, you have to be able to connect to a domain controller using host name resolution.  The simplest way to test that is working is to ping your domain name (e.g., companyname.int):

ping companyname.int

If you get a response from one of your domain controllers, you should be able to join the domain.  If not, you won't be able to join the domain.

In our instance, we had a laptop connected over our wifi that was failing to join the domain.  We'd been able to join laptops to the domain over wifi previously, so after some help from Google, we discovered the "ping your domain" test.  That was not working.  ipconfig/all showed that the first DNS server in the list of DNS servers was 8.8.8.8.  Huh, well, internal name resolution isn't going to work using that DNS server!  We manually removed 8.8.8.8 from the list of DNS servers on the laptop and it was able to join the domain.

It turns out that our network admin configured 8.8.8.8 as the first DNS server on the DHCP server running on our office's main router several months back when we had some internal DNS server issues.  At that time, Internet access stopped working for the office, since DNS was no longer working, and adding the 8.8.8.8 DNS server fixed that.  Probably would be best to added it to the end of the DNS servers list instead.

Enabling Multicast on Ubuntu

Enabling Multicast on Ubuntu

For some unknown reason, Ubuntu doesn’t install allowing access to multicast from the shell, apps, etc.  You have to enable it by editing the /etc/sysctl.conf file:

sudo vi /etc/sysctl.conf

And add these parameters:

net.ipv4.conf.default.rp_filter = 0

net.ipv4.conf.all.rp_filter = 0

net.ipv4.icmp_echo_ignore_broadcasts = 0

HOWEVER - it looks like .default and .all don’t necessarily do the trick.  On some servers we’ve had to explicitly set it for specific NICs, e.g., .eth1. Instead of .default and .all

I had to set the rp_filter for eth1 explicitly:

sudo sysctl -w net.ipv4.conf.eth1.rp_filter=0

now it works

Then load the params to the running systems (or reboot):

sudo sysctl -p

Fix for Norton Mobile Security (Android) reporting "This network is Compromised by an unknown third party that may view and alter your communications"

This started happening on my Android devices last night.  Unfortunately, it cost me an hour or so of sleep because I started scrambling around changing my wifi network password then updating all the umpteen devices that connect to it.  Then, when I got to work, NMS reported my work wifi as compromised as well!  Seriously?!??

Turns out, it's a false positive alert due to a bug introduced in an application update that was published last night.  It's since been fixed.

Norton Community post from Norton itself reporting the issue and its eventual resolution:
https://community.norton.com/en/forums/nms-wifi-security-network-compromised-alert

To fix the issue, go to Google Play, search for Norton Mobile Security and update the application.  The annoying alerts should go away.