Enabled bridged networking: can't ping host

Discussions related to using VirtualBox on Windows hosts.
Post Reply
hugoestr
Posts: 15
Joined: 16. Nov 2009, 21:50
Primary OS: MS Windows XP
VBox Version: OSE self-compiled
Guest OSses: Windows Server 2008, Windows Server 2008, Ubuntu 9.10, Windows XP

Enabled bridged networking: can't ping host

Post by hugoestr »

Hi, there,

I need the access a sql server db on my host computer from the virtual machine. The virtual machine is a Windows Server 2003. I have configured the db to run tcp services on the host computer. On the guest, sql server management studio can see the dbs on my host computer. However, when I try to access it, I get an error saying that they can't find the server.

On the guest computer I have access to the internet and to shared drives. However, I can't ping the host computer.

Any ideas on what else should I try?

Hugo
Perryg
Site Moderator
Posts: 34369
Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX

Re: Enabled bridged networking: can't ping host

Post by Perryg »

Make sure you don't have a firewall issue.
hugoestr
Posts: 15
Joined: 16. Nov 2009, 21:50
Primary OS: MS Windows XP
VBox Version: OSE self-compiled
Guest OSses: Windows Server 2008, Windows Server 2008, Ubuntu 9.10, Windows XP

Re: Enabled bridged networking: can't ping host

Post by hugoestr »

No, both computers have their firewall turned off while I am configuring them right now.
Perryg
Site Moderator
Posts: 34369
Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX

Re: Enabled bridged networking: can't ping host

Post by Perryg »

You need to run ipconfig /all in the host and the guest and post them here.
Also post the network settings you have in the VBox program.
hugoestr
Posts: 15
Joined: 16. Nov 2009, 21:50
Primary OS: MS Windows XP
VBox Version: OSE self-compiled
Guest OSses: Windows Server 2008, Windows Server 2008, Ubuntu 9.10, Windows XP

Re: Enabled bridged networking: can't ping host

Post by hugoestr »

Okay, here you go

Host
Windows IP Configuration

Host Name . . . . . . . . . . . . : FKK10KXY2
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : muzhnas

Ethernet adapter Wireless Network Connection:

Connection-specific DNS Suffix . : muzhnas
Description . . . . . . . . . . . : Intel(R) WiFi Link 5100 AGN
Physical Address. . . . . . . . . : 00-21-5D-C9-F9-30
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.2.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.2.1
DHCP Server . . . . . . . . . . . : 192.168.2.1
DNS Servers . . . . . . . . . . . : 192.168.2.1
64.83.1.10
209.137.171.20
Lease Obtained. . . . . . . . . . : Wednesday, November 18, 2009 10:42:43 AM
Lease Expires . . . . . . . . . . : Wednesday, November 25, 2009 10:42:43 AM

Ethernet adapter Network Bridge:

Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : MAC Bridge Miniport
Physical Address. . . . . . . . . : 02-21-70-C6-95-37

Ethernet adapter VirtualBox Host-Only Network:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VirtualBox Host-Only Ethernet Adapter
Physical Address. . . . . . . . . : 08-00-27-00-88-50
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.56.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
Guest

Windows IP Configuration

Host Name . . . . . . . . . . . . : sharepointcomputer
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : muzhnas

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : muzhnas
Description . . . . . . . . . . . : AMD PCNET Family PCI Ethernet Adapter
Physical Address. . . . . . . . . : 08-00-27-11-13-3F
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.2.5
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.2.1
DHCP Server . . . . . . . . . . . : 192.168.2.1
DNS Servers . . . . . . . . . . . : 192.168.2.1
64.83.1.10
209.137.171.20

Lease Obtained. . . . . . . . . . : Wednesday, November 18, 2009 5:35:16 PM
Lease Expires . . . . . . . . . . : Wednesday, November 25, 2009 5:35:16 PM
Perryg
Site Moderator
Posts: 34369
Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX

Re: Enabled bridged networking: can't ping host

Post by Perryg »

I need to know the exact guest settings that you are using. Do you have the wireless card selected in the settings.
Open the VBox guest setting and expand all of the areas and post a screen shot if nothing else.

If all else fails you can set the 1st adapter to host-only and then set a second adapter to NAT or Bridged for the Internet.
hugoestr
Posts: 15
Joined: 16. Nov 2009, 21:50
Primary OS: MS Windows XP
VBox Version: OSE self-compiled
Guest OSses: Windows Server 2008, Windows Server 2008, Ubuntu 9.10, Windows XP

Re: Enabled bridged networking: can't ping host

Post by hugoestr »

Oops, sorry. I missed that. Here you go:
Image
hugoestr
Posts: 15
Joined: 16. Nov 2009, 21:50
Primary OS: MS Windows XP
VBox Version: OSE self-compiled
Guest OSses: Windows Server 2008, Windows Server 2008, Ubuntu 9.10, Windows XP

Re: Enabled bridged networking: can't ping host

Post by hugoestr »

I just tried to ping in both directions. I was able to ping the guest computer from the host, but not ping host from the guest.
Perryg
Site Moderator
Posts: 34369
Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX

Re: Enabled bridged networking: can't ping host

Post by Perryg »

Ping in only one direction Sounds like a firewall issue. You said they were all off right? Something is filtering it in one direction.
hugoestr
Posts: 15
Joined: 16. Nov 2009, 21:50
Primary OS: MS Windows XP
VBox Version: OSE self-compiled
Guest OSses: Windows Server 2008, Windows Server 2008, Ubuntu 9.10, Windows XP

Re: Enabled bridged networking: can't ping host

Post by hugoestr »

I wonder what it could be. The windows firewalls are turned off. The anti-virus program doesn't seem to include a a firewall. and I assume that the filtering must be happening on the host computer, right? Or could the router have something to do with it too?
Perryg
Site Moderator
Posts: 34369
Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX

Re: Enabled bridged networking: can't ping host

Post by Perryg »

Maybe a tracert will show where it is stopping.
It could be the router or any computer that is running on your system.
Try disabling the virus software until you are done testing.
hugoestr
Posts: 15
Joined: 16. Nov 2009, 21:50
Primary OS: MS Windows XP
VBox Version: OSE self-compiled
Guest OSses: Windows Server 2008, Windows Server 2008, Ubuntu 9.10, Windows XP

Re: Enabled bridged networking: can't ping host

Post by hugoestr »

Okay, I it working now. Thanks for your help. :)
Perryg
Site Moderator
Posts: 34369
Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX

Re: Enabled bridged networking: can't ping host

Post by Perryg »

What was the problem?
Someone else may have this and it would help them.
hugoestr
Posts: 15
Joined: 16. Nov 2009, 21:50
Primary OS: MS Windows XP
VBox Version: OSE self-compiled
Guest OSses: Windows Server 2008, Windows Server 2008, Ubuntu 9.10, Windows XP

Re: Enabled bridged networking: can't ping host

Post by hugoestr »

Hi,

I tried to post the answer yesterday, but I hit save instead of submit by mistake.

There seem to be at least two problems. One of the problems was that the ip address seems to have changed for the host and the guest didn't know that. There is also a problem going on with the domain name server since sometimes it seems to recognize the host computer as being in the same network and sometimes it tries to find it out on the internet.
Post Reply