VMware Communities
gregorybfell
Contributor
Contributor

dell 630 network problems with vmw workstation?

hello....just got a new dell 630 laptop. am having problems with the networking for vm's. on every other machine i've ever used vmw ws on, it works great in the default bridged mode. seems i can get dhcp address etc...but no traffic can get out (or maybe back)....ie no internet, no ping, etc.

anyone?

0 Kudos
18 Replies
avarcher
Commander
Commander

Hi, I've a new 630 too and VMware Workstation networking works fine. There was a BIOS update to A04, that included a fix in A03 for wireless. Check your BIOS rev, I dont think the problem is with VMware. See

0 Kudos
gregorybfell
Contributor
Contributor

no changes. updated to the latest bios. the vm is set to 'bridged'. any other ideas? i think my other drivers are current.

0 Kudos
avarcher
Commander
Commander

There are a whole host of possibles here.

If you switch the VM to vmnet8(NAT) and release/renew does it get a 192 address and is it able to network to the outside world? Ping the host on it's vmnet8 address then try it's real external address.

If you look at 'Manage Virtual Neworks' "C:\Program Files\VMware\VMware Workstation\vmnetcfg.exe" can you change the automatic bridging to fixed on your nic? And does that make any difference?

0 Kudos
Greg_Fell
Contributor
Contributor

On VMnet(8) yes, it gets a new address, and it is able to reach the outside world. I can ping the NAT'ed address from my subnet.

When I bridge the ethernet connection to be the one chosen, the same behavior occurs (I get a DHCP address, and see the lease on my DHCP server. But no pings/traffic are successful.

I've reinstalled VMware, again reinstalled and this time removed the internet connection sharing service, and uninstalled my wireless NIC before reinstalling.

Any help would be greatly appreciated.

0 Kudos
Peter_vm
Immortal
Immortal

Please post "IPCONFIG /ALL" from host and guest, "vmware.log" from guest directory on host.

Also, screenshots of "Virtual Network Settings..." tabs would be helpfull.

Is firewall on host turned off?

0 Kudos
Greg_Fell
Contributor
Contributor

Also, I can ping the DHCP address from my subnet without it being NAT'ed. It seems like the issue is one way.

The firewall is turned off.

0 Kudos
Greg_Fell
Contributor
Contributor

VM

Windows IP Configuration

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :

IP Address. . . . . . . . . . . . : 192.168.0.7

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.168.0.1

C:\Documents and Settings\administrator>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : xp1

Primary Dns Suffix . . . . . . . : nessus.com

Node Type . . . . . . . . . . . . : Hybrid

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : nessus.com

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : VMware Accelerated AMD PCNet Adapter

Physical Address. . . . . . . . . : 00-0C-29-CF-54-A0

Dhcp Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 192.168.0.7

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. . . . . . . . . . : Tuesday, December 11, 2007 8:05:04 P

M

Lease Expires . . . . . . . . . . : Wednesday, December 12, 2007 8:05:04

PM

C:\Documents and Settings\administrator>

HOST

Microsoft Windows XP

(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Greg>IPCONFIG /ALL

Windows IP Configuration

Host Name . . . . . . . . . . . . : bigboy

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Unknown

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter VMware Network Adapter VMnet8:

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for

VMnet8

Physical Address. . . . . . . . . : 00-50-56-C0-00-08

Dhcp Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : 192.168.253.1

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . :

Ethernet adapter VMware Network Adapter VMnet1:

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for

VMnet1

Physical Address. . . . . . . . . : 00-50-56-C0-00-01

Dhcp Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : 192.168.214.1

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . :

Ethernet adapter Local Area Connection 2:

Media State . . . . . . . . . . . : Media disconnected

Description . . . . . . . . . . . : NVIDIA nForce MCP Networking Control

ler

Physical Address. . . . . . . . . : 00-0E-A6-64-95-59

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Marvell Yukon 88E8001/8003/8010 PCI

Gigabit Ethernet Controller

Physical Address. . . . . . . . . : 00-0E-A6-5F-8D-32

Dhcp Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : 192.168.0.100

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.168.0.1

DNS Servers . . . . . . . . . . . : 192.168.0.1

Ethernet adapter Bluetooth Network Connection:

Media State . . . . . . . . . . . : Media disconnected

Description . . . . . . . . . . . : Bluetooth Device (Personal Area Netw

ork)

Physical Address. . . . . . . . . : 00-0D-3A-A1-B8-8C

Ethernet adapter {0187EF69-3A62-4DE6-B159-A42CE53B4173}:

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Nortel IPSECSHM Adapter - Packet Sch

eduler Miniport

Physical Address. . . . . . . . . : 44-45-53-54-42-00

Dhcp Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : 0.0.0.0

Subnet Mask . . . . . . . . . . . : 0.0.0.0

Default Gateway . . . . . . . . . :

C:\Documents and Settings\Greg>

0 Kudos
Greg_Fell
Contributor
Contributor

added screen shots in attached doc

0 Kudos
Greg_Fell
Contributor
Contributor

added vmware.log

0 Kudos
Peter_vm
Immortal
Immortal

From screenshots:

1) You have unchecked "Automatic bridging", that is good. But you have bridged VMnet0 to adapter that is nonexistent on your host ?!

where is "Broadcom" NIC?

2) VMnet1 and VMnet8 are using different subnets than your host. How is that possible?

I think screenshots are NOT from your host, why is that?

0 Kudos
Greg_Fell
Contributor
Contributor

i'm working too much! here is the proper info

Microsoft Windows XP http://Version 5.1.2600

(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\gfell>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : bg-gfell01

Primary Dns Suffix . . . . . . . : Burwood.com

Node Type . . . . . . . . . . . . : Hybrid

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : burwood.com

burwood.com

Burwood.com

Ethernet adapter VMware Network Adapter VMnet8:

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for

VMnet8

Physical Address. . . . . . . . . : 00-50-56-C0-00-08

Dhcp Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : 192.168.230.1

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . :

Ethernet adapter VMware Network Adapter VMnet1:

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for

VMnet1

Physical Address. . . . . . . . . : 00-50-56-C0-00-01

Dhcp Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : 192.168.138.1

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . :

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Broadcom NetXtreme 57xx Gigabit Cont

roller

Physical Address. . . . . . . . . : 00-1C-23-09-C4-11

Dhcp Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 192.168.0.5

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. . . . . . . . . . : Tuesday, December 11, 2007 6:09:55 P

M

Lease Expires . . . . . . . . . . : Wednesday, December 12, 2007 5:31:34

PM

Ethernet adapter Wireless Network Connection 5:

Media State . . . . . . . . . . . : Media disconnected

Description . . . . . . . . . . . : Intel(R) PRO/Wireless 3945ABG Networ

k Connection

Physical Address. . . . . . . . . : 00-1C-BF-31-E6-51

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . : burwood.com

Description . . . . . . . . . . . : Cisco Systems VPN Adapter

Physical Address. . . . . . . . . : 00-05-9A-3C-78-00

Dhcp Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : 172.19.254.12

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . :

DNS Servers . . . . . . . . . . . : 172.17.1.151

172.17.1.150

Primary WINS Server . . . . . . . : 172.17.1.150

Secondary WINS Server . . . . . . : 172.17.1.151

C:\Documents and Settings\gfell>

0 Kudos
Peter_vm
Immortal
Immortal

Your guest connects to VMnet2 which you did not bridge - can you explain why?

Shutdown your CISCO VPN on host, or it will act as a very restrictive firewall/filter in your setup and will make analysis more difficult than neccessary.

Is guest's "IPCONFIG /ALL" from your previous post still valid?

0 Kudos
Greg_Fell
Contributor
Contributor

Not sure where you see it being connected to VMnet2. Could you explain?

I shut down the cisco vpn, still not working.

Yes the first ipconfig/all for the vm is correct.

0 Kudos
Peter_vm
Immortal
Immortal

Dec 11 18:13:17.671: vmx| DICT ethernet0.vnet = VMnet2

Please post current ".vmx" from guest directory on host.

0 Kudos
Greg_Fell
Contributor
Contributor

interesting, it does say vmnet2. i changed manually to vmnet0 and it didnt' work still.

0 Kudos
Peter_vm
Immortal
Immortal

Is that old ".vmx" or new? Because it still says VMnet2.

When you startup guest use static IP or release/renew. Post guest's IPCONFIG /ALL again.

0 Kudos
Greg_Fell
Contributor
Contributor

this is from the old one. here is the new one.

changed, rebooted vm, same problem

0 Kudos
Peter_vm
Immortal
Immortal

Reboot host.

When you startup guest use static IP or release/renew. Post guest's IPCONFIG /ALL again.

0 Kudos