Host and Guest Network Adapter Issue

[StuckinDC]

Please forgive me as I know this type of question has been asked before, but I need
some guidance on configuring my Virtual Box for so that it can "communicate"/see the host OS.
This is my first time using a virtual machine and running a server. Here goes:

I am running Windows Server 2008 R Standard as a host OS and
Windows Server 2008 Standard (Core Installation) as a guest
via Virtual Box (v. 3.2.8 r64453). The core installation worked
like a charm and continues to run smoothly.

My network adapter is Broadcom NetXtreme 57xx Gigabit Controller (Driver: 10.100.4.0)

I named each system and provided the correct IP data of which I have verified many times!

All I want to do at this point is to allow the host and guest to communicate,
and I do not need Internet access or anything like that. These are only two
OSs I have installed on my stand-alone system.

My issue is that while in the guest, I am unable to ping the guest itself or the host.
I also cannot ping the guest while in the host.

I have read Virtual Box's "Virtual Networking" section in the manual and used the Virtual Box's 'Network'
option to modify the adapter Virtual Box will use. I have read numerous posts on this website and
the Internet in general and I still cannot get them to "communicate"/see each other.

Can you please let me know if I need to complete any of the following?
-Do I need to connect a network cable from the system a hub to "enable" the network adapter?
-Do I need to update the network adapter driver to Intel PRO/1000 MT Desktop?
-Do I need to click on the network adapter and Virtual Box's network adapter at the same
time and select bridge? If so, are there any other settings I need to modify?

Here is the IP data -provided by Microsoft's 70-640 Training Kit book
Chapter 1
---------------------------------------------------------------------
Windows Server 2008 R Standard-
IP Address: 10.0.0.11
Subnet Mask: 255.255.255.0
Default Gateway: 10.0.0.1
Preferred DNS Server: 10.0.0.11

Windows Server 2008 Standard (Core Installation)-
IP Address: 10.0.0.12
Subnet Mask: 255.255.255.0
Default Gateway: 10.0.0.1
Preferred DNS Server: 10.0.0.11


Thanks for your help!

[Perryg]

Use host-only instead of NAT

[StuckinDC]

I am not using NAT. NAT has never been an option in my set-up. Please help if you can. Thanks.

[Perryg]

OK so what are you using. I can guess or you can tell me which would be faster. Bridged, NAT, Internal, or host-only.

See Chapter 6.2. Introduction to networking modes in your VirtualBox users manual.

[StuckinDC]

Hey Perryg,

I should have provided that information in my first post. Sorry. I had read chapter 6 prior to starting but for some reason I am not understanding something here. As I stated in my original post, all IP data has been verified and both OSs and Virtual Box are operating smoothly.

In the Network section, under the Adapter 1 tab, I have selected Host-only Adapter with Intel PRO/1000 MT Desktop as my Adapter Type, and have Enable Network Adapter and Cable Connected checked. I also have an Ethernet cable plugged into the system that is connected to a stand-alone hub. Each adapter can only ping itself while not in bridge mode. I receive various errors when in bridged mode.

All I want to do at this point is to allow the host and guest to communicate, and I do not need Internet access or anything like that. These are only two OSs I have installed on my stand-alone system.

Please let me know if you need anything else.
Thanks for helping me!

[Perryg]

If you only want the host and the guest to communicate use host-only.
If you want two guests to talk and not the host use Internal.
None of these will allow Internet access but from the sound of it you don't want/need it.
Make sure that your Firewall is configured to allow the traffic and it should work just fine.
The OSes will need to be in the same workgroup/domain and the IP addresses will need to be in the same scheme.
You will not need an external switch or router for this unless you want the host to have Internet access.