0

I have got strange problem with windows 2008 guest. Network for this host is configured as external. I am able to ping FROM this host and I am unable to ping to THIS host. When I am resetting connection at this guest system from network connections I can ping this host for few seconds. Where is the problem? This machine uses static address.

mn.
  • 115
  • 6

2 Answers2

0

The same network configuration requirements of a real machine apply to virtual machines. Do you have a default gateway configured? Perhaps you could elaborate on exactly how your VM, host, etc have their NICs configured.

Chris S
  • 77,337
  • 11
  • 120
  • 212
  • On hyper v server runs three virtual machines. All guest except this one works perfect. The problematic host is able to be pinged only for a while when network connection is resetting (on this problematic guest). All ip configration seems to be ok – mn. Dec 08 '10 at 15:35
  • Updated integration components installed on the guest? Host hardware on the [compatibility list](http://www.windowsservercatalog.com/)? – Chris S Dec 08 '10 at 15:48
  • It is ML 350 G5 (HP) integration disk is installed, all components are checked – mn. Dec 08 '10 at 15:55
  • Do any of your VMs have Legacy Network Interfaces? – Chris S Dec 08 '10 at 15:57
  • All my VMs using normal network adapters. I tries on problematic machine using legacy but there was the same problem - I was able to ping other machines and other machine were able to ping problematic machine only for few seconds when connection was resetting – mn. Dec 08 '10 at 16:21
  • You've got me, sounds like an issue with the OS on the guest machine. Anything in the event log? Firewall? Error messages? – Chris S Dec 08 '10 at 16:46
  • First I still didn't resolve that issue (5 houres). Firewall is disabled, in event log there is no information (I checked on host ang guest). I tried to reconnect to other built in server Ethernet port but there is same issue - can ping other machines but other machines cant ping me and cant access my services (for 10-15 sec can when I am resetting network card) – mn. Dec 08 '10 at 17:09
0

Are you pinging machine name and/or IP address?

Is Network Discovery enabled? By default it is not enabled. I would say this is the most likely root cause.

Also, look at this post: Enable Ping in Windows Server Firewall?

Based on: http://windows.microsoft.com/en-US/windows-vista/What-is-network-discovery , I would say that the custom status may warrant further investigation.

Custom

This is a mixed state in which some settings related to network discovery are enabled, but not all of them. For example, network discovery could be turned on, but you or your system administrator might have disabled a firewall exception that affects network discovery.

Network discovery requires that the dnscache, fdrespub, ssdpsrv, and upnphost services are started, that the Windows Firewall exception for network discovery is enabled, and that other firewalls are not interfering with network discovery. If some but not all of these are true, the network discovery state will be shown as Custom.

Community
  • 1
unhappyCrackers1
  • 977
  • 1
  • 6
  • 18
  • 1) I use ip addresses 2) network discovery is enabled, but status is "Custom" – mn. Dec 08 '10 at 15:48
  • Does the problem go away when the Firewall is completely disabled? – unhappyCrackers1 Dec 08 '10 at 16:04
  • I completely disabled firewall on all machines and clients in my network. Pinging works only when I am resetting connection on problematic virtual machine – mn. Dec 08 '10 at 16:15
  • You probably should think about doing some packet sniffing and some other network diagnostics to narrow the point of failure. Does the machine receive the ICMP traffic? Does it send a reply? – unhappyCrackers1 Dec 08 '10 at 18:04
  • when I scan network gateway is visible 10.10.9.1, it is gateway to problematic guest 10.10.9.3 – mn. Dec 08 '10 at 18:10