[COMPASS-3801] Compass on Windows 10 fails to connect to replica set (except via IP address) Created: 05/Aug/19  Updated: 10/Jan/24  Resolved: 30/Mar/20

Status: Closed
Project: Compass
Component/s: Compass, Connectivity
Affects Version/s: 1.18.0
Fix Version/s: 1.21.0

Type: Bug Priority: Major - P3
Reporter: Brian Blevins Assignee: Lucas Hrabovsky (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Windows 10


Attachments: Text File Mongo_Compass_Issue.log    
Issue Links:
Related
is related to NODE-1747 Replica set causes MongoNetworkError ... Closed
is related to NODE-2143 getaddrinfo ENOTFOUND error on Window... Closed

 Description   

After upgrading the OS to Windows 10 from Windows 7, customer can no longer access a replica set that has short hostnames in the rs.config().

The nslookup command returns the correct IP addresses for the replica set members using the short hostnames.

Compass 1.19.0-beta.1 reports MongoNetworkError: getaddrinfo ENOTFOUND when attempting to connect using the short hostname. A direct connection to the primary using its IP address (no Replica Set Name) succeeds.



 Comments   
Comment by Massimiliano Marcon [ 13/Aug/19 ]

As this seems to be a driver bug, I am going to close this ticket. Once it's fixed the driver and we'll bump the version we use in Compass, the issue will disappear.

For now, the workaround is to remove the replica set name.

Generated at Wed Feb 07 22:34:16 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.