One thing you can do: While the VM is running, you can play around with
port forwarding, live, from the Network configuration section of the
VirtualBox GUI (the first interface--the NAT one: Advanced > Port
Forwarding). That way, you'll know if you're dealing with a Vagrant or
VirtualBox issue.

On Wed, May 31, 2017 at 4:33 PM, French Fry <[email protected]> wrote:

> Running Vagrant 1.95 with VirtualBox Version 5.1.22 r115126 (Qt5.6.2).
> Box is bento/ubuntu-16.04. Host is Windows 8.
>
> ssh is working so no problem there.  What I can't do is either telnet or
> connect through host browser. Here is the relevant section of the
> Vagrantfile
>
> config.vm.network "forwarded_port", guest: 1125, host: 4567, protocol:
> "tcp", auto_correct: true
>   config.vm.network "forwarded_port", guest: 1125, host: 4567, protocol:
> "udp", auto_correct: true
>
> I added the protocol and auto_correct options recently but they haven't
> changed anything.
> Also enabled Vagrant logging and am not seeing any issues regarding the
> ports.   Running
> sudo netstat -lptn and other options shows the ports of ssh and my
> postgresql listening, but nothing for the forwarded ports in the config
> file.
>
> I was able to netcat the port,  that worked for telnet.  No firewall
> running on Ubuntu (ufw status - inactive) and iptables is basically empty /
> no rules defined.  Not that it would matter with ufw off.
>
> I've also done multiple tests with Windows firewall off, so the problem
> doesn't appear to be there. Checked my router and still no issues (not
> running a firewall on the router).
>
> Googling around there were some suggestions to use a bridged connection in
> Virtualbox as opposed to NAT, though if ssh is working, why wouldn't telnet
> and ultimately my browser.
>
> Looking for some suggestions / help on this issue.  Thank you!
>
> --
> 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/520ac130-6ace-4b6a-8769-27ae331565bf%40googlegroups.com
> <https://groups.google.com/d/msgid/vagrant-up/520ac130-6ace-4b6a-8769-27ae331565bf%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/CA%2BonWPdD45NA7P9Ovm2-K7XB85BQbecZ-f_r-ASCNXbzNutxow%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to