We couldn't authenticate with the credentials provided. Please try again

Question

Post reply

We couldn't authenticate with the credentials provided. Please try again

mybne

SSC Enthusiast

Points: 189
More actions
July 24, 2022 at 2:32 am
Go to Answer
#4067383

I am new to SQL area, it might be very simple, but googling did not help so far. Your help much appreciated.
I am trying to connect the database to see the live data of a particular table via a program. First, I want to test via excel database connection to verify username and permissions are set correctly. So far, I am not succeeded. (Please note, I can connect using the sa account or windows authentication with full permissions, which we don't want for known reasons). Looking at the below screenshot and details, could you tell me what I am missing, please?

Ant-Green

SSC Guru

Points: 113499
More actions
July 25, 2022 at 10:08 pm
Answer
#4068115

You will need to set a static port and open that in the firewall instead, along with UDP 1434
This should help with that.
https://docs.microsoft.com/en-us/sql/database-engine/configure-windows/configure-a-server-to-listen-on-a-specific-tcp-port?view=sql-server-ver16

Viewing 8 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic. Login to reply

Site Owners SSC Guru Points: 80330 More actions · Answer 1

Thanks for posting your issue and hopefully someone will answer soon.

This is an automated bump to increase visibility of your question.

Ant-Green SSC Guru Points: 113499 More actions · Answer 2

In Excel, don’t use windows credentials, switch it to use database credentials instead so on the left hand side. Windows or database or Microsoft account. It needs to be database.

Michael L John One Orange Chip Points: 27054 More actions · Answer 3

It has nothing to do with the credentials. Your local security policy is likely set to not allow impersonation.

Michael L John
If you assassinate a DBA, would you pull a trigger?
To properly post on a forum:
http://www.sqlservercentral.com/articles/61537/

mybne SSC Enthusiast Points: 189 More actions · Answer 4

Thanks, gentlemen. Ant-Green was right. Via localhost, I can connect but not from other PCs this time. I receive the below error. Firewall is off for now.

Details: "Microsoft SQL: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)"

This reply was modified 2 years, 3 months ago by mybne.
This reply was modified 2 years, 3 months ago by mybne.

globaltailor Newbie Points: 1 More actions · Answer 5

globaltailor

Newbie

Points: 1

July 26, 2022 at 7:04 am

#4068235

I have the same problem with you.

mybne SSC Enthusiast Points: 189 More actions · Answer 6

Ant-Green wrote:

You will need to set a static port and open that in the firewall instead, along with UDP 1434

This should help with that.

https://docs.microsoft.com/en-us/sql/database-engine/configure-windows/configure-a-server-to-listen-on-a-specific-tcp-port?view=sql-server-ver16%5B/quote%5D

Thank you, sir, spot on. All is good now.

This reply was modified 2 years, 3 months ago by mybne.