Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

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.

share|improve this question
add comment

2 Answers

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.

share|improve this answer
    
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 8 '10 at 15:35
    
Updated integration components installed on the guest? Host hardware on the compatibility list? –  Chris S Dec 8 '10 at 15:48
    
It is ML 350 G5 (HP) integration disk is installed, all components are checked –  mn. Dec 8 '10 at 15:55
    
Do any of your VMs have Legacy Network Interfaces? –  Chris S Dec 8 '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 8 '10 at 16:21
show 2 more comments

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.

share|improve this answer
    
1) I use ip addresses 2) network discovery is enabled, but status is "Custom" –  mn. Dec 8 '10 at 15:48
    
Does the problem go away when the Firewall is completely disabled? –  Somantra Dec 8 '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 8 '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? –  Somantra Dec 8 '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 8 '10 at 18:10
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.