No Internet Access for one of the VM's NIC which showed 'Connected'

far from giving enough information
we'd need some tips about the adresses, the virtual switch configuration, the physical network topology if that is relevant...

if you can ping intermittently between hosts, i believe thes 2 hosts are either on different physical servers, on on different virtual switches. maybe the failover associated to a misconfigured network could be the cause if one of the links only is misconfigured

I'll check out if it's E1000/VMXNet3 tomorrow when back to office:
Do I just go to Win 2008's "View Network ..." to check this?

Attached another screen shot showing ipconfig & ping outputs
(where ipconfig is the output from Web10 but I've indicated
 the corresponding values for Web10)
ipconfigVMweb10-9.png

From the screen shot I've just attached, there's a default gateway.

What's 158.152.1.222 ?

check the VM settings, you are using E1000 network interface, I would recommend a change.

Ping/icmp is permitted throughout this customer's
entire network.  Below is the ping/tracert result.

I'm currently using E1000 (as I heard from the VMware
engr who set it up).  How do I change it to VMXNet3?


C:\Users\svnerxpos1>ping 158.152.1.222

Pinging 158.152.1.222 with 32 bytes of data:
Request timed out.

Ping statistics for 158.152.1.222:
    Packets: Sent = 1, Received = 0, Lost = 1 (100% loss),
Control-C
^C
C:\Users\svnerxpos1>tracert 158.152.1.222

Tracing route to demon-du.demon.co.uk [158.152.1.222]
over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  10.30.3.187
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6  ^C


I've done web_tracker's suggestion below, it did not help:
>Open up the control panel, double click on internet options, click on the connections
> tab. Click on the lan settings button, then check to see if the box use a proxy server
> for your lan is checked. If you don't normally use a proxy server for your lan
> uncheck the box and try checking the box automatically detect settings

Just got a duplicate IP pops up on this problem Web09 VM (see attachmt).
However, the address in conflict is not this 10.41.161.140 but 10.41.161.192
(shown in the next/last attachment).

To verify if there's really a duplicate IP addr issue with this problem
LAN2 port on Web09, I disabled LAN2 & did the following (which showed
there's no duplicate IP addr) :


C:\>nbtstat -A 10.41.161.140
Local Area Connection:
Node IpAddress: [10.41.161.32] Scope Id: []

    Host not found.


So the issue is not duplicate IP addr.  How do I change my
adapter to VMXNET3 ?
DupIPaddrConflictWeb09.png
NLBDupIPaddrscr.png

Typo error, the suspected duplicate IP is 10.41.161.40
(which is also not duplicated):

C:\>nbtstat -A 10.41.161.40
Local Area Connection:
Node IpAddress: [10.41.161.32] Scope Id: []

    Host not found.

C:\>

>you remove the existing E1000 network interfaces, Add New Network Interfaces,
>Edit VM Settings, . . .
Are the above done from within vCenter?  So VMware Tools must be installed
in the vCenter?

VMware Tools must be installed in the VM.

Adding Remove hardware does not have to be done in vCenter.

but from the vSphere Client.

From vCenter. I selected the problem VM (Web09), right click &
"Edit Settings" : refer to next attachment.

For comparison, I attached Web10's "Edit Settings" screen too:
they looked the same for the Network Adapter 2 settings:
both using E1000 but Web10 is fine but Web09 has issue:
Web09-NetAdap2.png
Web10-NetAdap2.png

yes, both should really be using VMXNET3.

I've managed to Remove the Network Adapter 2 from Web09 VM
& added a new one, using vmxnet3 (refer to attached).  However,
the same issue still persist.

Now, this time, looks like Network Adapter 1 (which I recall was
previously pingable from other subnets) is now not pingable from
other subnets too.
Web09vmxnetscr.png

okay, DNS resolution looks okay, can you ping the default gateway on your network?

just out of curiosity why do you have two nics?

Can't ping the default gateway.  Refer to attached screen shot

We want our IIS to listen to one of the NIC only & not the other NIC.
Web09-vmxnet3pingtests.png

Just removed LAN2 & add it back as "E1000" and it's now working:
refer to attached . . . . . weird

Now, I'll have to do the same for LAN1 (which is now not working)
after the earlier tweaking of LAN2.
Web09-Lan2OK.png

OS NICs are probably not registered correctly.

Think when the new NIC is added, need to specify the gateway for the NIC