CODEWITHSUNDEEP
windowsubuntuvagrantvirtual-machinevirtualbox
Arijoon
Arijoon

Reputation: 2310

Vagrant cannot communicate to guest

I've initialized a standard vagrant (no additional config just default) with ubuntu/trusty64 box. Vagrant freezes on default: SSH auth method: private key step. I thought it was a ssh problem and tried using username password and etc.

Eventually I found out that the ports are not being forwarded properly. By default port 2222 on host is forwarded to 22 on the guest machine. I can use virtualbox gui to login to the machine and see that the guest is indeed listening on port 22:

enter image description here

However the host does not have the port 2222 open. If I run netstat -na |grep 2222 on my host machine I get no result (windows 7 host with cygwin).

Additionally if I do telnet localhost 2222 I get Could not open connection to the host, on port 2222: Connect failed which indicates the port is not open

EXTRA: I have been looking for solution for over 16 hours now but no luck. Tried many different solutions and even managed to ssh into the machine by using public bridged network and static ips however the vagrant-ssh didn't work in that case and refused to map the default network drives. My conclusion is that vagrant cannot communicate with the guest machine at all once it's booted up.

EDIT Also I get surprising result when I run nmap scan on port 2222

enter image description here enter image description here

I get both of those result. If I keep running the scan, it'll return either of them randomly

Upvotes: 0

Views: 830

Answers (1)

Arijoon
Arijoon

Reputation: 2310

The issue was with Virtualbox and not vagrant. Virtual box only allows signed dll's into the guest system (check virtualbox log files to find such issues). I had Killer N wireless card with BFLLR.dll. That file is not signed (probably Bigfoot Networks is too lazy to sign their own libraries, last time I'm buying anything from them).

Removing that file fixes the issue but then you also need the driver. That library is attached to the management software of the wireless card. Remove the management software and reinstall the driver only. That should fix this issue.

I didn't look into this but there might also be a way to sign the dll and add your key to the local trusted ones (highly doubt it's easy but might be something to explore)

Upvotes: 1

Related Questions