W2K8 R2 SP1: Can not access NAS due to error 0x80070035
-
Tuesday, November 20, 2012 10:28 AM
Hi,
very strange problem here. We aren't able to connect to several NAS on the same subnet from our virtual Windows Server 2008 R2 SP1 machines which are running on Hyper-V 2008 R2 Cluster. We always get error message 0x80070035 network path not found.
When we try to connect to NAS from physical Windows Server 2008 R2 SP1 machine it works like a charm. It seems to be that only our hyper-v machines are having this problem.
After some searching on the web we found a hotfix but it is already included to SP1 and won't help here. All other suggestions on the web like enabling Computer Browser service or changing NetBios Settings didn't help yet. We also checked firewall settings on both virtual and physical machines and found no differences.
We are using SCFEP 2012 on virtual and physical machines and Windows Server 2008 R2 SP1 Datacenter as OS.
Any suggestions would be very appreciated!
Thank you very much,
André
All Replies
-
Wednesday, November 21, 2012 10:41 AM
Hi,
Could you ping the NAS from the hyper-V machine? Could the physical server which holds the hyper-V machine access the NAS?
Best Regards
Scott Xie
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
-
Wednesday, November 21, 2012 10:44 AM
Hi Scott,
yes I am able to ping the NAS from both physical and virtual machines. I am also able to access the NAS shares from the Hyper-V Cluster Nodes which a holding the VMs.
Regards,
André
-
Saturday, November 24, 2012 6:06 AM
Hi André,
Though the OS is a little different, please refer to the following article:
http://support.microsoft.com/kb/958285
I suggest you can try the workaround in the article to disable IPv6 feature on the virtual machines.
http://support.microsoft.com/kb/929852
Best Regards
Scott Xie
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
-
Monday, November 26, 2012 10:55 AM
Hi Scott,
I followed your article regarding the hotfix. It came out that the hotfix is already included to SP1 of Windows Server 2008 R2.
I tried disabling IPv6 on one of the machines with no success. Also tried to change the virtual network adapter to legacy network adapter in hyper-v. The error keeps the same.
Best Regards,
André
-
Monday, November 26, 2012 11:11 AM
Are your hyper-V machines running Windows 2008 R2 SP1?
Regards
Satish
-
Monday, November 26, 2012 11:13 AM
Hi Satish,
exactly. Windows Server 2008 R2 SP1 Datacenter.
Regards,
André
-
Wednesday, December 05, 2012 9:47 AM
Hi André,
To further troubleshoot the issue, I suggest that you can capture network traces on the virtual machine, physical machine which holds the virtual machine and the file server sides when you reproduce the issue.
Also I suggest you can create a support case to Microsoft since there are many logs which need to be analyzed.
Best Regards
Scott Xie
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
-
Monday, December 10, 2012 4:06 PM
Hi Scott,
thank you very much. Finally we figured out that SMB Signing is causing the problem. We changed that with gpo and after restart of the VM it is working like a charm.
Best Regards,
André
- Marked As Answer by André Loske Monday, December 10, 2012 4:07 PM
.png)
