virtualbox.org

Hi all, I have:
Windows 10
VB 5.0.12
Ubuntu Server 14.04 (no GUI)

Ping from host to guest is ok, but I cannot reach a web server created with Node.js from my host.

Fighting with this for two days

Minimum information needed for assistance.
As far as the "VBox.log.zip goes", here's what you do:
- Start the VM.
- Observe the problem.
- Shut down the VM.
- Right-click on the VM in the VirtualBox Manager.
- Select "Show Log..."
- Save it, ZIP it and attach it in your response.

socratis wrote: As far as the "VBox.log.zip goes", here's what you do:
- Start the VM.
- Observe the problem.
- Shut down the VM.
- Right-click on the VM in the VirtualBox Manager.
- Select "Show Log..."
- Save it, ZIP it and attach it in your response.

Thanks for your time. The VM is not showing any error in the command line nor in the log. The problem is the Host cannot reach the Guest's localhost when I type its address (ip:port). As I said, ping from host works fine but not telnet guest_localhost:port (192.168.1.108:3000). Another thing which is working normal is file sharing for instance. So I don't know what or where the problem is. I'm thinking it's a bug in Windows 10 or in VB 5.0.12.
Anyway, logs are attached.

Silly question, true: guest firewall?

scottgus1 wrote:Silly question, true: guest firewall?

Nop. I've just installed Ubuntu 14.04 and guest additions

Ping from host to guest is ok, but I cannot reach a web server created with Node.js from my host.

This suggests that the network stack is working and the real issue probably resides in the web server configuration.

Note: the firewall is not on by default in the Ubuntu server guest, but it might be on the host. Try using wireshark to see where the server call is being stopped.

Perryg wrote:

Ping from host to guest is ok, but I cannot reach a web server created with Node.js from my host.

This suggests that the network stack is working and the real issue probably resides in the web server configuration.

Note: the firewall is not on by default in the Ubuntu server guest, but it might be on the host. Try using wireshark to see where the server call is being stopped.

Here is the code how I created the server. I'm new with JavaScript but I assumed this is ok according to the Lynda tutorial I'm watching.

I'll check how to use wireshark.

I assumed this is ok according to the Lynda tutorial I'm watching

Why are you not talking to Lynda? It is after all their tutorial.

I know people want to just assume that all their issues are due to VirtualBox but in fact most are not. You have demonstrated that the network stack is actually working so the next step would be to find out why the end point is not replying as you expect.

Perryg wrote:

I assumed this is ok according to the Lynda tutorial I'm watching

Why are you not talking to Lynda? It is after all their tutorial.

I know people want to just assume that all their issues are due to VirtualBox but in fact most are not. You have demonstrated that the network stack is actually working so the next step would be to find out why the end point is not replying as you expect.

You might be right. However, I assumed the code is ok is because I'm watching a video tutorial where things are working plus because I've read a lot about this issue since yesterday and I've found lots of questions about with no answer.
Additionally, (and better we should focus on this) why I think the problem is not in the code is because telnet command shows error in the connection to the guest in the port given. (ping ok, telnet not ok).

Ok and why do you not think this is the guests issue?

I really think you are chasing red herrings here. First I would make sure that the web server is working as it is supposed to and is configured properly. Since node.js is an application I would leave it out of the equation until you verify that the server is actually replying as it should. Then after you have verified that, add the next step in and test it.

Anyway good luck and I will leave you with it. I only posted to let you know at this point it does not appear to be a VirtualBox issue and save you some time. If you can point to something that does indicate a VirtualBox issue I or someone else here will be more than happy to assist.

Perryg wrote:Ok and why do you not think this is the guests issue?

I really think you are chasing red herrings here. First I would make sure that the web server is working as it is supposed to and is configured properly. Since node.js is an application I would leave it out of the equation until you verify that the server is actually replying as it should. Then after you have verified that, add the next step in and test it.

Anyway good luck and I will leave you with it. I only posted to let you know at this point it does not appear to be a VirtualBox issue and save you some time. If you can point to something that does indicate a VirtualBox issue I or someone else here will be more than happy to assist.

Thanks man. You are right. I've changed the code and server is working.