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

Pass Through Authentication Failing through domain website

Jump to solution

Hi all!

So we are having an issue getting pass through credentials to work when access the domain website for our EOC platform. We can access via https://(servername), but not through https://website.name . We have recently gone through an in place upgrade (to the same server version and build) to fix some issues we were having with the server taking windows update. We are still using the same certificate that was issued before the in place upgrade. My research isn't coming up with a definitive answer, but does a new certificate need to be issued if the IP and server name remain the same? Or has anyone gone through something similar and I'm missing a key configuration after doing the in place upgrade?

0 Kudos
1 Solution

Found the issue:

Was trying to look at getting another SSL certificate issued to verify that was or was not the issue (Its not!) found that the Netlogon service was not started.

After starting Netlogon service and setting it to automatic start, I was having issues connecting to the site with https://(servername). Looked at my settings again, ran through SolarWinds Active Diagnostics for website health (a really useful tool if you haven't used it to check your website implementation yet), removed all the unnecessary site bindings I created during this troubleshooting process, ran IISRESET in PowerShell(admin), and started the website. Tried accessing https://website.name and it works!

I hope this small oversight is what fixes it for anyone else having this issue.

View solution in original post

6 Replies

Found the issue:

Was trying to look at getting another SSL certificate issued to verify that was or was not the issue (Its not!) found that the Netlogon service was not started.

After starting Netlogon service and setting it to automatic start, I was having issues connecting to the site with https://(servername). Looked at my settings again, ran through SolarWinds Active Diagnostics for website health (a really useful tool if you haven't used it to check your website implementation yet), removed all the unnecessary site bindings I created during this troubleshooting process, ran IISRESET in PowerShell(admin), and started the website. Tried accessing https://website.name and it works!

I hope this small oversight is what fixes it for anyone else having this issue.

View solution in original post

Thank you very much for sharing this valuable feedback @artemis.hyginus 

0 Kudos
Level 9

Encountering the same thing. Any resolve to this?

0 Kudos

I have an open ticket with SolarWinds customer service. Hopefully another member of the Thwack community can help, but if I find a solution from the technician working the issue, I'll be sure to share.

0 Kudos

@artemis.hyginus do you have a support case number you can share please?  

0 Kudos

Hey, @jblankjblank

Here is the ticket number: 00495727

0 Kudos