[Solved] Win7 x64 Host Win7 x64 Guest network failing

[MacNala]

Hi,
I have a Win7 x64 host in which I have VB 3.0.10 and set up a Win7 x64 guest.
I can get internet access from the guest to work setting a network adapter to Intel PRO/1000 MT Desktop (85240EM) attached to NAT.
I can get network access from the guest to the host setting a network adapter to Host-only and attached to Virtualbox Host-only Ethernet adapter and from the host to the guest as well.

The host is a member of a workgroup (not WORKGROUP) to allow it access to the other machines in the local network (Not a domain) I have set the workgroup in the guest to be the same but I cannot get the guest to see the workgroup computers nor can they see the guest.
I have tried attaching the network adapter to Bridged Adapter but can not get any access to the host, the internet or the workgroup computers.

I have obviously missed something in the setup but cannot find an answer in the forums.
Can anyone help point me in the right direction?

[vbox4me2]

Using Bridge is the proper way, are you sure your router is giving IP details to your Guest?

[MacNala]

Thanks for the reply.
There was no IP address allocated at all. So I have tried allocating an IP address from the range my router supports but there is still no connection to the Workgroup.
Any more suggestions?

[vbox4me2]

Just an IP doesn't work without the mask, default route and such, are you sure they are all set properly?

[BillG]

That is odd. If you are using bridged mode, the vm should get its network config automatically, just like the host or other machines on the LAN. Works fine on my system with Win 7 x64 on host and guest.

Have you tried doing "ipconfig /release" followed by "ipconfig /renew" from a command prompt?

If it won't get its config automatically, you can try manually configuring it. The netmask and gateway should match the config of the host.

When you look at the NIC properties from the host OS, is there an entry for VirtualBox Bridged Networking Driver? Is the box checked?

[MacNala]

Yes the mask is set correctly. I don't know about the route.
I have examined the other ways of connecting to the host and to the internet. The IP address is one of the 10.0.2.n variety which may be the cause of my problem. I also am trying out Virtual PC and it seems to connect correctly through the gateway and obtain an IP address in the range which is supported by my router. The two machines I have installed under Virtual PC both work and connect properly.

So back to VBox; Is there a way of setting the default gateway of the adapter controller to use the range in my router. It is a very simple router a SMC7004ABR Barricade . I can't see any way to allow 10.0.2.n addresses through it.

[MacNala]

[quote="BillG"]
That is odd. If you are using bridged mode, the vm should get its network config automatically, just like the host or other machines on the LAN. Works fine on my system with Win 7 x64 on host and guest.

Have you tried doing "ipconfig /release" followed by "ipconfig /renew" from a command prompt?

If it won't get its config automatically, you can try manually configuring it. The netmask and gateway should match the config of the host.

When you look at the NIC properties from the host OS, is there an entry for VirtualBox Bridged Networking Driver? Is the box checked?[/quote]

I will get back to you tomorrow it is long past my bed time here.

[MacNala]

[quote="BillG"]That is odd. If you are using bridged mode, the vm should get its network config automatically, just like the host or other machines on the LAN. Works fine on my system with Win 7 x64 on host and guest.

Have you tried doing "ipconfig /release" followed by "ipconfig /renew" from a command prompt?

If it won't get its config automatically, you can try manually configuring it. The netmask and gateway should match the config of the host.

When you look at the NIC properties from the host OS, is there an entry for VirtualBox Bridged Networking Driver? Is the box checked?[/quote]
I have tried the suggested ipconfig commands without success. To illustrate I attach two images one shows the rersponse to a simple ipconfig with the IPAddress supposed to be obtained automatically. The other with the adapter configured to a specfici address in the router range and the gateway mask and DNS set correctly.
[img][attachment=1]ipconfig ipaddress not specified.png[/attachment][/img][img][attachment=0]ipconfig ipaddress specified.png[/attachment][/img]
This may or may not explain the problem I am not an expert in reading these things.
Perhaps someone can help.

[BillG]

The 169.254 IP as an APIPA address. You get that sort of address if the machine is configured to get its IP address automatically but a DHCP server is no available. So that confirms that the client cannot get its IP address automatically.

The manual address looks OK. Can you ping the gateway at 192.168.2.1 or the host machine's IP? Can you ping this machine's own IP?

[MacNala]

Hi BillG,

Pinging gave no response in fact it said transmit failure.

BUT

I have solved my problem through a procedure of exploring all the possible options
I have found that to enable the Bridged Adapter successfully I also needed to select the Marvell Yukon 88E8056 PCI-E Gigabit Ethernet Controller [u]#2[/u].
Everything now works Access to internet, Access to host libraries and files, Access to other workgroup member machines and files.

Yippee.
Now I can concentrate on the other problems
No Stereo sound.
Virtualbox and Virtual PC at the same time.
Understanding Snapshots.