[CSHARP-2977] Unable to connect to name server Created: 23/Feb/20  Updated: 06/May/20  Resolved: 06/May/20

Status: Closed
Project: C# Driver
Component/s: API, Connectivity
Affects Version/s: 2.9.3, 2.10.0-beta1, 2.10.0, 2.10.1, 2.10.2
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: John Nilson Assignee: Vincent Kam (Inactive)
Resolution: Done Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Windows 10. ASP.NET Core 3. C#


Attachments: Text File MongoDatabaseConnection.cs     File appsettings.Development.json     Text File databaseconnectionstring.txt     HTML File eventviewer deployed IIS     HTML File eventviewer localhost     HTML File localhost     PNG File screenshot-1.png    
Issue Links:
Related
is related to CSHARP-2968 Exception occurs when using mongodb+s... Closed

 Description   

https://github.com/jhnsartain3/Users-API

I included the errors I am getting and how to reproduce



 Comments   
Comment by Vincent Kam (Inactive) [ 06/May/20 ]

Hi jhnsartain3@gmail.com,

Thank you for your report. We tried to reproduce your issue using version 2.10.2 of the driver and were able to successfully connect to an Atlas cluster that uses a mongodb+srv connection string similar to the one you provided. Based off the logs you provided, I can also see that a MongoDB.Driver.MongoAuthenticationException is being thrown

MongoDB.Driver.MongoAuthenticationException: Unable to authenticate using sasl protocol mechanism SCRAM-SHA-1.
---> MongoDB.Driver.MongoCommandException: Command saslStart failed: Authentication failed.

Given the presence of the exception, I might recommend double checking the credentials in your connection string and also ensuring that the user has been added to the database with the correct role.

As your report does not appear to describe a bug specific to .NET/C# driver and the CSHARP project is for reporting bugs or feature suggestions for the driver, I think the MongoDB Community Forums may be a better place for your question. If you have more information that would indicate that there's a bug in the C#/.NET driver, we would be more than happy to investigate. 
 
Kind regards,
Vincent

Generated at Wed Feb 07 21:44:01 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.