IlDavo
Enthusiast
Enthusiast

XP Pro Guest Cannot Access Internet After WS 6.04 to 6.5 upgrade

Jump to solution

Hi, Can anyone offer suggestions as to why my guest OS can no longer see network resources after an upgrade to Workstation 6.5? Many thanks in advance!

Upgraded WS 6.04 to 6.5.0 build 118166 on XP Pro SP3 (32-bit) host, started XP Pro SP3 (32-bit) guest and upgraded VMWare Tools to 6.5.0 build 118166.

XP Pro SP3 guest could previously access LAN resources and Internet via NAT fine under 6.04. After upgrade, guest cannot see any network resources or Internet. Guest and VMWare WS report no errors.

ipconfig /all from guest:

Windows IP Configuration
Host Name . . . . . . . . . . . . : ESGRFS7-8-1SP4
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : localdomain
Ethernet adapter Local Area Connection 2:
Connection-specific DNS Suffix . : localdomain
Description . . . . . . . . . . . : VMware Accelerated AMD PCNet Adapter
Physical Address. . . . . . . . . : 00-0C-29-83-85-A6
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.5.128
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.5.2
DHCP Server . . . . . . . . . . . : 192.168.5.254
DNS Servers . . . . . . . . . . . : 192.168.5.2
Primary WINS Server . . . . . . . : 192.168.5.2
Lease Obtained. . . . . . . . . . : Monday, November 10, 2008 11:33:06 AM
Lease Expires . . . . . . . . . . : Monday, November 10, 2008 12:03:06 PM

ipconfig /all from host:

Windows IP Configuration
Host Name . . . . . . . . . . . . : DSaunders
Primary Dns Suffix . . . . . . . : us.witness.com
Node Type . . . . . . . . . . . . : Mixed
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : us.witness.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.5.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.44.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
Ethernet adapter Wireless Network Connection:
Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : Intel(R) PRO/Wireless 3945ABG Network Connection
Physical Address. . . . . . . . . : 00-1B-77-65-51-DE
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : sbcglobal.net
Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
Physical Address. . . . . . . . . : 00-1B-38-31-BB-4B
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 10.10.10.252
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.10.10.1
DHCP Server . . . . . . . . . . . : 10.10.10.1
DNS Servers . . . . . . . . . . . : 10.10.10.1
Lease Obtained. . . . . . . . . . : Monday, November 10, 2008 8:16:22 AM
Lease Expires . . . . . . . . . . : Tuesday, November 11, 2008 8:16:22 AM
Ethernet adapter Network Connect Adapter:
Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : Juniper Network Connect Virtual Adapter
Physical Address. . . . . . . . . : 00-FF-68-ED-1A-8B
Ethernet adapter Bluetooth Network:
Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : Bluetooth LAN Access Server Driver
Physical Address. . . . . . . . . : 00-1A-6B-85-D5-D7

Output from "ping google.com" on guest:

Ping request could not find host google.com. Please check the name and try again.

Ouput from "ping 209.85.171.99" on guest:

Pinging 209.85.171.99 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 209.85.171.99:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

Contents of .vmx file:

.encoding = "windows-1252"
config.version = "8"
virtualHW.version = "6"
scsi0.present = "TRUE"
memsize = "756"
ide0:0.present = "TRUE"
ide0:0.fileName = "Windows XP Professional-cl4-000001-cl3-000001-cl1.vmdk"
ide1:0.present = "FALSE"
ide1:0.fileName = "auto detect"
ide1:0.deviceType = "cdrom-raw"
floppy0.autodetect = "TRUE"
ethernet0.present = "TRUE"
ethernet0.connectionType = "nat"
ethernet0.wakeOnPcktRcv = "FALSE"
usb.present = "TRUE"
ehci.present = "TRUE"
sound.present = "TRUE"
sound.fileName = "-1"
sound.autodetect = "TRUE"
svga.autodetect = "FALSE"
pciBridge0.present = "TRUE"
mks.keyboardFilter = "allow"
displayName = "ESGRetail7.8.1_SP4_2CPUfromDS"
guestOS = "winxppro"
nvram = "ESGRetail7.8.1_SP4_2CPUfromDS.nvram"
deploymentPlatform = "windows"
virtualHW.productCompatibility = "hosted"
tools.upgrade.policy = "useGlobal"
floppy0.fileName = "A:"
numvcpus = "2"
floppy0.startConnected = "FALSE"
isolation.tools.hgfs.disable = "TRUE"
ethernet0.addressType = "generated"
uuid.location = "56 4d b8 b9 ae fa de 4a-b1 04 44 31 70 83 85 a6"
uuid.bios = "56 4d b8 b9 ae fa de 4a-b1 04 44 31 70 83 85 a6"
ide0:0.redo = ""
pciBridge0.pciSlotNumber = "17"
scsi0.pciSlotNumber = "16"
ethernet0.pciSlotNumber = "32"
sound.pciSlotNumber = "33"
ehci.pciSlotNumber = "34"
ethernet0.generatedAddress = "00:0c:29:83:85:a6"
ethernet0.generatedAddressOffset = "0"
extendedConfigFile = "ESGRetail7.8.1_SP4_2CPUfromDS.vmxf"
ide1:0.startConnected = "FALSE"
sharedFolder.option = "onetimeEnabled"
sharedFolder.maxNum = "1"
powerType.powerOff = "soft"
powerType.reset = "soft"
tools.syncTime = "FALSE"
sharedFolder0.present = "TRUE"
sharedFolder0.enabled = "TRUE"
sharedFolder0.readAccess = "TRUE"
sharedFolder0.hostPath = "C:\RawInstalls"
sharedFolder0.guestName = "RawInstallsFromHost"
sharedFolder0.expiration = "never"
inVMTeam = "FALSE"
checkpoint.vmState.readOnly = "FALSE"
checkpoint.vmState = ""
annotation =
sharedFolder1.present = "FALSE"
sharedFolder1.enabled = "FALSE"
sharedFolder1.readAccess = "TRUE"
sharedFolder1.hostPath = "P:\RawInstallFiles"
sharedFolder1.guestName = "RawInstallsFromNAS"
sharedFolder1.expiration = "never"
svga.maxWidth = "1680"
svga.maxHeight = "1050"
svga.vramSize = "7056000"
ide1:0.autodetect = "TRUE"
scsi0:1.present = "TRUE"
scsi0:1.autodetect = "TRUE"
scsi0:1.deviceType = "cdrom-image"
scsi0:1.startConnected = "FALSE"
vmotion.checkpointFBSize = "7077888"
scsi0:1.fileName = "C:\RawInstalls\MS\WinXPPro\WinXPPro_w_SP3.iso"

vmware log file attached.

Many thanks for any ideas!!!

Tags (3)
0 Kudos
1 Solution

Accepted Solutions
KevinG
Immortal
Immortal

Since you are using NAT networking, have you verified that the VMware NAT service is running?

View solution in original post

0 Kudos
3 Replies
KevinG
Immortal
Immortal

Since you are using NAT networking, have you verified that the VMware NAT service is running?

0 Kudos
drbohner
Contributor
Contributor

I'd, also, that the VMWARE NAT Service is failing for you (like it has for many of us).

You can set it to restart on First, Second, Third and EVERY failure (and after zero time) - and that puts a bandaide on the issue.

If Someone still has support (I think that 30 days is REDICULOUS) - please file an issue and share with the rest of us that 'band aided' our machines.

(db)

(db)
IlDavo
Enthusiast
Enthusiast

Very interesting! Following KevinG's tip, I found that my VMWare NAT service was, indeed offline and I restarted it. All was well.

...until I attempted to start another XP Pro SP3 vm whose virtual network adapter was not connected and I instructed WS 6.5 to "connect" its adapter via NAT. I then got an error indicating VMWare NAT service had failed. Windows error report files, attached.

I've thus far been unable to reproduce the conditions that led to failure. Many thanks to drbohner for the bandaide!

0 Kudos