Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

InstanceConnection Test Returns Error for AuthScheme Against Local Instances #601

Open
kylejdoyle opened this Issue Feb 14, 2019 · 5 comments

Comments

Projects
None yet
2 participants
@kylejdoyle
Copy link

kylejdoyle commented Feb 14, 2019

Bug Report

Steps to Reproduce

Run the InstanceConnect Test against a local instance of SQL Server.

Description of Bug

The auth scheme step will always fails if the instances being checked includes a local instance. Perhaps it would be better to first check if the instance being checked is local to the server and if it is always accept a result of NTLM.

@SQLDBAWithABeard

This comment has been minimized.

Copy link
Collaborator

SQLDBAWithABeard commented Feb 15, 2019

You can use skip.connection.auth to skip the authentication check but are you asking for the check to specifically test for local instance first?

@kylejdoyle

This comment has been minimized.

Copy link
Author

kylejdoyle commented Feb 15, 2019

Yes, there are a couple ways to handle this as it is now. However, since this is something that is always true, connecting to local instance is always NTLM, I was thinking perhaps it should be built into the check versus working around it every time.

@SQLDBAWithABeard

This comment has been minimized.

Copy link
Collaborator

SQLDBAWithABeard commented Feb 18, 2019

I have coded a fix for the next release

@kylejdoyle

This comment has been minimized.

Copy link
Author

kylejdoyle commented Feb 19, 2019

This should work, but I was just testing and it looks like there is a bug in Test-DbaConnection which shows the NetBIOSName incorrectly as the FQDN. I changed the IF condition to $Connection.ComputerName -eq $ENV:COMPUTERNAME and it works beautifully.

@SQLDBAWithABeard

This comment has been minimized.

Copy link
Collaborator

SQLDBAWithABeard commented Feb 19, 2019

ah grrr, didnt get that in my lab, I ummed and ahed as to which one to use - I'll change it. Thanks for testing :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.