VMware Communities
brentofenstein
Contributor
Contributor

Bridged network not working with VMWare Fusion or Player

I just purchard a MacBook Pro.  I've installed VMWare Fusion.  I created a new guest running Windows 7 x64 Pro.  I'm using WiFi to connect the Mac to the network.  In the guest, networking using NAT is reliable.  However, using  the Bridged option is unreliable.  My guest gets an IP address from DHCP, but DNS seems to stop working.  This is intermittent, but frequent making Bridged not a viable option at the moment.

The router/DSL modem is the 2Wire 2701HG-B for AT&T.  For WiFi I'm using a Linksys E2000.

Today I also tested using the Bridged network option using VMWare Player from a Windows 7 laptop with a Windows 7 guest with the same results.  Bridged doesn't work, but NAT does. 

I'm frustrated because I want the Win7 VM to participate in the home network and use network resources, but it can't when using NAT.  I've seen a lot of discussions including the 2Wire router/modem.  Has anyone ever gotten this to work?

Reply
0 Kudos
9 Replies
rsicilia
Expert
Expert

Please, post the guest network configuration (full text) and describe your LAN.

Bye!

--
Rocco Sicilia [aka: BrC]
http://www.roccosicilia.it

Rocco Sicilia [aka: BrC] - http://www.roccosicilia.it - VTSP 4-5, VCP 4-5, vExpert 2013/2014
Reply
0 Kudos
continuum
Immortal
Immortal

Hi
did you already extyract the Virtual Network Editor for VMplayer ?
maybe you just need to disable "automatic bridging"


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

Reply
0 Kudos
brentofenstein
Contributor
Contributor


Windows IP Configuration

   Host Name . . . . . . . . . . . . : win7x64vm
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Broadcast
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : gateway.2wire.net

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . : gateway.2wire.net
   Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network Connection
   Physical Address. . . . . . . . . : 00-0C-29-4C-74-08
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::8586:8eb4:80a8:eacc%10(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.1.25(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Sunday, October 30, 2011 7:44:14 AM
   Lease Expires . . . . . . . . . . : Sunday, November 06, 2011 7:44:14 AM
   Default Gateway . . . . . . . . . : 192.168.1.1
   DHCP Server . . . . . . . . . . . : 192.168.1.1
   DHCPv6 IAID . . . . . . . . . . . : 234884137
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-16-36-0F-CF-00-0C-29-46-8D-5A

   DNS Servers . . . . . . . . . . . : 192.168.1.1
   NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.gateway.2wire.net:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : gateway.2wire.net
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Teredo Tunneling Pseudo-Interface:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

The strange thing is I can ping the Linksys, which is providing the wireless access from the guest, and I can even access the Linksys configuration web page, but I can't ping 192.168.1.1.  DHCP work fines though, becase as you can see from above, the guest gets an IP address from the router.

Reply
0 Kudos
brentofenstein
Contributor
Contributor

What did you mean by:

Hi
did you already extyract the Virtual Network Editor for VMplayer ?
maybe you just need to disable "automatic bridging"

I'm not sure how to do this.

Reply
0 Kudos
brentofenstein
Contributor
Contributor

I forgot to describe the LAN.  Here goes:

Wireless provided by Linksys E2000, IP address 192.168.1.108 (but I'm not using the E2000 as a router.)

DSL Modem/Router is 2Wire 2701HG-B, IP address 192.168.1.1

Guest is able to get DHCP address from 192.168.1.1, but unable to get to 192.168.1.1 shortly after getting an address.

Guest has no problem accessing Linksys configuration pages.

Let me know if there is anything else you would like to know about the LAN.

Reply
0 Kudos
orthohin
Enthusiast
Enthusiast

                        

LAN is kocal area network which can connect your local machine

Regards,
Milton

Never trust a computer you can't throw out a window
Reply
0 Kudos
wazzaF5
Contributor
Contributor

This is a problem for Player and Workstation 7.x that I am using. It used to be fine so something has changed...

I set the VMnet0 Bridged network connection to the actual physical nic in Virtual Network Editor - instead of Automatic but it makes no difference..

I get an IP from the routed network (cable modem) and can ping the modem and can ping the host PC and can nslookup to external DNS servers provided by the modem BUT cannot browse the WWW... wtf? (My VM's are Xp and Win 7 and 2008 R2 - but that is irrelevant it seems)

Has anyone had any success?

Reply
0 Kudos
brentofenstein
Contributor
Contributor

I did solve this by replacing my DSL modem/router. I had a 2Wire and after opening a support case with VMWare I was told that certain routers can cause the issue. I picked up a Motorola 3347

(at their recommendation) and haven't had the issue since. You might want try a different router and see if the problem goes away.

Reply
0 Kudos
srnhpp
Enthusiast
Enthusiast

                               

According to your configuration you did not enable DHCP or configure any ip maddress your second adapter. You just enable DHCP or confugare static IP address the Bridge network will work.

Reply
0 Kudos