Jump to content

ESET Endpoint blocking Dell iDRAC Remote Console


Go to solution Solved by Marcos,

Recommended Posts

Hello

I need to access some remote Dell iDRAC consoles (remote access consoles). The certificates are self-signed by the iDRAC.

I can access the iDRAC itself with no problem, it all works well, although I do get browser warnings about the site not being secure. However if I try to access the Virtual Console I get a few popups and then a connection closed message. Viewing the (invalid) certificate shows ISSUED TO as  the iDRAC name and ISSUED BY as ESET.

If I Disable "Enable SSL/TLS protocol filtering" under Web and Email is the ESET client, I can connect successfully.  In this case both ISSUED TO and ISSUED BY show the iDRAC name.

What might be the best way to resolve this, aside from completely disabling SSL protocol filtering? I am using 8.0.2028.0 on Win10.

Many thanks,

 

Jim

 

Link to post
Share on other sites
  • Administrators

Have you tried excluding the appropriate IP address from SSL filtering? You can also temporarily switch SSL filtering to interactive mode and select to ignore the certificate when asked.

Link to post
Share on other sites

Thanks Marcos. I couldn't find a setting to exclude from SSL filtering, only Protocol Filtering, which I guess has a wider scope than just SSL? Adding the IP address in there does indeed make the problem go away.

Would you envisage this being a short-term workaround or a long-term solution?

Many thanks

Jim

 

image.png.001e71faf42bd59662e02dffb25dd0e0.png

Link to post
Share on other sites
  • Administrators

The question is if it doesn't work for security reasons when the application refuses to communicate if the certificate is issued by an unexpected issuer or if there's an issue with filtering the SSL communication.

I'd recommend generating 2 sets of logs:

1,
- with SSL filtering enabled and no IP exclusion in place
- enable advanced network protection + protocol filtering logging under tools -> diagnostics
- reproduce the issue
- disable logging
- collect logs with ESET Log Collector

2,
- with SSL filtering disabled
- enable advanced network protection logging under tools -> diagnostics
- try to reproduce the issue (it should work now)
- disable logging
- collect logs with ESET Log Collector

When done, upload both archives here.

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...