@Dashrender said in Printer and UniFi AP:

Does that printer have a bunch of unneeded protocols running on it?

Might. I'll take a look at it again and maybe to a packet capture.

I think I finally figured it out! I made a test SSID and turned off "Multicast and Broadcast Filtering" and all of a sudden I am able to ping it. I'm not sure why this would make such a difference.

@Dashrender said in Printer and UniFi AP:

@Markferron said in Printer and UniFi AP:

Can't believe I forgot this piece of info.
If I ping the printer from my laptop for an extended period of itme it's almost always ends up being a 50% packet loss. So I can access it on WiFi, but for maybe only 15 seconds at a time before it drops out again.

If you have two pings going - one to that printer, and a second to a printer you don't have issues with, do both pings stop replying, or only one?

Only the one to the problem printer stops.

Can't believe I forgot this piece of info.
If I ping the printer from my laptop for an extended period of itme it's almost always ends up being a 50% packet loss. So I can access it on WiFi, but for maybe only 15 seconds at a time before it drops out again.

@scottalanmiller said in Printer and UniFi AP:

You can ping everything else on the VLAN?

Yup. I have other printers and devices already on that network. Everything shows up just fine.

Oh and all of this testing I've been doing is on the same VLAN/subnet of the printer.

I have a Sharp MX-C301W printer connected thought Ethernet that I am having issues connecting to on my UniFi access points. All wired clients (including the UniFi APs) can consistently ping the printer or bring up the web interface without any issues. However, I had an old Meraki AP laying around and I was able to connect to the printer on a similar SSID.
I've checked the cable, no problems, changed to another network jack, no difference. I can connect a device to the jacks and they work flawlessly. So far, I haven't noticed any other issues accessing wired devices from my UniFi APs. My APs are on the latest firmware (UAP-AC-PRO 4.3.21.11325) and my controller is on 5.14.23.

Any suggestions on things to test?
Thanks ahead.

@scottalanmiller said in Blocking spoofed emails O365:

https://support.knowbe4.com/hc/en-us/articles/212679977-Domain-Spoof-Prevention-in-Exchange-2013-2016-Office-365

Actually that might work. If the sender is outside the organization and the sender address includes our domain, just put in junk. I'll test this out tonight and see if it works right. Thanks!

We have our SPF protection setup on our DNS system and that's working fine. I even have it where all external emails have a giant red warning saying that it's external, but I still get users asking us if spoofed emails are legitimate. The spoofed email addresses nowadays looks something like [email protected]. Our emails are always just [email protected], or something similar. I know for a fact people are responding to the fake emails. Do you guys know of any way I can finagle a O365 rule to quarantine any email addresses that have our domain in the local-part?

@EddieJennings said in NGINX config issues:

I want to make sure I understand the problem. When you request http://my.testingtesting.com you receive a 301 redirect https://1.2.3.4 ?

...You know what. I think I have bigger problems. My machine off campus all of a sudden cannot ping the FQDN. When I remote into campus and ping the website I get the public IP address. Ugh, well I guess ignore this, maybe it'll straighten itself out once I fix this issue.