Unable to ping ESXi 5.5 VM workstation 11 comments

Similar Questions

• Unable to Ping IP across 2 IPsec Tunnels

  Hello world

  Here's the Setup program

  Server1 - layer 2 switch-ASA1 -L2 tunnel-ASA2 -Layer2 tunnel-ASA3- layer 2 switch - Server2.

  Server1 IP 10.31.2.83/28

  Server2 IP 10.31.2.35/28

  Server1 has its default gateway to ASA1

  Server1 can ping the ASA1 but cannot ping the Server2.

  ASA1 is also unable to ping server2.

  Ping 10.31.2.35
  Type to abort escape sequence.
  Send 5, echoes ICMP 100 bytes to 10.31.2.35, wait time is 2 seconds:
  ?????
  Success rate is 0% (0/5)

  ASA2 can ping the Server2

  Ping 10.31.2.35
  Type to abort escape sequence.
  Send 5, echoes ICMP 100 bytes to 10.31.2.35, wait time is 2 seconds:
  !!!!!
  Success rate is 100 percent (5/5), round-trip min/avg/max = ms 02/01/10

  ASA2 can ping Server1

  Ping 10.31.2.83
  Type to abort escape sequence.
  Send 5, echoes ICMP 100 bytes to 10.31.2.83, wait time is 2 seconds:
  !!!!!
  Success rate is 100 percent (5/5), round-trip min/avg/max = ms 02/01/10

  ACL is allowing traffic, routing, crypto card also allows the traffic.

  What else can I check?

  Any help is appreciated.

  Concerning

  Mahesh

  I don't understand what you mean with Tunnel of Layer2. Is it relevant to this question?

  IPsec is involved?

  Do you have any troubleshooting basic Layer 3? Check the routing information?

  (1) the ASA2 has 2 interfaces, one for each tunnel?

  • ASA2 there transatlantic lines?
    • 10.31.2.80 255.255.255.240 to ASA1
    • 10.31.2.32 to ASA3 255.255.255.240

  (2) ASA2 has only one interface for the two tunnels?

  • You same-security-traffic allow intra-interface?
  • If IPsec is involved, understanding Cryptography ACLs on ASA2
    • 10.31.2.80/28-> 10.31.2.32/28 to ASA3
    • 10.31.2.32/28-> 10.31.2.80/28 to ASA1

  The following command will help all three ASAs:

  SH, route

  HS card crypto

  SH crypto ipsec his (look for the counters of packets on the SAs)

  Best regards, MiKa

• Unable to ping a website in command line with an error message: 'ping is not recognized as an internal or external command.'

  Original title: ping does not work

  In the cmd box when I try to ping from a site, I get a message saying 'ping is not recognized as an internal or external command.'

  I entered the command as follows: Office > ping www.yahoo.com

  Dan Calic, salvation

   

   

  Thanks for posting your question in the Microsoft Community.

  I understand that you are unable to ping a website in command line with an error message: 'ping is not recognized as an internal or external command.' Correct me if I'm wrong.

  I imagine the inconvenience that you are experiencing. I will certainly help the question of fixing.

  To help you suggest several steps to solve the problem, I would appreciate if you could answer the following questions:

  1 are you facing problems when accessing Internet?

  2. have you made any recent hardware or exchange of software on your computer before the show?

  Please follow the steps and check the question below:

  a. click Start, and then type the three letters cmd in the search box and then right-click on command prompt and click run as administrator.

  b. type these commands and press enter after each:

  dir %SystemRoot%\System32\ping.exe

  path %path%;%SystemRoot%\System32

  Ping www.yahoo.com

  c. a report.

  Your response is very important for us to ensure a proper resolution. Please get back to us with the information above to help you accordingly.

• Unable to ping Virtual Machines within ESXi host (vSphere Home Lab)

  I'm using VMware workstation 9, I have 4 virtual machines created inside the workstation.
  (192.168.1.0 network is defined inside VMware workstation VM network editor)

  Domain controller - 192.168.1.1
  ESX1 - 192.168.1.11 (2 NICs - vmnic0 and vmnic1 connected to n/w)
  Esx2 - 192.168.1.12 (2 NICs - vmnic0 and vmnic1 connected to n/w)
  Management Server - 192.168.1.5

  I have 2 virtual computers created inside the machine Esx1

  machine to SQL - 192.168.1.4
  vcenter1 - 192.168.1.2

  I have 1 computer virtual created inside the Esx2 machine

  vcenter2 - 192.168.1.3

  I can ping all the machines in the administration server - no problem

  Question - I can not ping vcenter1 to sql, cannot ping vcenter1 to vcenter2, cannot ping vcenter2 to sql.
  There is basically no communication between virtual machines with the Esx host and in the whole of the host. Firewalls is disable on all these machines virtual esx internal hosts.

  Any ideas how to solve this problem?

  Make sure that virtual network on ESXi hosts maps are Sunrise promiscous mode networking.

• RHEL6 VM workstation: unable to ping with bridged connection gateway

  I have here is the config for my workstation RHEL6.

  1. WLAN card: filled with the "physical replicate network connection' checked box (I tried unchecking the checkbox as well)

  2. I have my host connected to the router via LAN. (Router IP: 192.168.3.1;) Host IP: 192.168.3.100)

  2. / etc/sysconfig/network file as below:

  Networking = yes

  Hostname = AYMsimvm1

  GATEWAY 192.168.3.1 =

  3. / etc/sysconfig/network-scripts/ifcfg-eth0 file as below:

  Networking = yes

  BOOTPROTO = dhcp

  DEVICE = eth0

  4. I can see my IP VM (192.168.3.150) registered in the list of clients of the router

  5 MAC address of eth0 corresponds to the .vmx file recorded in the router

  5. various command output as below

  ~: root $ ifconfig

  eth0 Link encap HWaddr 00:50:56:34:2E:9E

  INET addr:192.168.3.150 Bcast:192.168.3.255 mask: 255.255.255.0

  ADR inet6: fe80::250:56ff:fe34:2e9e / 64 Scope: link

  RUNNING BROADCAST MULTICAST MTU:1500 metric: 1

  Fall of RX packets: 147 errors: 0:0 overruns: 0 frame: 0

  Dropped packets: 271 TX errors: 0:0 overruns: 0 carrier: 0

  collisions: 0 txqueuelen:1000

  RX bytes: 14292 (13,9 KiB) TX bytes: 21919 (21.4 KiB)

  Lo encap:Local Loopback link

  INET addr:127.0.0.1 mask: 255.0.0.0

  ADR inet6:: 1/128 Scope: host

  RACE of LOOPING 16436 Metric: 1

  Fall of RX packets: 160 errors: 0:0 overruns: 0 frame: 0

  Dropped packets TX: 160 errors: 0:0 overruns: 0 carrier: 0

  collisions: 0 txqueuelen:0

  RX bytes: 8324 (8,1 KiB) TX bytes: 8324 (8,1 KiB)

  ~: root $ ping - I eth0 192.168.3.100 < this is IP host >

  PING 192.168.3.100 (192.168.3.100) from 192.168.3.150 eth0: 56 (84) bytes of data.

  64 bytes of 192.168.3.100: icmp_seq = 1 ttl = 64 time = 13.6 ms

  64 bytes of 192.168.3.100: icmp_seq = 2 ttl = 64 time = 0.809 ms

  ^ Z

  [5] + Stopped ping - I eth0 192.168.3.100

  ~: root $ ping - I eth0 192.168.3.1 < it's IP router, ping crashes >

  PING 192.168.3.1 (192.168.3.1) from 192.168.3.150 eth0: 56 (84) bytes of data.

  ^ Z

  [6] + Stopped ping - I eth0 192.168.3.1

  ~: root $ road n

  Kernel IP routing table

  Destination Gateway Genmask Flags metric Ref use Iface

  192.168.3.0 0.0.0.0 255.255.255.0 U 1 0 0 eth0

  0.0.0.0 192.168.3.1 0.0.0.0 UG 0 0 0 eth0

  ~: root $ ping - I eth0 google.com

  ^ Z

  [7] + Stopped ping - I eth0 google.com

  ~: root $

  Thank you for helping me with this.

  Nothing was wrong with the configuration of the VM.

  My firewall was blocking traffic in and out of the virtual IP network machine.

• Virtual MACHINE is unable to ping host and vice versa

  It is a very strange problem.  VMWare support tried to understand this output as Dell.  So, I just throw it to the community to see if anyone else has experienced this problem and may have a solution.  I have 3 identical Dell R720 servers.  2 work with no problem, but 1 (let's call it vm8) gave me problems since day 1.  Reference verified Dell equipment today and has updated me the BIOS, firmware and drivers on vm8, which did not solve the problem.  VMWare technicians checked each parameter network in recent weeks and currently, they are not the cause.

  VM8 have ESXi installed 5.5.0.  The Server 4 has 2 NICs with 4 ports each.  Current configuration is vmnic 0-3 is connected to our LAN, 4-5 on our DMZ and 6-7 in our SAN (iSCSI). The AP will go up and down because VM8 loses connectivity to our isolation address (gateway).

  VM8 (Mgmt IP network is 172.20.100.9) has only 1 VM (172.20.100.40). Same subnet (255.255.255.0).  .9 happens to ping expiration.40 using vmkping.  When I ping.9 de.40, the first package gets a quick response, then all following packets timeout.  According to VMWare, when you ping in (VM to host) it does not go out through the card physical network to the physical switch.  Everything is internal with vmnic and vSwitch.  When I ping my gateway (172.20.100.1), the ping is successful.  When I ping.9 from my workstation, the first packet times out, then answered the following packages.  It is the exact opposite of ping the virtual computer.

  Here's a better ventilation-

  .9 VM8 host

  .40 VM on the host VM8

  .1 gateway

  .122 workstation over LAN

  .25 vRanger connection (physical server on LAN)

  Ping

  .9 40 (100% packet loss)

  first package de.40 a.9 (75% packet loss) Gets the response, then 3 timeout

  .9 a.122 good ping (0 packet loss)

  .122 a.9 (0 packet loss) good ping

  vmkping (75% loss).9 a.25 does not appear each packet that it is sent.  But other results, can I assume first package times out.

  first package de.25 a.9 (75% loss) has expired, the following 3 got a response

  .40 a.122 good ping (0 packet loss)

  . 122. 40 (100% packet loss)

  The 3 can ping a.1 (every 20 minutes on VM8 I get a "vSphere HA agent on this host failed isolation address 172.20.100.1"

  Also, throughout the day, I get the message - "vSphere HA agent on this host cannot reach some of the management of the addresses of network of other hosts, and HA is perhaps not able to restart the virtual computer if a failure of the host is displayed."  I came to work in the morning, and all my VMS on VM8 migrated to my other 2 hosts.  My backups don't work on VM on VM8.  I use vRanger connection and when I ping connection vRanger VM8 (physical server), the first package expires and the following packages get a response.  Then, when connection vRanger goes to back up my VM, runs aground due to loss of original packet.

  These are things I've already tried.  I tested individually each physical NETWORK adapter.  I removed all the ports on the two NIC to try to isolate a specific port. All the 4 vmnic is active adapters in network properties NIC Teaming management and I moved each vmnic individually to unused to test each port.  I replaced the Cat6 cables.  I used different Dell switches and various ports of the switch.  I even swapped the switch ports that host another employee, exclude a switch port configuration problem. In addition, port security is disabled on the ports.  I upgraded ESXi 5.5.0 to a newer version.  There is a known issue with the tg3 driver, which I've updated to the latest version without problem.  I also used tg3 workaround by disabling NetQueue.  And we do not use of VLAN. Dell technical support says that it is not a hardware problem and thinks it's a matter of layer 2, but does not know where.  Basically, it's an internal problem (meaning strictly on VM8) with vSwitches or vmnic or it's a material gremlin in our Dell R720 box.

  The final recommendation of Dell is to blow the ESXi server and install a clean copy.  It's extremely frustrating and I'm out of ideas.

  Thanks in advance.

  Any luck that you have an IP address that is duplicated on your network?

• Unable to add esxi for appliance Vcenter Server

  Hi all

  I am facing strange problem in my lab environment. I created two esx1 (192.168.111.130) ESX servers and esx2 (192.168.111.131) on VMware workstation that runs on Windows 7.

  I am able to connect to these esxi two servers with help of the Visual c# client.

  Now, I installed device as VM on esx1 VCenter. IP of Vcenter server appliance is 192.168.111.128

  Now, after being part of the server of the device configuration, when I connect to the device via c# client server. I am able to add esx1 but not esx2 host.

  ESX2 isn't to pings from the server to the device.

  ESX1 and esx2 are who answered the other.

  server appliance, and ESX1 esx2 are pings from my window machine on which I have installed VMware Workstation to set up this environment.

  I rebooted twice esx2 and change the IP address as well of 192.168.111.131 to 192.168.111.132, but no luck

  Any help to the above question is very appreciated.

  Thank you

  Vikrant

  Try to reduce the number of vCPU s 2 and increase the RAM to 4 GB

• Behavior of 5.5 very strange Ping ESXI

  So I have a simple two great host * white boxes * lab at home. Both hosts run ESXI 5.5 and are connected to a 16 port switch TP-link GIG using Cat5e.

  Today I implemented a small third host with a single NETWORK Realtek GBE Lan card card. This host is wired in to the same switch as the other hosts on the same subnet and not on any vlan.

  After going through the installation process, I have ip'ed the host and for some reason it failed my gateway, DNS server or all the other guests.

  I ran a Ping of my workstation which is again on the exact same network and I get weird results like that. Have no idea what might be up?

  

  I would say a conflict of ip address, bad, bad port or bad NIC cable.

  In this order

  Linjo

• Error when installing ESXi 5 on 8 workstation

  Hello team,

  I'm dounia. Recently, I completed my training as a VCP on vSphere 5. But when I try to set up a lab in my personal pc using workstation 8, it gives the VT is not enabled on your processor error. I even checked in my physical syustem BIOS and it has been activated. I disabled it and re-enabled again. Then, turn power off and power on the same. But still the same error. I checked the BIOS settings on the operating system prompted but unable to find VT settings on it.

  I am using Windows 7 32-bit operating system

  Intel i3 processor

  I allocated CPU 2 and Core 2, GBB 50 HDD, 2 GB of RAM to the ESXi.

  Please help me!

  Thank you

  Dounia

  Welcome to the VMware communities forum.

  You will need to tweak the virtual machine a little to get VT crossed at the prompt.

  Workstation 8 / Player 4

  Virtualized HV is available for the hardware virtual version 8 virtual machines on the hosts that support Intel VT - x or AMD - V and EPT of IVR. To activate the HV virtualized, select VM-> settings and access the processor settings screen. Check the box 'Virtualiser Intel VT-x/EPT or AMD-V/IVR.' You will see a warning that virtualized HV will make this inconsistent VM with other VMware products. In particular, if this virtual computer is moved to a 5.0 ESXi host, virtualized HV is available without twist additional.

  For more information, please see this document - http://communities.vmware.com/docs/DOC-8970.

• Unable to bridge the physical network in Workstation 7 server

  Hello

  Newbie here. I looked through forums here and can see that some people have had issues trying to fill (VMnet0) virtual machines to physical networks. Not sure if someone came up with a definitive answer, so I'll add my scenerio to the mix.

  I implemented WMware Workstation 7 on a Windows 7 boot camp partition on my iMac and created a network of 3 Win 2 k 3 servers, a Win 2 k 8 Server, a client Win XP and Win 7 for the test. These are connected to a local network called LAN 1 and resident in an area properly.

  I'm trying to set up internet connectivity to network through the first win 2 k 3 server. This server has two network adapters - one on LAN 1 and a bridge to my netgear router. I configured my router to reserve an ip address for the server (192.168.0.5) and manually configure internet/bridge the NIC server with this ip address.

  I can't do a ping to the router (192.168.0.1) the Win 2 K 3 server and also my iMac (192.168.0.4) virtual machine. Can also ping the server of my iMac.

  I'm limiting my internet on the server tests to see if the machine alone can access the network before I try to configure the other machines to access.

  Have seen a few suggestions of uninstall, reinstall the bridge of VMware for the physical network card Protocol, but also to restore the properties by default Virtual Network Editor - I made two suggestions, still unable to connect to the network. Also changed the setting "filled in the ' in the virtual network to the physical network, bridge auto setting map editor.

  In the settings of the server vm, the machine has a list of two network cards - a set jumpered to the physical network, the other to connect to LAN1.

  Interesting thing is that the original image (vmware machine used as a model) is always set to NAT and is able to connect to the Internet.

  Spend about 6 hours to try a variety of ideas and get back on my feet, but I think that everything is as it should.

  Is there a bug in Workstation 7 or y at - it a step that I missed?

  Any ideas would be most appreciated!

  shadowalka wrote:

  Virtual machine:

  IPv4 routing table
  ===========================================================================
  List of the interface
  0x1 ........................... MS TCP Loopback interface
  0 x 10003... 00 0c 29 66 51 df... Intel(r) PRO/1000 MT Network Connection
  0 x 10004... 00 0c 29 66 5 b df... Intel(r) PRO/1000 MT Network Connection #2
  ===========================================================================
  ===========================================================================
  Active routes:
  Network Destination gateway metric Interface subnet mask
  0.0.0.0 0.0.0.0 192.168.0.1 192.168.0.5 10
  0.0.0.0 0.0.0.0 192.168.61.2 192.168.61.2 10
  127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
  192.168.0.0 255.255.255.0 192.168.0.5 192.168.0.5 10
  192.168.0.5 255.255.255.255 127.0.0.1 127.0.0.1 10
  192.168.0.255 255.255.255.255 192.168.0.5 192.168.0.5 10
  192.168.61.0 255.255.255.0 192.168.61.2 192.168.61.2 10
  192.168.61.2 255.255.255.255 127.0.0.1 127.0.0.1 10
  192.168.61.255 255.255.255.255 192.168.61.2 192.168.61.2 10
  224.0.0.0 240.0.0.0 192.168.0.5 192.168.0.5 10
  224.0.0.0 240.0.0.0 192.168.61.2 192.168.61.2 10
  255.255.255.255 255.255.255.255 192.168.0.5 192.168.0.5 1
  255.255.255.255 255.255.255.255 192.168.61.2 192.168.61.2 1
  Default gateway: 192.168.61.2

  
  ===========================================================================

  The W2K3 prompt, which should act as a router must have a default gateway configured to point to the physical gateway you. In case you, it points to itself. It is a dualhomed machine and it must only have set up a default gateway, remove the gefault gateway that manages the connection 192.168.61.0.

  AWo

• Unable to ping guest operating system host

  Hello

  I've set up the vmware workstation as below:

  [Vmware VPC] guest operating system running on windows server 2003 standard edition.

  Host OS running on windows server 2003 standard edition.

  Used IP address are as follows:

  Guest operating system [VPC Vmware]

  IP address: 192.168.15.74

  Subnet mask: 255.255.255.0

  Default gateway: 192.168.15.1

  Host operating system

  IP address: 192.168.15.34

  Subnet mask: 255.255.255.0

  Default gateway: 192.168.15.1

  VMNet1

  IP address: 192.168.15.1

  Subnet mask 255.255.255.0

  The network adapter used to connect the guest OS no [Host].

  I was able to ping between host and guest, but unable to do the reverse. [guest to host]

  The gateway can also be ping of two BONES.

  Firewall of these two OS are off.

  Can we ask or advise me about this problem? Thank you.

  Shacky wrote: I need to connect to a device that is on the live network. I need to connect the guest and the device so that they can talk to each other.

  So why you use VMnet1 Host only and does not connect to the physical LAN?  You should use linked by a bridge.

  Suggest that read 14 chapters (setting up a virtual network) & 15 (advanced virtual networking) in the user of the workstation manual in order to gain a better understanding of the Virtual Network Infrastructure.

• ESXi and HA on Workstation 7.1.1

  I have a couple of ESXi servers installed with a SAN Openfiler. Everything seems to work except HA. Errors of resource poor and unable to communicate with a senior officer of HA. Just about everything trying to make it work. DNS seems very well.

  Just wondering if it was just an impossibility with workstation or if someone managed to activate and test HA on workstation.

  Thank you.

  How much RAM do you have given the ESXi hosts?

  I struggled for a long time because I only gave it 2 GB when she needed 3 GB.

• Ping ESXi 6.0 U2 problems

  Hello

  all devices are on the same subnet.

  I ping the ESXI host and our monitoring server, but the ESXi host and the monitoring server cannot ping each other.

  Firewall on the monitoring server is disabled. The ESXI host has not changed the firewall settings. Restart both does not help.

  What can I do?

  I ended up reinstalling 6.0 Update 2, preserving the data store and now it works.

• Unable to ping my Guest OS-Linux - 5.8 (IP/hostname) of Host-OS: win-7

  Hi all

  I'm using VMWare workstation-8 on my host OS: win - 7 laptop with guest operating system: Linux OEL 5.8. But I can't ping my guest operating system (IP/hostname) of win - 7. I tried with all the bridge, NAT, host only with WMCI (active) options. I'm able to share the Folders (hgfs) between the guest os and host.

  I want to access a few Oracle application of middle ware (running on reviews: Linux os) through Win-7 host operating system.

  Any suggestions would be very helpful.

  Machine: DELL XPS

  SE host: Windows-7 (64-bit)

  Guest operating system: Linux OEL 5.8

  Thank you

  Remy

  I changed to the bridge and enable (check) "State of the repeated physical network connection.

  Now I am able to ping and access Oracle Applications running on the guest operating system of the host operating system.

  Thank you

  Remy

• Nested ESXI 5.1 in Workstation 5.5 9/10 - constantly losing the connection

  Hi all

  I am trying to build my using ESXI VMware Lab nested in VMware workstation. My hardware configuration is:

  CPU-Xeon E5 - 1620 v3, 7 GHz

  Motherboard: Asus P9X79

  First HARD - SSD 128 GB David M5S drive

  Second HDD - Segate 3.5 "2 TB ST2000DM001

  RAM-2x8GB Kingston HyperX 1600 MHz DDR3 Non - ECC CL10

  I installed Windows 7 x 64 SP1 and Windows 8.1x64. On both systems is the same. Workstation works fine for 10-15 minutes. After this date, all (vSphere, SSH for hosted OS) connections are closed. I installed a Linux CentOS 6.5, 5.1 ESXI and ESXI 5.5. Linux CentOS 6.5 are inside of ESXI. All connections are bridged.

  Then when I reconnect by vSphere or SSH connection, everything works well for the next 10 to 15 minutes.

  Below you can see the Logs of Windows (sorry, but I have the Polish version of Windows) and VMware Workstation logs (in this version of the example 9.0.3 1410761) of c:\ProgramData\VMware\hostd\hostd-12.log.

  I enclose also a few screenshots.

  I would like more information, please ask me.

  Any idea what can cause this problem?

  Quote from the journal of VMware workstation (time lost connections):

  2014 02-20 T 10: 03:50.632 + 01:00 [01632 verbose "Default"] has expired between HTTP requests. : Read timeout after about 1205000ms. closing flow TCPStreamWin32 (socket = local TCP(fd=1736) = [: 1]: 8307, peer = [: 1]: 49345)

  2014 02-20 T 10: 03:50.632 + 01:00 [03028 error 'SoapAdapter.HTTPService'] cannot read the request; flow: TCPStreamWin32(not-connected), error: class Vmacore::TimeoutException (operation timed out)

  2014 02-20 T 10: 08:50.387 + 01:00 [02576 verbose "Proxy Req 00006'] new client proxy SSL (TCPStreamWin32 (socket = = 127.0.0.1:443, even local TCP(fd=1752) = 127.0.0.1:49364))))

  2014 02-20 T 10: 08:50.389 + 01:00 [00800 info "Default"] wire attached

  2014 02-20 T 10: 08:50.391 + 01:00 [02576 verbose 'PropertyProvider'] RecordOp REMAP: info, haTask - vim.ServiceInstance.currentTime - 1679830147

  2014 02-20 T 10: 08:50.391 + 01:00 [02576 verbose 'PropertyProvider'] RecordOp REMAP: info, haTask - vim.ServiceInstance.currentTime - 1679830147

  2014 02-20 T 10: 09:20.389 + 01:00 [02528 info "Default"] wire attached

  2014 02-20 T 10: 09:20.389 + 01:00 [01748 info "Default"] wire attached

  2014 02-20 T 10: 10:27.389 + 01:00 [info 04944 "Default"] detached thread

  2014 02-20 T 10: 10:57.388 + 01:00 [02528 info "Default"] detached thread

  2014 02-20 T 10: 13:50.389 + 01:00 [00800 info "Default"] detached thread

  2014 02-20 T 10: 28:50.699 + 01:00 [02576 verbose "Default"] has expired between HTTP requests. : Read timeout after about 1205000ms. closing flow TCPStreamWin32 (socket = local TCP(fd=1820) = [: 1]: 8307, peer = [: 1]: 49365)

  2014 02-20 T 10: 28:50.699 + 01:00 [01632 error 'SoapAdapter.HTTPService'] cannot read the request; flow: TCPStreamWin32(not-connected), error: class Vmacore::TimeoutException (operation timed out)

  2014 02-20 T 10: 32:10.380 + 01:00 [info 03812 "Default"] wire attached

  2014 02-20 T 10: 33:17.381 + 01:00 [01748 info "Default"] detached thread

  2014 02-20 T 10: 33:50.411 + 01:00 [02576 verbose "Proxy Req 00007'] new client proxy SSL (TCPStreamWin32 (socket = = 127.0.0.1:443, even local TCP(fd=928) = 127.0.0.1:49405))))

  2014 02-20 T 10: 33:50.414 + 01:00 [info 01412 "Default"] wire attached

  2014 02-20 T 10: 33:50.414 + 01:00 [02576 verbose 'PropertyProvider'] RecordOp REMAP: info, haTask - vim.ServiceInstance.currentTime - 1679830148

  2014 02-20 T 10: 33:50.416 + 01:00 [02576 verbose 'PropertyProvider'] RecordOp REMAP: info, haTask - vim.ServiceInstance.currentTime - 1679830148

  Windows Journal:

  -

  System

  - Provider of [ Nom] Application error

  - Event ID 1000 [ Qualification]

  Level

  2

  Task 100

  Keywords 0 x 80000000000000

  - TimeCreated [ SystemTime] 2014 02-19 T 21: 55:10.000000000Z

  EventRecordID

  2510

  Channel Application

  Computer COMPUTER

  			Security
  -		EventData

  VMware - vmrc.exe

  9.0.0.28537

  520fabbf

  Msvcr90.dll

  9.0.30729.6161

  4dace5b9

  40000015

  0005beae

  1370

  01cf2db7c9ad3847

  C:\Program Files (x 86) Remote Console Plug-ins 5.5\Internet Explorer\vmware \Common Files\VMware\VMware - vmrc.exe

  C:\Windows\WinSxS\x86_microsoft. VC90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\MSVCR90.dll

  7ffed6bb-99B0-11E3-90f5-005056C00008

  Hello

  I found what caused this problem. In my lab environment, I have the WRT54G-TM with DD - WRT router onboard. It has been configured in Client Bridge mode. He has some problem with mains supply. I disconnected the router from my computer and plugged directly on the wireless NIC card. He helped with the interruption of network problems, but there were a lot of issues with routing etc. I bought new router TP-Link TL-WR740n v4.27 and connect as a client mode on my primary wireless router. After that everything works fine.

  Once again thank you for trying to help.

  I hope this helps someone simillar questions.

  Thank you!