virtualbox.org

I'm tired of searching for solutions (I'm not a computer scientist, and I have to get back to my
work - architecture), they pass 4 days and I do not see a solution. If someone did this out and
uses this configuration (but does not have time to explain) it may be the fastest will litter the
files to the substitution/replacement in the FW http://www.agnitum.com/support/kb/artic ... id=1000144 ?
Perhaps it would be easier to make a tutorial with screenshots (step by step)?
Of course, the desire to understand not to make the mistake again. Thanks for your time and help.

I tried this:

1. https://www.wilderssecurity.com/threads ... ss.244239/ ...not work

2. http://www.agnitum.com/support/kb/artic ... id=1000061 ...I may be wrong, but I understand what I do because it did not work

3. I tested on FW: Trusted zone, Nat Zone e.t.c

Soft. Config:

Host: Win 8.1 Pro N x64, +Outpost Firewall Pro 9.3 (+Nod AV 10, +Spybot) In my subjective opinion
it works faster than 7 and it is a lightweight solution to defend. VM 5.1.12
(hard. Config: CPU:i7-2630QM, RAM:16GB DDR2/CL10, SSD mSATA R:550 MB/s W:505 MB/s)

Guest1: Win 7 Ultimate x64 SP1, +Outpost Firewall Pro 9.3 (+Nod AV 10, +Spybot)

Guest2: Win XP Pro x86 (Outpost required SP3), +Outpost Firewall Pro 9.3 (+Nod AV 10, +Spybot)

All OS recompiltaion in Nlite (XP) and NTlite (7, 8.1) I added all updates KB and it works great,
when turn (host) firewall off internet works (Guest). When the test changed firewall (free30trial) Bitdefender
and NOD Sec. One message with a question and after approval of all work (NAT and Bridge)
oh, come on Outpost.

N.

Nic, since this is your first post, I'll point out that it is very hard to understand. You need to communicate in more complete thoughts and sentences.

If you get a Virtualbox popup error, press the Copy button in the error popup and post the text of the error here.

If you get an error in the guest, re-type the text of the error here, exactly as it is written in the guest OS.

nic wrote:All OS recompiltaion in Nlite (XP) and NTlite (7, 8.1)

This is very likely a game-stopper. Since N(t)lite modifies what's in the base operating system we cannot tell what has been removed, so we can't tell if an issue is with Virtualbox not finding something it usually would find in a full OS installation, or with Virtualbox itself.

I would try running a test guest with the basic Windows firewall in the host and guest, no other security programs, just to see if Virtualbox can connect your guest in a basic system. If this works, then the problem is with your add-on security products, not Virtualbox. In fact, you report:

nic wrote:when turn (host) firewall off internet works (Guest)

So you seem to be able to connect when the host firewall is off. So Virtualbox is working and the host firewall is the problem. You probably have to enable network access for Virtualbox in the firewall rules. Talk to those folks.

Thank you for your fast reply, I'll try to write simpler (but this is g.translator):

1. everything works correctly when the firewall is turned off

2. I asked for help with setting outpost here because VM creates something which is not properly understood in FW.
I have a problem only with the VM. Other programs do I block or allow Internet because rules are created correctly.

3. Your suggestions for not blocking VM firewall - is correct, I tried, it does not change anything.

N.

That's much clearer, Nic, thanks!

If everything works correctly when the firewall is turned off, then Virtualbox is working well. The issue would then be with the firewall settings. I have read the Windows sub-forums here for a while, and Outpost Firewall does not get mentioned very often, if at all. Most people here would not know how to set the firewall.

Try researching what settings to use in Outpost if you were running VMware or Hyper-V. The settings for Virtualbox would probably be similar.

And you should change the title of your first post to "Outpost Firewall Blocks Guest Internet" to attract any Outpost users.

Thx again for your reply, hm... essentially nothing? ok.

ad.1

scottgus1 wrote: If everything works correctly when the firewall is turned off, then Virtualbox is working well.

Are you kidding me? I wrote it in the first two posts. We can write like a long time but look for solutions?

ad.2

scottgus1 wrote: Try researching what settings to use in Outpost if you were running VMware or Hyper-V.

Hyper-V is turned on, I wrote that it works VM Guest1 win7 x64

ad.3

scottgus1 wrote:The settings for Virtualbox would probably be similar.

I agree, so it should work similarly but does not work, testing has long been Outpost.
In my opinion VM manager should be visible to the FW just like any other program.

The problem is to configure UDP and TCP, hoping for a response or files from someone who is already solved.

N.

nic wrote:I wrote that it works VM Guest1 win7 x64

No you did not. The first mention of Hyper-V in this thread is from me. if the underlined x64 in your quoted response, but not underlined in your first post, is supposed to mean that Hyper-V is running it, then you are extending the meaning of "x64" far beyond the way the rest of the world uses it. "x64" means 64-bit, not Hyper-V, and Virtualbox can run 64-bit guest's too. Get your facts straight.

If Hyper-V is turned on, then you are running two hypervisors at the same time: Hyper-V and Virtualbox. Unexpected results can happen. This is not recommended or supported. Nor are your N(T)lited operating systems.

nic wrote:your reply, hm... essentially nothing? ok.

OK, so you go and have fun with your firewall then. You have bitten the hand that was feeding you. I'm out.

Thx again for your reply

scottgus1 wrote:... far beyond the way the rest of the world uses it. "x64" means 64-bit, not Hyper-V, and Virtualbox can run 64-bit guest's too...

Correct me if I'm wrong but without using a Hyper-V can be installed only OS x86?

scottgus1 wrote: Nor are your N(T)lited operating systems.

This is the best way to add a file KB, did not have any other changes,
already but if you write about it again this situation is identical to clean copy OS
(If it would work, but it still needs the OS security patches, it's probably obvious?)

scottgus1 wrote: ...You have bitten the hand that was feeding you...

My intention was never to insult anyone... but I'm looking only solution to this problem
(I wrote to Support FW but as you know/or do not, that FW was sold and I doubt anyone wrote back).

N.

nic wrote:Thx again for your reply

scottgus1 wrote:... far beyond the way the rest of the world uses it. "x64" means 64-bit, not Hyper-V, and Virtualbox can run 64-bit guest's too...

Correct me if I'm wrong but without using a Hyper-V can be installed only OS x86?

N.

I will correct you because you are wrong. x64 does indeed mean 64-bit, and VirtualBox can run a 64bit OS. But Hyper-V has no place in this conversation. Hyper-V is the Windows virtualization software and should not be on your machine if you intend to use VirtualBox. What you do need to run 64-bit guests is for your system to support hardware virtualization. It must be available in your CPU and it must be enabled in the BIOS.

You are also wrong to assume that it is the fault of VirtualBox that your third-party firewall does not work well with VirtualBox. It is not. As scottgus1 said, if everything works fine with your firewall off, VirtualBox is working as it should. That is how it is designed and tested.

Thank you for your reply,

BillG wrote:It must be available in your CPU and it must be enabled in the BIOS.

And that is exactly I mean, thanks for the clarification

BillG wrote: VirtualBox is working as it should. That is how it is designed and tested.

ok, I do not want to argue (or badly we understand, the standard rule in the FW does not solve connections,
and it's not funny and will not serve to play, I'm not a child - as suggested scottgus1), looking still solutions,
writes here because I read a few persons/posts with similar configurations have tried to solve it in this forum.

N.

ps. bad time... aaaa...

"Thank you for your message.

Unfortunately, support and updates stopped on 9 January 2017. This was
a known issue, but the development of the program had ended before the
examination and fixing this issue.

Best regards,
Alexander.

Agnitum Support Team"

Thank you for posting the reply from Agnitum support.