title: ssh_exchange_identification read connection reset by peer - Homestead Laravel
body: <p>I'm trying to connect to Homestead using the vagrant ssh command but I'm getting the below error message. I'm using Windows 7. How do I fix this issue?</p>
  
  <p><strong>ssh_exchange_identification read connection reset by peer</strong></p>
  
  <pre><code>Bringing machine 'default' up with 'virtualbox' provider...
  ==&gt; default: Importing base box 'centos-64-x64-vbox4210'...
  ==&gt; default: Matching MAC address for NAT networking...
  ==&gt; default: Setting the name of the VM: rafael_default_1396403974194_51967
  ==&gt; default: Clearing any previously set forwarded ports...
  ==&gt; default: Clearing any previously set network interfaces...
  ==&gt; default: Preparing network interfaces based on configuration...
  default: Adapter 1: nat
  ==&gt; default: Forwarding ports...
  default: 22 =&gt; 2222 (adapter 1)
  ==&gt; default: Booting VM...
  ==&gt; default: Waiting for machine to boot. This may take a few minutes...
  default: SSH address: 127.0.0.1:2222
  default: SSH username: vagrant
  default: SSH auth method: private key
  default: Error: Connection timeout. Retrying...
  default: Error: Connection timeout. Retrying...
  default: Error: Connection timeout. Retrying...
  default: Error: Connection timeout. Retrying...
  default: Error: Connection timeout. Retrying...
  Timed out while waiting for the machine to boot. This means that
  Vagrant was unable to communicate with the guest machine within
  the configured ("config.vm.boot_timeout" value) time period.
  
  If you look above, you should be able to see the error(s) that
  Vagrant had when attempting to connect to the machine. These errors
  are usually good hints as to what may be wrong.
  
  If you're using a custom box, make sure that networking is properly
  working and you're able to connect to the machine. It is a common
  problem that networking isn't setup properly in these boxes.
  Verify that authentication configurations are also setup properly,
  as well.
  
  If the box appears to be booting properly, you may want to increase
  the timeout ("config.vm.boot_timeout") value.
  </code></pre>