virtualbox.org

I've come up to a point that I need to bridge a network between my guest and host OSes, but hit a roadblock.
When I'm using a bridged connection configuration on my guest, the guest can ping other computers on the Internet, but any TCP/UDP traffic seems to go out and not come back in, since I can't visit any pages on guest, nor can I connect to any services.

Yes, I have a router and yes, it assigns an IP address to the VM via DHCP, so issues with my ISP are out of the question.

My purpose for using a bridged network config is to be able to connect to a VPN, so unless there's some other way to achieve that, the problem above is the problem I'm asking for a solution for.

Thanks in advance for any replies and I hope I'll be able to supply more information on this topic, if any of you would need more.

This is a routing issue, maybe you have ports forwarded in your router that are pointing to the Host and not the Guest. Is the default gateway pointing to your router from all systems? is your router properly configured for NAT usage?

Everything was properly configured.
I figured it out though: it was Outpost Firewall making those issues.

Unfortunately, now I'm being hit with the VERR_SUPDRV_COMPONENT_NOT_FOUND error. I've tried reinstalling VBox and creating new machines, but so far - no result.

[ EDIT @ 2009-05-17 17:58 CET ]
Ok, fixed the driver error.
Now, I'd like to know if there's a way to overwork Outpost Firewall 4, so it doesn't block my incoming traffic via bridged network to my VM?

Bumping up the topic. Check the edited part in my previous post for the issue/question.

iNdefiNite wrote:Everything was properly configured.

[ EDIT @ 2009-05-17 17:58 CET ]
Ok, fixed the driver error.
Now, I'd like to know if there's a way to overwork Outpost Firewall 4, so it doesn't block my incoming traffic via bridged network to my VM?

That would be a question for Outpost http://www.outpostfirewall.com/

How about something more creative than that?

Lets see. You were having a problem with VBox and you asked here.
Now you stated that the problem was with Outpost and you think that asking Outpost is a problem? Where is the logic in that?
This is a VirtualBox forum, and we deal with VirtualBox issues.

Which is related to your software. I'm not gonna argue with you, as we probably have different points of view on the same topic and as I found my solution.

For further reference in problems regarding network connections of VMs and Outpost Firewall, here's a guide how to add rules to the firewall itself, based on VMWare: http://www.agnitum.com/support/kb/artic ... id=1000061