This problem just started recently. I have a number of VMs (2008 R2) on a 2012 Hyper-V host but not all are effected in the same manner. The VMs are identical and no changes were made to either the VM or Hyper-V host.

I am unable to reach the Cluster Shared Volume on a few VMs. I am able to ping the Hyper-V host by name and IP. But I cannot connect to the share via name, IP, or FQDN. I can reach other network shares okay, but not shares on the Hyper-V host.

Things that I have checked/tried - DNS does not seem to be an issue. I can ping by name and nslookup resolves correctly - 6to4 Adapter has been disabled - Windows firewall turned off for troubleshooting purposes - NETBIOS over TCP.IP is enabled - workstation/server/computer browser service is running. (Computer browser service is not running on the VMs that work) - Accessing the CSV from other servers (outside of the Hyper-V host) works just fine - Reboot Hyper-V Host and Reboot VM - File and print sharing service is enabled on both VM and Hyper-V host

Error: File and print sharing resource is online but isn't responding to connection attempts. The remote computer isn't responding to connections on port 445, possibly due to firewall or security policy settings, or because it might be temporarily unavailable. Windows couldn't find any problems with the firewall on your computer.

I might be missing something simple, but does anyone have a suggestion on something to try/check?

UPDATE: There was an unannounced change to the Enterprise Firewall. Which explains why I never saw anything in the Windows Firewall log. Not being able to connect over port 445 was the tell tale sign. I changed the IP of a working VM to a non working VM IP and noticed that I could no longer connect.

  • 1
    I'm not understanding your question. A CSV is not a shared folder, it is a shared volume for use by the cluster nodes. The "Shared" in the name refers to the volume being "shared" amongst the cluster nodes. Why are you trying to access the CSV from the virtual machines? – joeqwerty Nov 5 '13 at 23:50
  • Let me clarify. I cannot reach either the CSV or any shared folders on the Hyper-V host. The reason a VM would need to access the CSV is because we hold our software .iso on there. – Tho H. Le Nov 5 '13 at 23:56
  • On the working VMs I can telnet to the Hyper-V host over port 445. From the non-working VMs I cannot telnet to that port. Hyper-V host is listening on that port and the firewalls have been turned off. – Tho H. Le Nov 5 '13 at 23:58
  • 1
    Not for nothing but you can connect the VM DVD drive to the ISO file from the VM settings rather than having the VM access the ISO file over the network. – joeqwerty Nov 6 '13 at 0:09
  • Yeah. I'm not being blocked by this problem right now. But I am concerned as to how this got started, and if there will be additional problems down the road. Not being able to telnet over port 445 seems to be the biggest clue. Firewall and AV have both been turned off, and the Hyper-V Host is listening on 445. – Tho H. Le Nov 6 '13 at 17:38

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.