n00b networking issues

[roly445]

I have just downloaded and installed Windows Home Server on virtual box. the host OS is Vista x64. The install went fine but I am now have network problems.

I have read through the help for virtual box and I understand that I want a bridged network because I want the the guest to see the other pcs on the network and vice-versa.

With it set to bridged, i can ping the local computers but not the internet.

Am I missing something?

Thanks for any help

[stefan.becker]

Add router as DNS Server in the Guest.

[roly445]

Thanks for the advise.
i added the dns server as the routers ip but it didn't work.
the router is giving the guest an ip and the router is picking up on the guest, but no traffic is getting outside of the network.

[vbox4me2]

Are all the ipsettings between Host and Guest the same apart from the machine's ip? can the Guest ping the router?

[stefan.becker]

Try disabling firewalls.

[roly445]

the guest cant ping the router or any other pc. pcs can ping the guest but not the router.
the guest can see network files on the host and the host can see networked files on the guest

[roly445]

i have disabled all the firewalls guest and host, but without any luck

[Sasquatch]

Did you check the VirtualBox FAQ already for possible DNS failure?

[roly445]

I did, but none of the points raised was like my own issue

[Sasquatch]

So accessing Google through the IP noted there doesn't work either? Are you sure you can access the rest of your physical network?

[roly445]

actually it cant. if its not on the host the guest cant see it. Damn my non static IPs.
Sorry about thats guys for throwing a spanner in the works there.

Any ideas?

[roly445]

ok the pc i was testing the ping on doesnt respond to pings from guest or host, but now both guest and host can access the 2nd pc's network shared files

[Sasquatch]

Which VB version are you using and what networking options? Maybe VB needs a repair option to get it's bridged network working. Check each machine IP settings, they should have the same configuration. Maybe using static addresses help.

[roly445]

I am running the last version, and i have already gone through the repair option, but without luck.

I am connecting onto the network successfully, but i still have no wan access.

the ip configuation is the same for both guest and host, i will paste the below.

guest

Code: Select all

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : AMD PCNET Family PCI Ethernet Adapter
   Physical Address. . . . . . . . . : 08-00-27-81-5E-C8
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   IP Address. . . . . . . . . . . . : 192.168.0.16
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.0.1
   DHCP Server . . . . . . . . . . . : 192.168.0.1
   DNS Servers . . . . . . . . . . . : 192.168.0.1
   Lease Obtained. . . . . . . . . . : 13 April 2009 11:23:03
   Lease Expires . . . . . . . . . . : 16 April 2009 11:23:03

host

Code: Select all

Ethernet adapter Local Area Connection 4:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : NVIDIA nForce Networking Controller Virtual #2
   Physical Address. . . . . . . . . : 00-04-4B-04-C8-BA
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::e9c8:b1b7:f588:be7f%17(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.0.10(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : 13 April 2009 10:44:04
   Lease Expires . . . . . . . . . . : 16 April 2009 10:44:15
   Default Gateway . . . . . . . . . : 192.168.0.1
   DHCP Server . . . . . . . . . . . : 192.168.0.1
   DNS Servers . . . . . . . . . . . : 192.168.0.1
   NetBIOS over Tcpip. . . . . . . . : Enabled

[Sasquatch]

Strange. Does your router have some sort of MAC filtering? Some routers, not many, can also use MAC filtering on wired connections. Check the log of the router for more info.