I received an urgent ticket about a week ago. One of our clients was complaining that a printer of theirs was not sending email to any of the recipients after scanning.
Our client uses O365 which is managed by us. The printer sends email through a connector we have setup by using the onsite Gateway IP.
A quick look into the logs showed a mysterious Error #806. After some google-fu I was able to find Canon's error code listing that stated the printer was using a bad address?
Uh what???
I double and triple checked the address book and yes, they were completely fine.
Okay so what now? It has to be a DNS problem right? Nope. I checked the printer DNS setup and saw it was using google's own DNS server. I even went as far as changed the DNS settings to our company's own DNS servers it was still a no go.
I tried adding the Gateway IP to the clients allowed IP-list in O365, still a no go.
I was getting desperate. It had been three days at this point and I was not able to keep working on this same case for long periods at a time, plus the client was getting antsy...
| An accurate imagery of an Sysadmin getting swamped by clients tickets |
I finally resulted in asking help from my colleagues from the company chat but didn't receive any concrete advice until two of y colleagues came up with a really far fetched idea....
We remoted to a computer located inside the domain and launched putty.exe. We then opened a telnet session with the O365 connector setup and finally tried to send a test message when we received the following error:
"550 5.7.1 Service unavailable, Client host [REDACTED] blocked using Spamhaus. To request removal from this list see http://www.spamhaus.org/lookup.lasso (REDACTED) [DB3EUR04FT053.eop-eur04.prod.protection.outlook.com]"
"550 5.7.1 Service unavailable, Client host [REDACTED] blocked using Spamhaus. To request removal from this list see http://www.spamhaus.org/lookup.lasso (REDACTED) [DB3EUR04FT053.eop-eur04.prod.protection.outlook.com]"
Huh that is most certainly strange.
We followed the link and lo and behold! Our clients gateway-ip was blocked. It would seem that our customer had been sending emails to outside of their designated domain. Controllers are not meant for this kind of use and this resulted in the ip of our client's firewall getting banned.
We promptly removed the ban and after a few hours everything worked like a charm again.
| And I would have gotten away with it too, if it weren't for you meddling kids... |
| Next time: The gang solves the mystery of a spooky Cryptolocker! |
