Create a Post
cancel
Showing results for 
Search instead for 
Did you mean: 
Tom_Cripps
Advisor

Checkpoint R80.10 Management Failing to Auth to Microsoft Exchange

Hi all,

We're looking into getting reports sent through email through SmartEvent. We're just having failed auth's on Exchange when we initiate a connection to send the email. Before I open a TAC case anyone seen this kind of behaviour? I've checked routing to the Mail Server, that's all fine, it's as is the MD5 hash isn't correct from what we can see in the logs?

Any help is appreciated guys! Smiley Happy

9 Replies
Vladimir
Champion
Champion

Have you tried running smtp commands from the SmartEvent serer using same credentials?

0 Kudos
Tom_Cripps
Advisor

Hi Vladimir, 

I'm not 100% sure what commands you could from the SmartEvent server? I wasn't aware there was any?

0 Kudos
Vladimir
Champion
Champion

Just ssh into SmartEvent server and attempt to telnet into your Exchange on port 25 using its name.

Use commands described here to compose and send a test message:

How to Test SMTP AUTH using Telnet [Wiki] | NDCHost 

FYI: do Not use backspace while typing SMTP commands, it'll nullify them. If you've made a mistake, end the telnet session and retry again from the beginning.

0 Kudos
Tom_Cripps
Advisor

Just had it connect successfully with CLI using that method Vladimir, I've now tried using the Base64 encoded phrases as my credentials on the GUI to see if that works. Are you aware of any difference between CLI and the GUI in how it presents the username and password to the mail server?

0 Kudos
Vladimir
Champion
Champion

Nope, sorry, that would be a question for TAC.

But at least you have the confirmation that there is nothing wrong with communication and authentication between your SmartEvent and Exchange, so this will help them to troubleshoot.

Include the results of your test in SR.

0 Kudos
Tom_Cripps
Advisor

Just got them from my Exchange Administrator, my presumption is that how it presents itself to the mail server through the GUI is different compared to the CLI with my results.

Tom_Cripps
Advisor

So, we've ran some Wireshark Traces and it looks like doing it through the CLI compared to the GUI encodes the username and password differently? 

 

Anyone else seen this behaviour?

PhoneBoy
Admin
Admin

Shot in the dark, but may want to review your password to see if it has characters not on this list:

List of allowed ASCII characters for passwords on Gaia OS 

May need to involve the TAC also.

0 Kudos
Tom_Cripps
Advisor

Hi Dameon,

Just checked and the characters of our password are all in the ASCII  table so will look to get in touch with our support contact unless you have any other ideas to try?

0 Kudos

Leaderboard

Epsum factorial non deposit quid pro quo hic escorol.

Upcoming Events

    CheckMates Events