OpenText Socks Client V14 - Vagrant 1.8.5, Windows 7, Virtual Box 5.1.2 - Caused Default Vagrant Box (hashicorp/precise64) to not allow SSH (thereby fail vagrant up) - Error Found in Virtual Box Log

[Dan Hiebert]

Since I spent a few days debugging this one...I thought  I would share :) 

Work Around:

Remove OpenText Socks Client V14 (for now) 

Error: 

INFO interface: Machine: error-exit ["Vagrant::Errors::VMBootTimeout", "Timed out while waiting for the machine to boot. This means that\nVagrant was unable to communicate with the guest machine within\nthe configured (\"config.vm.boot_timeout\" value) time period.\n\nIf you look above, you should be able to see the error(s) that\nVagrant had when attempting to connect to the machine. These errors\nare usually good hints as to what may be wrong.\n\nIf you're using a custom box, make sure that networking is properly\nworking and you're able to connect to the machine. It is a common\nproblem that networking isn't setup properly in these boxes.\nVerify that authentication configurations are also setup properly,\nas well.\n\nIf the box appears to be booting properly, you may want to increase\nthe timeout (\"config.vm.boot_timeout\") value."]

Problem Description:

Installed Virtual Box 5.1.2 and Vagrant 1.8.5 on Windows 7, on hashicorp/precise64 ... vagrant up would never get past replacing insecure key and eventually time-out.   Seperate SSH client direct to precise64 would fail with connection refused.  

Error In Virtual Box Log:

00:00:11.628421 supR3HardenedErrorV: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Program Files\Open Text\SOCKS Client\HumSOCKS.dll' (C:\Program Files\Open Text\SOCKS Client\HumSOCKS.dll): rcNt=0xc0000190

I think there was SSH error in virtual box log.

I think my problem is solved now (socks client not needed presently) ... but since a weird anomaly I thought I would share. 

 

[Dan Hiebert]

Found a Fix - no need to uninstall OpenText Socks 

It seems the Cached Driver needs to be cleared, so new one can be re-loaded 

Windows Command Prompt 

 Start , type cmd, right click and select "Run as Administrator"

Some commands that will reinitialize various network states:

Reset WINSOCK entries to installation defaults : netsh winsock reset catalog
Reset TCP/IP stack to installation defaults : netsh int ip reset reset.log
Flush DNS resolver cache : ipconfig /flushdns
Renew DNS client registration and refresh DHCP leases : ipconfig /registerdns
Flush routing table : route /f

This worked for me now ... so better work-around then uninstalling the OpenText Socks client. 

[Dan Hiebert]

So ... actually, now I am not able to access the VPN / Socks Environments ... I wonder had I only cleared the cache ... but now environments are completely not accessible, with socks client. 

[Fazal Feroze]

simply uncheck the opentext from  windows startup  (i.e options run dashboard from startup)..   this will solve the vagrant issue

[Fazal Feroze]

simply uncheck the opentext from  windows startup  (i.e options run dashboard from startup)..   this will solve the vagrant issue