Describe the bug
GNS3 starts fine but the GNS VM indicator does not turn green.
GNS3 version and operating system (please complete the following information):
Windows 10 Pro Version 1909 (OS Build 18363.778)
Running GNS3 version 2.2.7 on Windows (64-bit) with Python 3.6.8 Qt 5.12.1 and PyQt 5.12.
Copyright (c) 2006-2020 GNS3 Technologies.
To Reproduce
Steps to reproduce the behavior:
Start GNS3. Wait for GNS3 VM to be fully started. Click on GNS3 menu to open an existing project.
Screenshots or videos
If applicable, add screenshots (e.g. of the topology and/or error message) or links to videos to help explain the problem. This will help us a lot to quickly find the bug and fix it.
Additional context
So far, the only fix is to close GNS3, thus closing VMware Workstation, doing a repair for VMWare Workstation (reset all VMware virtual nics to their default values) and running vmnet-manager.cmd.
GNS3 then works fine until I close it, restart my workstation and try to run it again.
BTW. a similar if not the same issue has been report on gns3.com under community/questions.
"Cannot connect to compute 'GNS3 VM (GNS3 VM)' with request POST /projects"
Please we need a fix for this, i have the same issue!! only fix i see is for me, uninstall and reinstall vmware!! this is so annoying!! im working on something now on gn3 and how on earth am i going to be able to do that every time i open gns3? uninstall and reinstall and over and over again!!cant keep doinig that forever!!
Two hours after posting this comment the GNS3 issue noted above is back. Sorry.....
Well, this may turn out to be a fluke but here goes. I no longer have the problem. But, will see if my good luck continues to tomorrow. Here's what I did.
Unfortunately I did two things not one.
Firstly, I ran the most recent Windows 10 update,
2020-4 Cumulative Update for Windows 10 version 1909 for X64-based Systems (KB4550945)
Reboot the Windows workstation.
Secondly, I did the following.
Start the VMware Workstation GNS3 VM.
Select the Upgrade - Upgrade the GNS3 VM option.
Select and run the v2.2.7 Release v2.2.7 option, just to see if perhaps it would fix something that was broken.
Shut down the GNS3 VM.
Start GNS3 application.
Continuing the saga and, likely, merely adding confusion.
Does not work:
Vmware Workstation 15.5.2
Vmware VIX 1.15.3.00000
Works....so far.
Vmware Workstation 15.5.1
Vmware VIX 1.15.3.00000
So you are using 15.5.1 and gns3 2.2.7?
On Thu, Apr 23, 2020, 5:15 PM jtorri notifications@github.com wrote:
Continuing the saga and, likely, merely adding confusion.
Does not work:
Vmware Workstation 15.5.2
Vmware VIX 1.15.3.00000Works....so far.
Vmware Workstation 15.5.1
Vmware VIX 1.15.3.00000—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/GNS3/gns3-gui/issues/2969#issuecomment-618718410, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/APJQFTS7CR6P4TZSIWFQMA3RODD2ZANCNFSM4ML4UY2Q
.
Yep. Uninstalled VMware Workstation 15.5.2, keeping the current configurations, rebooted, installed VMware Workstation 15.5.1, rebooted and ran GNS3 2.2.7. Rebooted my workstation several more times running GNS3 2.2.7 each time after reboot. Very limited testing, obviously, but it continues to work so far.
Sent from Mail for Windows 10
From: kb389
Sent: Thursday, April 23, 2020 7:17 PM
To: GNS3/gns3-gui
Cc: jtorri; Author
Subject: Re: [GNS3/gns3-gui] Cannot connect to compute 'GNS3 VM (GNS3-2.2.7)'with request POST /projects (#2969)
So you are using 15.5.1 and gns3 2.2.7?
On Thu, Apr 23, 2020, 5:15 PM jtorri notifications@github.com wrote:
Continuing the saga and, likely, merely adding confusion.
Does not work:
Vmware Workstation 15.5.2
Vmware VIX 1.15.3.00000Works....so far.
Vmware Workstation 15.5.1
Vmware VIX 1.15.3.00000—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/GNS3/gns3-gui/issues/2969#issuecomment-618718410, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/APJQFTS7CR6P4TZSIWFQMA3RODD2ZANCNFSM4ML4UY2Q
.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Hmm I have the exact same setup but it fails for me, at least did so in the
morning, let me try again now, I'm telling you, those gns3 freaks don't
know when to release an update, always buggy! I should have never ever ever
ever upgraded to 2.2.7! It was working perfectly fine before that!!!!!!!
On Thu, Apr 23, 2020, 5:30 PM jtorri notifications@github.com wrote:
Yep. Uninstalled VMware Workstation 15.5.2, keeping the current
configurations, rebooted, installed VMware Workstation 15.5.1, rebooted and
ran GNS3 2.2.7. Rebooted my workstation several more times running GNS3
2.2.7 each time after reboot. Very limited testing, obviously, but it
continues to work so far.Sent from Mail for Windows 10
From: kb389
Sent: Thursday, April 23, 2020 7:17 PM
To: GNS3/gns3-gui
Cc: jtorri; Author
Subject: Re: [GNS3/gns3-gui] Cannot connect to compute 'GNS3 VM
(GNS3-2.2.7)'with request POST /projects (#2969)So you are using 15.5.1 and gns3 2.2.7?
On Thu, Apr 23, 2020, 5:15 PM jtorri notifications@github.com wrote:
Continuing the saga and, likely, merely adding confusion.
Does not work:
Vmware Workstation 15.5.2
Vmware VIX 1.15.3.00000Works....so far.
Vmware Workstation 15.5.1
Vmware VIX 1.15.3.00000—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/GNS3/gns3-gui/issues/2969#issuecomment-618718410,
or
unsubscribe
<
https://github.com/notifications/unsubscribe-auth/APJQFTS7CR6P4TZSIWFQMA3RODD2ZANCNFSM4ML4UY2Q.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/GNS3/gns3-gui/issues/2969#issuecomment-618722656, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/APJQFTRJEJW6S4IQF5ZYADDRODFRXANCNFSM4ML4UY2Q
.
Ok it worked for me as well, strange, but it could be because I did not
reboot my laptop, maybe it will show an error again after a laptop reboot,
why don't you try it by rebooting your laptop or pc? I think it will fail
again of the laptop or pc is rebooted.
On Thu, Apr 23, 2020, 5:30 PM jtorri notifications@github.com wrote:
Yep. Uninstalled VMware Workstation 15.5.2, keeping the current
configurations, rebooted, installed VMware Workstation 15.5.1, rebooted and
ran GNS3 2.2.7. Rebooted my workstation several more times running GNS3
2.2.7 each time after reboot. Very limited testing, obviously, but it
continues to work so far.Sent from Mail for Windows 10
From: kb389
Sent: Thursday, April 23, 2020 7:17 PM
To: GNS3/gns3-gui
Cc: jtorri; Author
Subject: Re: [GNS3/gns3-gui] Cannot connect to compute 'GNS3 VM
(GNS3-2.2.7)'with request POST /projects (#2969)So you are using 15.5.1 and gns3 2.2.7?
On Thu, Apr 23, 2020, 5:15 PM jtorri notifications@github.com wrote:
Continuing the saga and, likely, merely adding confusion.
Does not work:
Vmware Workstation 15.5.2
Vmware VIX 1.15.3.00000Works....so far.
Vmware Workstation 15.5.1
Vmware VIX 1.15.3.00000—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/GNS3/gns3-gui/issues/2969#issuecomment-618718410,
or
unsubscribe
<
https://github.com/notifications/unsubscribe-auth/APJQFTS7CR6P4TZSIWFQMA3RODD2ZANCNFSM4ML4UY2Q.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/GNS3/gns3-gui/issues/2969#issuecomment-618722656, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/APJQFTRJEJW6S4IQF5ZYADDRODFRXANCNFSM4ML4UY2Q
.
For my 2 cents….I’m not altogether certain GNS3 2.2.7 is the primary source of the problems. For free software it has a lot of remarkable features. However, for stability and ease of install/update I suggest some form of Linux (at the moment I prefer Linux Mint 19.2) as the platform on which to run GNS3. The instructions for install are pretty clearly described on gns3.com. And it eliminates any challenges related to Microsoft/VMware incompatibility issues.
As I said, that’s merely my 2 cents.
Sent from Mail for Windows 10
From: kb389
Sent: Thursday, April 23, 2020 7:35 PM
To: GNS3/gns3-gui
Cc: jtorri; Author
Subject: Re: [GNS3/gns3-gui] Cannot connect to compute 'GNS3 VM (GNS3-2.2.7)'with request POST /projects (#2969)
Hmm I have the exact same setup but it fails for me, at least did so in the
morning, let me try again now, I'm telling you, those gns3 freaks don't
know when to release an update, always buggy! I should have never ever ever
ever upgraded to 2.2.7! It was working perfectly fine before that!!!!!!!
On Thu, Apr 23, 2020, 5:30 PM jtorri notifications@github.com wrote:
Yep. Uninstalled VMware Workstation 15.5.2, keeping the current
configurations, rebooted, installed VMware Workstation 15.5.1, rebooted and
ran GNS3 2.2.7. Rebooted my workstation several more times running GNS3
2.2.7 each time after reboot. Very limited testing, obviously, but it
continues to work so far.Sent from Mail for Windows 10
From: kb389
Sent: Thursday, April 23, 2020 7:17 PM
To: GNS3/gns3-gui
Cc: jtorri; Author
Subject: Re: [GNS3/gns3-gui] Cannot connect to compute 'GNS3 VM
(GNS3-2.2.7)'with request POST /projects (#2969)So you are using 15.5.1 and gns3 2.2.7?
On Thu, Apr 23, 2020, 5:15 PM jtorri notifications@github.com wrote:
Continuing the saga and, likely, merely adding confusion.
Does not work:
Vmware Workstation 15.5.2
Vmware VIX 1.15.3.00000Works....so far.
Vmware Workstation 15.5.1
Vmware VIX 1.15.3.00000—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/GNS3/gns3-gui/issues/2969#issuecomment-618718410,
or
unsubscribe
<
https://github.com/notifications/unsubscribe-auth/APJQFTS7CR6P4TZSIWFQMA3RODD2ZANCNFSM4ML4UY2Q.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/GNS3/gns3-gui/issues/2969#issuecomment-618722656, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/APJQFTRJEJW6S4IQF5ZYADDRODFRXANCNFSM4ML4UY2Q
.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Yup I also do think that the incremental updates that Microsoft releases
breaks gns3 a lot and then you have to wait for a fix , either way it's us
consumers suffering from it!
On Thu, Apr 23, 2020, 5:42 PM jtorri notifications@github.com wrote:
For my 2 cents….I’m not altogether certain GNS3 2.2.7 is the primary
source of the problems. For free software it has a lot of remarkable
features. However, for stability and ease of install/update I suggest some
form of Linux (at the moment I prefer Linux Mint 19.2) as the platform on
which to run GNS3. The instructions for install are pretty clearly
described on gns3.com. And it eliminates any challenges related to
Microsoft/VMware incompatibility issues.
As I said, that’s merely my 2 cents.Sent from Mail for Windows 10
From: kb389
Sent: Thursday, April 23, 2020 7:35 PM
To: GNS3/gns3-gui
Cc: jtorri; Author
Subject: Re: [GNS3/gns3-gui] Cannot connect to compute 'GNS3 VM
(GNS3-2.2.7)'with request POST /projects (#2969)Hmm I have the exact same setup but it fails for me, at least did so in the
morning, let me try again now, I'm telling you, those gns3 freaks don't
know when to release an update, always buggy! I should have never ever ever
ever upgraded to 2.2.7! It was working perfectly fine before that!!!!!!!On Thu, Apr 23, 2020, 5:30 PM jtorri notifications@github.com wrote:
Yep. Uninstalled VMware Workstation 15.5.2, keeping the current
configurations, rebooted, installed VMware Workstation 15.5.1, rebooted
and
ran GNS3 2.2.7. Rebooted my workstation several more times running GNS3
2.2.7 each time after reboot. Very limited testing, obviously, but it
continues to work so far.Sent from Mail for Windows 10
From: kb389
Sent: Thursday, April 23, 2020 7:17 PM
To: GNS3/gns3-gui
Cc: jtorri; Author
Subject: Re: [GNS3/gns3-gui] Cannot connect to compute 'GNS3 VM
(GNS3-2.2.7)'with request POST /projects (#2969)So you are using 15.5.1 and gns3 2.2.7?
On Thu, Apr 23, 2020, 5:15 PM jtorri notifications@github.com wrote:
Continuing the saga and, likely, merely adding confusion.
Does not work:
Vmware Workstation 15.5.2
Vmware VIX 1.15.3.00000Works....so far.
Vmware Workstation 15.5.1
Vmware VIX 1.15.3.00000—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/GNS3/gns3-gui/issues/2969#issuecomment-618718410,
or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/APJQFTS7CR6P4TZSIWFQMA3RODD2ZANCNFSM4ML4UY2Q
>.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/GNS3/gns3-gui/issues/2969#issuecomment-618722656,
or
unsubscribe
<
https://github.com/notifications/unsubscribe-auth/APJQFTRJEJW6S4IQF5ZYADDRODFRXANCNFSM4ML4UY2Q.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/GNS3/gns3-gui/issues/2969#issuecomment-618725937, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/APJQFTTAYVGDO5J24HOJU7TRODG6FANCNFSM4ML4UY2Q
.
Time to leave this issue to those who know what they are doing. The original issue has returned, not connecting when opening an existing project.
Yeah, I will be booting up my laptop soon and testing again , I'm sure I
will get the same problem as well.
On Fri, Apr 24, 2020, 4:21 AM jtorri notifications@github.com wrote:
Time to leave this issue to those who know what they are doing. The
original issue has returned, not connecting when opening an existing
project.—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/GNS3/gns3-gui/issues/2969#issuecomment-618929474, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/APJQFTRJOT2JHL7F4OE6FP3ROFR3FANCNFSM4ML4UY2Q
.
Yup as expected, booting up the laptop has brought back this issue, damn
I'm going crazy, all I can do I keep my laptop turned on for 12 hrs
straight in a day so that I don't have to keep uninstalling and
reinstalling VMware to make gns3 work for now, hopefully someone fixes this
although I have low hopes😪
On Thu, Apr 23, 2020, 5:15 PM jtorri notifications@github.com wrote:
Continuing the saga and, likely, merely adding confusion.
Does not work:
Vmware Workstation 15.5.2
Vmware VIX 1.15.3.00000Works....so far.
Vmware Workstation 15.5.1
Vmware VIX 1.15.3.00000—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/GNS3/gns3-gui/issues/2969#issuecomment-618718410, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/APJQFTS7CR6P4TZSIWFQMA3RODD2ZANCNFSM4ML4UY2Q
.
So there were a bunch of windows updates that were on queue, I installed
them all and everything is upto date and upon rebooting the laptop and
starting gns3 I'm able to load my project normally now, this is the first
time I've been able to load the project without any issues with this 2.2.7
version, maybe it's fixed who knows, since I've only tried once, will know
if it's actually fixed for good within the next few days.
On Thu, Apr 23, 2020, 5:15 PM jtorri notifications@github.com wrote:
Continuing the saga and, likely, merely adding confusion.
Does not work:
Vmware Workstation 15.5.2
Vmware VIX 1.15.3.00000Works....so far.
Vmware Workstation 15.5.1
Vmware VIX 1.15.3.00000—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/GNS3/gns3-gui/issues/2969#issuecomment-618718410, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/APJQFTS7CR6P4TZSIWFQMA3RODD2ZANCNFSM4ML4UY2Q
.
I think the issue is completely gone now, tried rebooting again and started
gns3 and it started without issues, so looks like those windows updates
fixed it.
On Thu, Apr 23, 2020, 5:15 PM jtorri notifications@github.com wrote:
Continuing the saga and, likely, merely adding confusion.
Does not work:
Vmware Workstation 15.5.2
Vmware VIX 1.15.3.00000Works....so far.
Vmware Workstation 15.5.1
Vmware VIX 1.15.3.00000—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/GNS3/gns3-gui/issues/2969#issuecomment-618718410, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/APJQFTS7CR6P4TZSIWFQMA3RODD2ZANCNFSM4ML4UY2Q
.
VMware has been very problematic for us as it seems they have bugs on their side + they broke vmrun in their latest Workstation 15.x version...
I recommend to manually start the GNS3 VM as described in https://gns3.com/community/discussion/gns3-with-workstation-player-15-
Thanks for the suggestion. I still believe the best solution is to run GNS3 on linux rather than windows.
However, tried changing GNS3 from local to remote server. When I restart GNS3 the changes are not there in Preferences and GNS3 once again fails to start the GNS3 VM.
Lol so was able to use gns3 without any issues for only 4 days and now the
issue is back (probably a new windows updates broke it again) haha.
On Tue, Apr 28, 2020, 6:56 AM jtorri notifications@github.com wrote:
Thanks for the suggestion. I still believe the best solution is to run
GNS3 on linux rather than windows.
However, tried changing GNS3 from local to remote server. When I restart
GNS3 the changes are not there in Preferences and GNS3 once again fails to
start the GNS3 VM.—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/GNS3/gns3-gui/issues/2969#issuecomment-620588955, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/APJQFTXBI5TDSFMPSXVTMG3RO3HARANCNFSM4ML4UY2Q
.
Please feel free to close this issue. For me, running GNS3 on linux is so much more efficient in terms of resources and effort required. Thanks!
@jtorri yep Linux is much better ;)
Same here:
Running GNS3 2.2.8 on Linux Mint 19.3 , Kernel: 4.15.0-99-generic, and VMware 15.5.2
GNS3 starts fine but the GNS VM indicator does not turn green.
GNS3 management console.
Running GNS3 version 2.2.8 on Linux (64-bit) with Python 3.6.9 Qt 5.11.2 and PyQt 5.11.3.
Copyright (c) 2006-2020 GNS3 Technologies.
Use Help -> GNS3 Doctor to detect common issues.
=> Cannot connect to compute 'GNS3 VM (GNS3 VM v2)' with request POST /projects
Yeah this seems to be a problem that everyone's facing now, hopefully some
fix comes out, cuz everytime I want to work on my lab I have to uninstall
and reinstall VMware to fix this issue and it's such a big big waste of
time and inconvenience 😪
On Sat, May 9, 2020, 1:52 PM RP-11 notifications@github.com wrote:
Same here:
Running GNS3 2.2.8 on Linux Mint 19.3 , Kernel: 4.15.0-99-generic, and
VMware 15.5.2GNS3 starts fine but the GNS VM indicator does not turn green.
GNS3 management console.
Running GNS3 version 2.2.8 on Linux (64-bit) with Python 3.6.9 Qt 5.11.2
and PyQt 5.11.3.
Copyright (c) 2006-2020 GNS3 Technologies.
Use Help -> GNS3 Doctor to detect common issues.=> Cannot connect to compute 'GNS3 VM (GNS3 VM v2)' with request POST
/projects—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/GNS3/gns3-gui/issues/2969#issuecomment-626227208, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/APJQFTVDP6QG6XUFGBZ2LZ3RQWYA7ANCNFSM4ML4UY2Q
.
The 2.2.5 version works fine... I learned to make snapshots before upgrading :)
If I roll back do you think my project will work on 2.2.5? Even I never had
any problems with .5 just upgraded blindly and now I'm paying the price,
although I highly doubt it would work that way 😥
On Sat, May 9, 2020, 6:32 PM RP-11 notifications@github.com wrote:
The 2.2.5 version works fine... I learned to make snapshots before
upgrading :)—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/GNS3/gns3-gui/issues/2969#issuecomment-626254362, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/APJQFTS2MZGI5M6IIZG25W3RQXYZVANCNFSM4ML4UY2Q
.
it should. just need to downgrade the desktop app to 2.2.5
But the gns3 vm should also be donated
Downgraded right?
On Sat, May 9, 2020, 6:41 PM RP-11 notifications@github.com wrote:
it should. just need to downgrade the desktop app to 2.2.5
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/GNS3/gns3-gui/issues/2969#issuecomment-626254977, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/APJQFTSFIIYWK7VTCV67DSDRQXZ2RANCNFSM4ML4UY2Q
.
I meant downgraded not donated lol a typo
On Sat, May 9, 2020, 6:41 PM RP-11 notifications@github.com wrote:
it should. just need to downgrade the desktop app to 2.2.5
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/GNS3/gns3-gui/issues/2969#issuecomment-626254977, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/APJQFTSFIIYWK7VTCV67DSDRQXZ2RANCNFSM4ML4UY2Q
.
correct
Do you have a link to the gns3 2.2.5 vm? For some reason whenever there is
a latest version you can only find that version in the gns3 website, cannot
find older versions and I'm scared to do it as well since my project is
about 170 gb or so😥
On Sat, May 9, 2020, 6:43 PM RP-11 notifications@github.com wrote:
correct
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/GNS3/gns3-gui/issues/2969#issuecomment-626255093, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/APJQFTUO6MJ76Z2ZPFTN2L3RQX2CJANCNFSM4ML4UY2Q
.
Hello thank you! So on this particular website if I just search for a
particular version of gns3 on the search bar I should get results right?
I'll just bookmark this site so it will be useful for me in the future, now
I must do some research on how to downgrade gns3 carefully.
On Sat, May 9, 2020, 6:51 PM RP-11 notifications@github.com wrote:
https://sourceforge.net/projects/gns-3/files/Releases/v2.2.5/
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/GNS3/gns3-gui/issues/2969#issuecomment-626255653, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/APJQFTTEY7F27WHMKKEPHPDRQX3AVANCNFSM4ML4UY2Q
.
I had same problem. I installed gns3 v2.2.5 and gns3vm v2.2.5 as well. My problem solved. Thank you!
I facing the Same Issue and i solved by Doing :
STEP1:
Start the VMware Workstation GNS3 VM.
Select the Upgrade - Upgrade the GNS3 VM option.
Select and run the v2.2.7 Release v2.2.7 option,
** try to ping gns3VM From cmd if unreachable do next:
STEP2:
Network Connections (on Windows)
VMware Network Adapter VMnet "adapter# the gns3VM working on"
Disable
enable
** now try again ping gns3VM From cmd
Turns out the latest release of Virtualbox does work with GNS3. In order to start with a "clean slate" I did uninstall Virtualbox, run a registry cleaner (i.e., CCleaner registry clean option), rebooted and then installed VB 6.1.6 It has remained stable for last couple of days.
However, I continue to believe the most efficient way to run GNS3 is on linux using either Virtualbox or VMware solely to run VM guest, e.g., tinycore, Ubuntu, or some version of Windows as participants in a topology....or use Docker for that purpose. The only issue so far is I am unable to set the parameters for either Superputty or Solarputty for them to allow multi-tabs. Putty works without issues.
GNS3 management console.
Running GNS3 version 2.2.8 on Windows (64-bit) with Python 3.6.8 Qt 5.12.1 and PyQt 5.12.
Windows 10 Pro 64 bit
Version 1909 (OS Build 18363.815)
Virtualbox Version 6.1.6 r137129 (Qt5.6.2)
Hi how do I know which adapter the gns3 vm is using?
On Wed, May 13, 2020, 2:32 PM Omaralturki notifications@github.com wrote:
I facing the Same Issue and i solved by Doing :
STEP1:
Start the VMware Workstation GNS3 VM.
Select the Upgrade - Upgrade the GNS3 VM option.
Select and run the v2.2.7 Release v2.2.7 option,** try to ping gns3VM From cmd if unreachable do next:
STEP2:
Network Connections (on Windows)
VMware Network Adapter VMnet "adapter# the gns3VM working on"
Disable
enable** now try again ping gns3VM From cmd
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/GNS3/gns3-gui/issues/2969#issuecomment-628230042, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/APJQFTWUZD6GV2IIYGLAVSLRRL7VVANCNFSM4ML4UY2Q
.
Ok so I followed this video and everything is working again, looks like
some of my settings got messed up so followed this video and set things up
correctly-
On Wed, May 13, 2020, 2:32 PM Omaralturki notifications@github.com wrote:
I facing the Same Issue and i solved by Doing :
STEP1:
Start the VMware Workstation GNS3 VM.
Select the Upgrade - Upgrade the GNS3 VM option.
Select and run the v2.2.7 Release v2.2.7 option,** try to ping gns3VM From cmd if unreachable do next:
STEP2:
Network Connections (on Windows)
VMware Network Adapter VMnet "adapter# the gns3VM working on"
Disable
enable** now try again ping gns3VM From cmd
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/GNS3/gns3-gui/issues/2969#issuecomment-628230042, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/APJQFTWUZD6GV2IIYGLAVSLRRL7VVANCNFSM4ML4UY2Q
.
Nothing but repairing VMware Workstation seems to work. But that is not a viable option every time you want to use a program.
Yup that's what I was doing everyday until like Tuesday or so but it seems
to be fixed now, as I followed that video which I shared in a previous
reply, try watching that video and see if you have everything set up
properly, maybe that could you it.
On Fri, May 15, 2020, 5:20 AM RobertGru notifications@github.com wrote:
Nothing but repairing VMware Workstation seems to work. But that is not a
viable option every time you want to use a program.—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/GNS3/gns3-gui/issues/2969#issuecomment-629180237, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/APJQFTT4PIZQVNCW3X3BFKDRRUQPLANCNFSM4ML4UY2Q
.
This issue is widely reported on the following threads. From what I can read in this thread, the current work-around is to downgrade to 2.2.5, is that correct? Thanks.
Issue present on:
GNS3 2.2.8
Windows 10 18363.836
VMware Workstation 15.5.2 15785246
https://gns3.com/community/discussion/cannot-connect-to-compute-gns3-8
https://gns3.com/community/discussion/problem-on-remote-server-esxi
https://gns3.com/community/discussion/gns3vm-workstation-pro-gns-vm-is
Yes that's true, although try watching the video that I shared in the
previous replies maybe that might help.
On Mon, May 18, 2020, 9:25 PM Trent notifications@github.com wrote:
This issue is widely reported on the following threads. From what I can
read in this thread, the current work-around is to downgrade to 2.2.5, is
that correct? Thanks.Issue present on:
GNS3 2.2.8
Windows 10 18363.836
VMware Workstation 15.5.2 15785246https://gns3.com/community/discussion/cannot-connect-to-compute-gns3-8
https://gns3.com/community/discussion/problem-on-remote-server-esxi
https://gns3.com/community/discussion/gns3vm-workstation-pro-gns-vm-is—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/GNS3/gns3-gui/issues/2969#issuecomment-630556047, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/APJQFTX4TFHMVT4ZC3XNVODRSH3ZZANCNFSM4ML4UY2Q
.
My GNS3 VM does have ip addresses assigned to interfaces eth0 and eth1, although I can't seem to ping either address from my host.
C:\Users\trent>ping 192.168.8.128
Pinging 192.168.8.128 with 32 bytes of data:
Request timed out.
Request timed out.
Ping statistics for 192.168.8.128:
Packets: Sent = 2, Received = 0, Lost = 2 (100% loss),
Control-C
^C
C:\Users\trent>ping 192.168.220.128
Pinging 192.168.220.128 with 32 bytes of data:
Request timed out.
Request timed out.
Ping statistics for 192.168.220.128:
Packets: Sent = 2, Received = 0, Lost = 2 (100% loss),
Control-C
^C
C:\Users\trent>

Yes then follow the video and your issue might get solved
On Mon, May 18, 2020, 9:50 PM Trent notifications@github.com wrote:
My GNS3 VM does have ip addresses assigned to interfaces eth0 and eth1,
although I can't seem to ping either address from my host.`C:\Users\trent>ping 192.168.8.128
Pinging 192.168.8.128 with 32 bytes of data:
Request timed out.
Request timed out.Ping statistics for 192.168.8.128:
Packets: Sent = 2, Received = 0, Lost = 2 (100% loss),
Control-C
^C
C:\Users\trent>ping 192.168.220.128Pinging 192.168.220.128 with 32 bytes of data:
Request timed out.
Request timed out.Ping statistics for 192.168.220.128:
Packets: Sent = 2, Received = 0, Lost = 2 (100% loss),
Control-C
^C
C:\Users\trent>`[image: image]
https://user-images.githubusercontent.com/6335629/82282503-f89ae680-9961-11ea-972b-c1419fa7e568.png—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/GNS3/gns3-gui/issues/2969#issuecomment-630562474, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/APJQFTWYXKXRCTHHOGNY5CTRSH6XXANCNFSM4ML4UY2Q
.
Confirmed a work-around posted by another user works for me. Disable and re-enable the host VMnet1 and VMnet8 adapters, and then reboot the gns3 server. It was reported that you may have to do this every time you restart your computer.
Ok that's great
On Tue, May 19, 2020, 7:52 AM Trent notifications@github.com wrote:
Confirmed a work-around posted by another user works for me. Disable and
re-enable the host VMnet1 and VMnet8 adapters, and then reboot the gns3
server. It was reported that you may have to do this every time you restart
your computer.—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/GNS3/gns3-gui/issues/2969#issuecomment-630833385, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/APJQFTTJEHSKKNRQIQ5CCEDRSKFK5ANCNFSM4ML4UY2Q
.
Hi how do I know which adapter the gns3 vm is using?
…
On Wed, May 13, 2020, 2:32 PM Omaralturki @.*> wrote: I facing the Same Issue and i solved by Doing : STEP1: Start the VMware Workstation GNS3 VM. Select the Upgrade - Upgrade the GNS3 VM option. Select and run the v2.2.7 Release v2.2.7 option, * try to ping gns3VM From cmd if unreachable do next: STEP2: Network Connections (on Windows) VMware Network Adapter VMnet "adapter# the gns3VM working on" Disable enable * now try again ping gns3VM From cmd — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#2969 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/APJQFTWUZD6GV2IIYGLAVSLRRL7VVANCNFSM4ML4UY2Q .
Usually VMware Network Adapter VMnet1
Another way
1- in gns3 VM screen you will Find "IP: --------------"
2- on VMware go to: Edit --> Virtual Network Editor
on Virtual Network Editor you will Find the Number and Subnet
The same issue facing in GNS3 v2.2.8 & GNS3 VM v2.2.8 with VM Ware Pro 15.5.1. Installing & uninstalling VM Ware provide a temporary solution but after 2-3 days, the same result. GNS3 VM not turning green in GNS3. It seems a big bug from the GNS side.
Using GNS3 & its VM version 2.2.5 but the probability of turning on VM is still not 100%.
I have fixed an issue regarding connecting to the GNS3 VM. Let's see how this turns out after we release version 2.2.9.
Alternatively, please try the following build to see if it works correctly: https://sourceforge.net/projects/gns-3/files/Nightly%20Builds/2020-06-01/master/GNS3-master.2020-06-01-all-in-one.exe/download
Windows 10 Version 1909 (OS Build 18363.836)
GNS3 management console.
Running GNS3 version 2.2.9dev2 on Windows (64-bit) with Python 3.6.8 Qt 5.12.1 and PyQt 5.12.
VMware Workstation 15.5.2 build-15785246
Same results as originally described. The GNS3 VM starts but within the GNS3 application there is no connectivity to the GNS3 VM.
Have you checked the port setting for the GNS3 VM is correct?

Also, starting gns3server.exe --local from the command line (cmd.exe) could help to see what's happening.
Yes, GNS3 VM preferences does show port set to 80.
Output from gns3server.exe --local
2020-06-02 05:30:16 INFO run.py:219 GNS3 server version 2.2.9dev2
2020-06-02 05:30:16 INFO run.py:221 Copyright (c) 2007-2020 GNS3 Technologies Inc.
2020-06-02 05:30:16 INFO run.py:224 Config file C:\Users\theuser\AppData\Roaming\GNS32.2\gns3_server.ini loaded
2020-06-02 05:30:16 WARNING run.py:230 Local mode is enabled. Beware, clients will have full control on your filesystem
2020-06-02 05:30:16 INFO run.py:237 HTTP authentication is enabled with username 'admin'
2020-06-02 05:30:16 INFO run.py:244 Running with Python 3.6.8 and has PID 13792
2020-06-02 05:30:16 INFO web_server.py:307 Starting server on localhost:3080
2020-06-02 05:30:16 INFO __init__.py:62 Load controller configuration file C:\Users\theuser\AppData\Roaming\GNS32.2\gns3_controller.ini
2020-06-02 05:30:16 INFO __init__.py:66 Controller is starting
2020-06-02 05:30:16 INFO compute.py:63 Create compute local
2020-06-02 05:30:16 INFO compute.py:360 Connecting to compute 'local'
2020-06-02 05:30:16 INFO web_log.py:233 ::1 [02/Jun/2020:09:30:16 +0000] "GET /v2/compute/capabilities HTTP/1.1" 200 525 "-" "Python/3.6 aiohttp/3.6.2"
2020-06-02 05:30:16 INFO __init__.py:313 Start the GNS3 VM
2020-06-02 05:30:16 INFO compute.py:63 Create compute vm
2020-06-02 05:30:16 INFO notification_handler.py:50 New client has connected to compute WebSocket
2020-06-02 05:30:16 INFO compute.py:430 Connected to compute WebSocket 'http://localhost:3080/v2/compute/notifications/ws'
2020-06-02 05:30:16 INFO __init__.py:572 Searching for VMware VMs in inventory file "C:\Users\theuser\AppData\Roaming\Vmware\Inventory.vmls"
2020-06-02 05:30:16 INFO __init__.py:390 Executing vmrun with command: "C:\Program Files (x86)\VMware\VMware Workstation\vmrun.exe" -T ws checkToolsState "C:\Virtualmachines\GNS3-2.2.8_20200601\GNS3-2.2.8-20200601.vmx"
2020-06-02 05:30:17 INFO __init__.py:390 Executing vmrun with command: "C:\Program Files (x86)\VMware\VMware Workstation\vmrun.exe" -T ws list
2020-06-02 05:30:17 INFO vmware_gns3_vm.py:151 Update GNS3 VM settings (CPU, RAM and Hardware Virtualization)
2020-06-02 05:30:17 INFO vmware_gns3_vm.py:87 GNS3 VM vCPU count set to 4 and RAM amount set to 12288
2020-06-02 05:30:17 INFO __init__.py:390 Executing vmrun with command: "C:\Program Files (x86)\VMware\VMware Workstation\vmrun.exe" -T ws start "C:\Virtualmachines\GNS3-2.2.8_20200601\GNS3-2.2.8-20200601.vmx"
2020-06-02 05:30:21 INFO vmware_gns3_vm.py:161 GNS3 VM has been started
2020-06-02 05:30:21 INFO vmware_gns3_vm.py:166 Waiting for GNS3 VM IP
2020-06-02 05:30:30 INFO vmware_gns3_vm.py:185 GNS3 VM IP address set to 192.168.41.128
2020-06-02 05:30:39 WARNING web_server.py:159 Server has got signal SIGINT, exiting...
2020-06-02 05:30:39 INFO web_server.py:114 Closing 1 websocket connections...
2020-06-02 05:30:39 INFO compute.py:456 Connection closed to compute WebSocket 'http://localhost:3080/v2/compute/notifications/ws'
2020-06-02 05:30:39 INFO notification_handler.py:59 Client has disconnected from compute WebSocket
2020-06-02 05:30:39 INFO __init__.py:121 Controller is stopping
2020-06-02 05:30:39 INFO __init__.py:403 Stop the GNS3 VM
2020-06-02 05:30:39 INFO __init__.py:390 Executing vmrun with command: "C:\Program Files (x86)\VMware\VMware Workstation\vmrun.exe" -T ws stop "C:\Virtualmachines\GNS3-2.2.8_20200601\GNS3-2.2.8-20200601.vmx" soft
2020-06-02 05:30:40 WARNING __init__.py:378 Could not check the VM is in the same subnet as the local server: Cannot connect to compute 'GNS3 VM (GNS3-2.2.8-20200601)' with request GET /network/interfaces
2020-06-02 05:30:41 INFO vmware_gns3_vm.py:213 GNS3 VM has been stopped
2020-06-02 05:30:16 INFO web_server.py:307 Starting server on localhost:3080
The local server is bound to localhost while the GNS3 VM server is running on 192.168.41.128. The local server should be bound to 192.168.41.1 or another address on the same subnet in the GNS3 preferences.
Please try and let me know if this solves the problem.
Bearing in mind the size of my ignorance compared to your understanding of the inner workings of GNS3 I'm a bit reluctant to say the following but here goes. I think we have a communication issue. Your latest suggestion did not work nor do I believe it could have. 192.168.41.0/24 is the host-only subnet for eth0 on my GNS3 VM. By definition, a host-only interface is not reachable by the local machine on which the VM is running.
What did work was my opening the network manager on VMware Workstation, clicking on Edit then Virtual Network Editor and finally clicking on Restore Defaults. This has solved connectivity problems for me in the past, so I took a shot.
GNS3 2.2.9 now starts and connects to the GNS3 VM.
GNS3 VM eth0: 192.168.145.128 eth1: 192.168.126.128 eth2: 10.1.1.118
GNS3 server: host bindings: localhost port: 3080
GNS3 VM port: 80
Is it possible a significant source of connectivity issues is related to negative interactions between VMware interface drivers and Windows 10 updates?
Curiously, the GNS3 VM information screen shows what appears to be a place to display a port value but no value is displayed.

As always thanks for a truly great learning tool! And free for goodness sake!
Bearing in mind the size of my ignorance compared to your understanding of the inner workings of GNS3 I'm a bit reluctant to say the following but here goes. I think we have a communication issue. Your latest suggestion did not work nor do I believe it could have. 192.168.41.0/24 is the host-only subnet for eth0 on my GNS3 VM. By definition, a host-only interface is not reachable by the local machine on which the VM is running.
No worries, I must have missed something because so many users have similar issues so I often mix up something ;)
However, the host-only interface should be reachable by the local machine but not from your network. Try to ping the GNS3 VM IP from the local machine.
Is it possible a significant source of connectivity issues is related to negative interactions between VMware interface drivers and Windows 10 updates?
Correct, there are issues communicating with VMware vmnet interfaces using Winpcap or Npcap and also with different version of Windows (Windows 10 will behave the same as Windows 7 or even with another revision of Windows 10).
Curiously, the GNS3 VM information screen shows what appears to be a place to display a port value but no value is displayed.
Thanks for catching this, I have fixed that problem. It should work if you upgrade the VM again.
As you suggested, the issue "Curiously, the GNS3 VM information screen shows what appears to be a place to display a port value but no value is displayed." is resolved by upgrading the GNS3 VM.
However, the connectivity issue returns as described is my previous post after rebooting my workstation. It was once again "fixed" by clicking on Restore Defaults in VMware Workstation virtual network editor also as described in my previous post. As I am sure you know this method of "solving" the problem is untenable in as much as topologies using VMs, e.g., TinyCore, Win7, etc., rely upon specific IPs assigned to specific VMware virtual interfaces.
As always, thanks!
GNS3 2.2.9 and the VMware workstation VM provided with the release of GNS3.
Windows 10 Version 1909 (OS Build 18363.900)
VMware® Workstation 15 Pro Version 15.5.6 build-16341506
The issue of problems with the bridge network bindings is mentioned in the release notes for this newest version of VMware Workstation. So, as I would guess as the GNS3 developers suspected all along, it appears the issue with connectivity in the GNS3 referenced originally in this bug report is either resolved or much less likely to occur by VMware addressing the issue. Might be best to wait and see what other are experiencing, my testing is not be extensive.
As always, thanks!
Thanks for the information! We will wait to hear about what others are experiencing :+1:
Tested v2.2.8 (GNS3 & its VM) for at least 15 days. VM is working fine. But note that there is no installation of either L2 device or MLS on that VM. As of now, v2.2.9 is available, I am moving on it. Let's see the issue resolved in this version or not. I will again start with routers only & if no issue arises (at least in 20 or 30 days), then I will install MLS on VM (will avoid L2 device this time).
Clearly I am a glutton for punishment in that I am once again posting on this issue. But....
Windows 10 Pro Version 1909 (OS Build 18636.900)
VMware Workstation Pro version 15.5.6 build-16341506
GNS3 versions 2.2.4 through 2.2.9 inclusive are running without connection or other issues. True even after several reboots of my desktop.
I installed win10pcap based on several online comments referring to issues with winpcap and updates of Windows 10. Also running npcap so I assume the install of npcap was done as suggested
on https://docs.gns3.com/11YYG4NQlPSl31YwvVvBS9RAsOLSYv0Ocy-uG2K8ytIY/index.html
I also spent sometime making sure I had the latest Windows nic drivers.
So, we'll see....
I have somehow managed to fix the issue with GNS3vm greyed out and issue with request/POST project on Vmware Fusion & GNS3 version 2.2.9
* I was using 2 network adapters, one was in bridged mode and 2nd was in NAT mode *
The key to fix was to select
"Configure - Edit server configuration (advanced users only)"
option and make note of the value.
For example, if the file has
Host IP = X.X.X.X
port =
go to GNS3 preferences and select the same IP and Port for the server.
Click Apply > Ok
Restart GNS3, and now the GNS3 should come up as GREEN.
For request POST /projects, try changing the port number to some unused port in both GNS3 pref and inside the config file of VM.
Restart GNS3.
I cannot guarantee the fix, but these steps help me fixed my issue.
Cheers
As for my part in this issue please see my latest comments to jnatschev on issue 2999 also related to connectivity to the GNS3 VM. In summary my best guess is my problems were related to VIX. My solution was to uninstall all VMware products on my workstation, clean up the registry, reboot and reinstall VMWare Workstation Pro 15.5.6 which reinstalled VIX. My host binding on the GNS3 application Server Preferences, Main Server, host binding is now for the same subnet as vmnet1 assigned to eth0 in the GNS3 VM and no longer experience connectivity issues to GNS3 VM.
I have somehow managed to fix the issue with GNS3vm greyed out and issue with request/POST project on Vmware Fusion & GNS3 version 2.2.9
* I was using 2 network adapters, one was in bridged mode and 2nd was in NAT mode *
The key to fix was to select
"Configure - Edit server configuration (advanced users only)"
option and make note of the value.For example, if the file has
Host IP = X.X.X.X
port =go to GNS3 preferences and select the same IP and Port for the server.
Click Apply > Ok
Restart GNS3, and now the GNS3 should come up as GREEN.
For request POST /projects, try changing the port number to some unused port in both GNS3 pref and inside the config file of VM.
Restart GNS3.I cannot guarantee the fix, but these steps help me fixed my issue.
Cheers
Hi Masagar,
This worked for me. Just changed the port from 80 to any unused port. Thanks much! :)
At the moment my issues connecting from the GNS3 app to the GNS3 VM are related to vmnet1 configured as eth0 in the GNS3 VM. Please note, that configuration has always worked since GNS3 versions 1.x and the problem is sporadic.
Assume the following settings on GNS3 VM: eth0 vmnet1 (host-only), eth1 vmnet8 (NAT), eth2 vmnet0 (bridged - not automatic).
eth0 set to DHCP in netplan configuration and vmnet1 is set to DHCP in VMware Workstation configuration with IP obtained of 192.168.56.128, for example. The IP of vmnet virtual NIC on my workstation is 192.168.56.1, for example.
From DOS prompt on my Windows 10 workstation I can ping both 192.168.56.1 and 192.168.56.128.....when all is working. When connectivity is not working I can ping 192.168.56.1 but cannot ping 192.168.56.128.
The only solution that works consistently is resetting defaults for virtual NICS in VMware Workstation, a clumsy solution at best. However, after a couple of workstation reboots the connectivity issue returns.
That's the symptoms. It's the cause I cannot determine.
I have version 2.2.9. I had this issue of the GNS3 VM server not connecting. I tried the following and it hasn't failed since.
1.) In VMware Workstation Pro Virtual Network Editor, I added VMnet2, host-only Subnet 10.0.0.0 255.255.255.0 (was default in GNS3 VM I downloaded)

2.) Made sure network settings correct in GNS3 VM Network config file (I kept DHCP off, since it's a server). Left DHCP enabled even though I'm using static IP.


3.) Shutdown GNS3 on local machine and VM.
4.) Restarted GNS3 on local machine, which turned on VM and it has connected consistently since then.
In your situation maybe try disabling DHCP in GNS3 VM settings, set static IP for GNS3 VM of 192.168.56.128/24 with default gateway 192.168.56.1. Make sure in VMware you have a VMnet adapter for the 192.168.56.0 /24 subnet, set to host-only.
Hope this helps.
Latest solution in this saga. After starting GNS3 and GNS3 VM not connecting, disabling/enabling vmnet1 works will cause the connection to turn green.
https://www.gns3.com/community/discussion/fix-to-gns3-vm-greyed-out-gns3-v
I am also getting the same error on my system when using GNS3, I am using Windows 10 machine VMWare 15 Workstation, and recently day before yesterday upgraded my GNS3 from 2.2.8 to GNS3 2.2.11 the latest version,
One major issue resolution for GNS3 most of the problems are every time you shutdown GNS3, just Disable and Enable all the virtual adapters on your system, it works most of the time but not every time.
But seriously some days GNS3 sucks 👎
Please see my comments from yesterday on issue #2999. I am no longer required to disable/enable vmnet 1 for connectivity to the GNS3 VM from the GNS3 application to complete. Thanks!
@jtorri Thanks for the feedback. I will close this then.
My solution: