Hello, I don't know for sure. But if you are using powershell then that may explain.
Powershell will inherit proxy details from IE settings, so if you have a proxy setting that say all traffic for all ports should go to this proxy, then that may explain the issue. glad you got past that! Alvaro. On Sat, Feb 20, 2016 at 9:32 AM, 'Adam Turner' via Vagrant < [email protected]> wrote: > Hi Alvaro, > > I tried what you suggested and just got "connection refused". I may have > now fixed my problem although I don't really understand how! > > I was googling how to enable ssh in windows 10 and came across this post: > > > https://social.technet.microsoft.com/Forums/en-US/0a3f62e4-fe5e-4926-a277-99588258bf62/windows-10-ssh-tunnel-with-putty?forum=win10itprogeneral > > It includes the following instructions: > > 1. Press the *+ R* keys to open the Run dialog. > 2. Type *inetcpl.cpl*, and click/tap on *OK*. > > 3. Click on Connections tab. > > 4. Click on LAN settings button on the bottom. A LAN Settings Windows will > open. > > 5. un-check "Automatically detect settings" and check on "Use a proxy > server for your LAN..." > > 6. Click on "Advanced" button. A Proxy Settings window will open. > > 7. ONLY FILL the socks information, for example... Socks: 127.0.0.1 and > port 1080 (leave everything else blank) > > 8. Uncheck "Use the same proxy server for all protocols." Click OK. Step 7 > was only the thing that changed in my previous attempts. > > > So I followed the above and could ssh into my VM but lost my connection to > the web. So I re-ticked "automatically detect settings" and unticked "Use > a proxy server for your LAN..." and now both ssh and the web seem to work. > > > Thanks for your help, > > > Adam > > On Friday, February 19, 2016 at 1:03:57 PM UTC, Alvaro Miranda Aguilera > wrote: >> >> Hello Adam, >> >> If you do vagrant up >> >> then do vagrant ssh-config it should tell the port forwarded >> >> Then using the web browser you can try to reach that port. ie >> >> https://127.0.0.1:2222 >> >> it should return protocol-error since its ssh and not https, but will >> help to see the port. >> >> Other test will be use putty or ssh command from your OS and see if you >> get a prompt. >> >> Alvaro. >> >> >> On Sat, Feb 20, 2016 at 1:33 AM, 'Adam Turner' via Vagrant < >> [email protected]> wrote: >> >>> Hello again, >>> >>> a) I can stop and start the virtual machine in virtualbox without any >>> apparent problems. >>> >>> b) I found this suggestion of trying precise32 on other forums, so that >>> is what I was trying in my first post but it still has the same problem. >>> >>> This is what made me wonder if it is a problem with the ssh itself. >>> Possibly a problem with the port forwarding but disabling firewall and >>> antivirus does not seem to help. Are there any other programs and or >>> settings that may be causing the ssh to fail? Or diagnostics I could use to >>> check whether the port forwarding is working? >>> >>> Thanks. >>> >>> -- >>> This mailing list is governed under the HashiCorp Community Guidelines - >>> https://www.hashicorp.com/community-guidelines.html. Behavior in >>> violation of those guidelines may result in your removal from this mailing >>> list. >>> >>> GitHub Issues: https://github.com/mitchellh/vagrant/issues >>> IRC: #vagrant on Freenode >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "Vagrant" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/vagrant-up/b9b064e2-a957-46ba-a1c3-f905c02e18b6%40googlegroups.com >>> . >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- > This mailing list is governed under the HashiCorp Community Guidelines - > https://www.hashicorp.com/community-guidelines.html. Behavior in > violation of those guidelines may result in your removal from this mailing > list. > > GitHub Issues: https://github.com/mitchellh/vagrant/issues > IRC: #vagrant on Freenode > --- > You received this message because you are subscribed to the Google Groups > "Vagrant" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/vagrant-up/c9e604b0-b933-43f8-a467-137bcc2ce53b%40googlegroups.com > <https://groups.google.com/d/msgid/vagrant-up/c9e604b0-b933-43f8-a467-137bcc2ce53b%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/vagrant/issues IRC: #vagrant on Freenode --- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/CAHqq0ezM%3DZgWgeWW0CGC5ML-DxmXq4%2BQOGs7Sq2%2BK2mbNqw-6Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
