Unable to access guest from non-local network

[Boxuser2016]

I have Ubuntu server 14.04 running as guest on Virtualbox.
The guest server is using bridged interface and has IP 10.0.0.2. (I need separate IP for the guest machine so I use bridged interface.)

From the network 10.0.0.0/24 I can access the server without any problems. (With SSH and some other protocols.)
I have other network 10.1.1.0/24. From there I can ping the virtual server but SSH and other connections fail.
From the 10.1.1.0/24 network I can access all other servers in the 10.0.0.0./24. Only servers hosted by Virtualbox are unreachable.

Firewalls should not be the problem. I have tried disabling them on both host and guest.
I have tried using both Windows and Linux as host OS. (Virtualbox 4.1.44-dfsg-1+deb7u1ubuntu1 on Linux host and 5.0.12 r104815 on Windows host.)

I have tried allowing promiscious mode for the VM.

These results indicate that Virtualbox in somehow preventing all connections but pinging from non-local networks.

What can I do to access my Virtualbox-hosted server from non-local network?

I was unable to find any similar problems from researching this problem.

[Perryg]

See what non-routable addresses are https://www.google.com/search?q=Non-Rou ... gws_rd=ssl

You could use VBox NAT and port forwarding. See the users manual.

[Boxuser2016]

As I stated in my original post I need to guest to have separate IP so I use bridged interface.

The 10.0.0.0/24 is just example, because I don't want to publish my public Ip range.
Routing between the networks works, the problem is that SSH packets fail to reach to VMs that are hosted by Virtualbox.

[Perryg]

The 10.0.0.0/24 is just example, because I don't want to publish my public Ip range.

Would have been nice if you stated that bit at the start so I didn't have to waste my time.

[Boxuser2016]

The 10.0.0.0/24 is just example, because I don't want to publish my public Ip range.

Would have been nice if you stated that bit at the start so I didn't have to waste my time.

My post made it very clear tough I did not explicitly state it.
Also the exact IP range used is irrelevant to my problem.

And it its normal practice to replace public IPs with some private range set.

[socratis]

I don't want to publish my public Ip range.

Here's mine: 85.73.108.138. Please hack me...

[Boxuser2016]

I don't want to publish my public Ip range.

Here's mine: 85.73.108.138. Please hack me...

I never said it has anything to do with security.

Also, I am busy enough without playing any "hacker" games.

[Perryg]

OK before this really gets out of hand here's the deal.

Without being able to tell what the actual addresses are I can tell you it sounds like a routing issue or filter of some kind. VirtualBox bridged acts like just another guest network on a real LAN.
I would use wireshark and see where the communication is failing. It could be that your provider is not allowing certain ports ( yes they do that ) or that they actually need to add a routing statement if the guest/s use public addresses.

[Boxuser2016]

Thank you for new reply. I'll try to see what I could find out with Wireshark.

Still I am convinced that that is not about the router and the packets get lost at Virtualbox.

There are many servers in my network. Some are physical and some are on Virtualbox and some virtualized with other tools.
From remote I can SSH to all these (and connect other opened ports too), execpt the ones that are hosted by Virtualbox. This should mean that ports between the networks are open.

I'll post my Wireshark findings here later.

[Perryg]

Here again Boxuser2016, this is information that was not available to anyone else. It is all but impossible to help without any information especially when dealing with a network.

At this point all anyone other than you know is you have a network issue and nothing to point to the actual cause. I appreciate your not wanting to divulge this information but without it the pieces just don't come together.

If I were you though I would try to shake off this it has to be VirtualBox that is causing this and focus on finding the real issue. The chances are far less that this is caused by VirtualBox than some other reason.

[Martin]

Is this bridged connection on a cabled LAN adapter or on WLAN?