It is currently Sat Sep 21, 2019 9:09 am


All times are UTC




Post new topic Reply to topic  [ 5 posts ] 
Author Message
 Post subject: GNS3 1.0 beta 2 + VBOX - Could not connect to 192.168.1.56
PostPosted: Tue Sep 16, 2014 9:22 pm 
Offline

Joined: Tue Sep 16, 2014 9:08 pm
Posts: 2
While connecting to any local server in Preferences>GNS3 Server>Local Servers>Host Binding (127.0.0.1 or 192.168.56.1) there is always WinError 10061!

Any ideas?

Thank you in advance!




Attachments:
10061.png
10061.png [ 7.04 KiB | Viewed 2872 times ]
Top
 Profile  
 
 Post subject: Re: GNS3 1.0 beta 2 + VBOX - Could not connect to 192.168.1.
PostPosted: Wed Sep 17, 2014 3:52 am 
Offline

Joined: Tue Sep 16, 2014 9:08 pm
Posts: 2
The problem was solved by uninstalling GNS3 0.8.6 which existed alongside.


Top
 Profile  
 
 Post subject: Re: GNS3 1.0 beta 2 + VBOX - Could not connect to 192.168.1.
PostPosted: Wed Sep 17, 2014 8:56 am 
Offline

Joined: Sun Sep 16, 2012 9:55 pm
Posts: 541
Location: England
AnthonIvanov wrote:
The problem was solved by uninstalling GNS3 0.8.6 which existed alongside.


Note: Whilst this appears to have solved the issue, I'm not sure this is the cause. GNS3 0.8.6 and GNS v1 are completely different, so unless you're trying to run both at the same time there shouldn't be an issue

_________________
Daniel
Forum Moderator & Debian Package Maintainer for GNS3, Dynamips & VPCS.
Standalone DEB Packages are available from http://gns3.serverb.co.uk - To be updated!


Top
 Profile  
 
 Post subject: GNS3 1.0 beta 2 Unable to start the VM (failed at 20%)
PostPosted: Thu Sep 18, 2014 11:25 am 
Offline

Joined: Wed Jun 25, 2014 12:24 pm
Posts: 15
This is the output of the VM when I run my GNS3;


Server error [-3200] from 192.168.56.1:8000: VM7_1: Unable to start the VM (failed at 20%)

How do I solve this problem.


Top
 Profile  
 
 Post subject: Re: GNS3 1.0 beta 2 + VBOX - Could not connect to 192.168.1.
PostPosted: Thu Sep 25, 2014 6:16 pm 
Offline

Joined: Mon Jun 25, 2012 2:06 am
Posts: 10
I encountered this error as well. I noticed that my computers routing table did not have a route to 192.168.1.56. I turned off automatic private IP addresses on the virtual network adapter created by VBOX. This seemed to resolve the problem. I also noticed that the virtual adapter had the same IP address as the virtual box. So that was another issue I had as well.




Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 5 posts ] 

All times are UTC


Who is online

Users browsing this forum: No registered users and 3 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB® Forum Software © phpBB Group

phpBB SEO