You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description:
The pre-requisites for the GNS3 VM server to be running have been checked and I've re-installed multiple times but the issue still keeps happening.
After the GNS3VM settings are done and the VM is running successfully, the server status fails to turn green. The VMware adapters were checked and they are of 1) Host-only and 2) NAT types
The GNS3 versions of client and VM match as 2.2.45
The GNS3 Doctor has all check marks as OK
GNS3 version and operating system (please complete the following information):
OS: Windows 10
GNS3 version - 2.2.45
Any use of the GNS3 VM or remote server - GNS3VM with VMware Workstation Pro 17
To Reproduce
Steps to reproduce the behavior:
Complete the GNS3 setup and select GNS3 VM to be used
Make sure that the VMware is ready with a GNS3 VM and it is not running yet
Select GNS3VM from the Setup Wizard and let the GNS3VM be started
Notice that localhost server is detected green and running
But the GNS3VM server is not green
Please find the screenshots of the configurations done and let me know if something is amiss.
on version 2.2.45
The text was updated successfully, but these errors were encountered:
Description:
The pre-requisites for the GNS3 VM server to be running have been checked and I've re-installed multiple times but the issue still keeps happening.
After the GNS3VM settings are done and the VM is running successfully, the server status fails to turn green. The VMware adapters were checked and they are of 1) Host-only and 2) NAT types
The GNS3 versions of client and VM match as 2.2.45
The GNS3 Doctor has all check marks as OK
GNS3 version and operating system (please complete the following information):
To Reproduce
Steps to reproduce the behavior:
Please find the screenshots of the configurations done and let me know if something is amiss.
on version 2.2.45
The text was updated successfully, but these errors were encountered: