Snapshots and export portable project failing with "duplicate name exists on network"

[eantowne]

Description: When attempting to either create a snapshot or export as portable project, after some time (not consistently the same point) the process fails with the below error(s). When running the snapshot or export without the Docker container, snapshot and export work fine.

Could not create snapshot file 'C:\Users\eanto\GNS3\projects\untitled2\snapshots\snapshot_test_2_220421_145753.gns3project': Cannot connect to host 192.168.1.204:3080 ssl:default [You were not connected because a duplicate name exists on the network. If joining a domain, go to System in Control Panel to change the computer name and try again. If joining a workgroup, choose another workgroup name]

ExportProjectWorker thread stopping with an error: Cannot export project: Cannot connect to host 192.168.1.204:3080 ssl:default [You were not connected because a duplicate name exists on the network. If joining a domain, go to System in Control Panel to change the computer name and try again. If joining a workgroup, choose another workgroup name]
Cannot export project: Cannot connect to host 192.168.1.204:3080 ssl:default [You were not connected because a duplicate name exists on the network. If joining a domain, go to System in Control Panel to change the computer name and try again. If joining a workgroup, choose another workgroup name]

GNS3 version and operating system (please complete the following information):

• OS: GNS3 Client: Windows 10 20H2(Controller), GNS3 Servers: 2 each POP-OS 20.10 (Ubuntu) (Compute)
• GNS3 version: 2.2.20
• 2 bare metal GNS3 Server instances as referenced above

Additional context Project consists of: 1 Cloud node running on Windows 10 (GNS3 Client) 1 Network Automation Docker container running on 1 bare metal server 1 VPCS running on each bare metal server 1 built-in L2 switch running on one of the bare metal servers

snapshot_export_bug_debug_info.zip

[eantowne]

Additionally, there are no duplicate IP's on the network involved. Ping, a constantly open SSH to each server, plus validation via network devices was conducted.