Solved

Can't access share sometimes and some strange performance issues

Posted on 2014-11-27
8
101 Views
Last Modified: 2015-09-11
I'm getting error 0x80070043 "The network name cannot be found" when accessing \\dc01 (the root), but sometimes can (and sometimes not) access shares via \\dc01\share.

When I get that error I also didn't get the network drive on hosted that server set via Group Policy, it fails with this error:

The user 'W:' preference item in the 'GPO Name' Group Policy Object did not apply because it failed with error code '0x80070008 Not enough storage is available to process this command.' This error was suppressed.


The client is Windows Server 2012 R2 Remote Desktop and the DC server is 2012 R2 too, both on a - the same - VMware ESX host.

Then I log off and on, and no issues most of the time. Because also roaming profiles are located on the DC, also strange behaviour regarding saving and/or opening files, Outlook stationary, template files like normal.dotx and so on. Think all related to the 'network problems' that occur.

Maybe related and maybe where the problem is: When I have this issue and sometimes when I don't (the network drive is added fine) I have some strange performance issues on share/network drive: Word, Excel and PDF files opens very slowly. Offices says "Contacting \\dc01\share..." for 20-30 sec. Txt files don't have that problem.

Any tips how to troubleshoot?
0
Comment
Question by:traction
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 3
8 Comments
 
LVL 120
ID: 40468615
Make sure VMware Tools is installed.

Are you using the VMXNET3 network interface, if not switch to it, and replace the E1000.
0
 
LVL 62

Expert Comment

by:gheist
ID: 40468801
With full disk no system will run fast. Also disk is now badly fragmented, which will cause lots of pain in virtual machine in future - very slow chkdsk, very slow diks access etc, even you manage to clean it up
0
 

Author Comment

by:traction
ID: 40468850
@Andrew; we will change this today as we also see that recommendation from VMWare, thanks and we'll keep you posted.

@gheist: plenty of disk space available, it's just the message complaining about the lack of disk space, we are very sure it's a network related issue, see previous answer.
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
LVL 62

Expert Comment

by:gheist
ID: 40468888
Can we guess host build number somehow?
Can you confirm you are using vmxnet3?
0
 

Author Comment

by:traction
ID: 40468898
We wil change to VMXNET3 later today when systems can be shutdown.

What do you want to know?ESX build?

ESXi 5.5.0
GA      2013-09-22      1331820
0
 
LVL 62

Expert Comment

by:gheist
ID: 40468914
Heard of security patches? 5.5 Update 2a you know...
0
 

Author Comment

by:traction
ID: 40470062
Still same problem after changing to VMXNET3 network interface.
Also disabled antivirus, just to be sure.

The strange part is that it only occur between remote desktop server and DC (where shares and profiles are located). After a restart, or sometimes also when most of the users logout, the problem disappears for a while. When a user logs in than the profile, network shares (through GPO) are loaded.

After switching to VMXNET3, the virtual servers restarted, the problem wasn't there, but also not all users logged in. After this night when users logged in in the early morning the problem is still there.

Any idea about next steps?
0
 
LVL 62

Accepted Solution

by:
gheist earned 500 total points
ID: 40470175
Try to drill through some guide off the internet. Problem looks outside vmware.
To my memory 5.5 as you have had problems with TCP communication between machines on same host. It is well reflected in network counters on machines.
Upgrade to 5.5U2 (which includes new vm tools too) to see if it goes away.
Or first try moving TS off the DC host?
0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

The following article is comprised of the pearls we have garnered deploying virtualization solutions since Virtual Server 2005 and subsequent 2008 RTM+ Hyper-V in standalone and clustered environments.
If we need to check who deleted a Virtual Machine from our vCenter. Looking this task in logs can be painful and spend lot of time, so the best way to check this is in the vCenter DB. Just connect to vCenter DB(default DB should be VCDB and using…
In this Micro Tutorial viewers will learn how to restore single file or folder from Bare Metal backup image of their system. Tutorial shows how to restore files and folders from system backup. Often it is not needed to restore entire system when onl…
This video shows you how to use a vSphere client to connect to your ESX host as the root user. Demonstrates the basic connection of bypassing certification set up. Demonstrates how to access the traditional view to begin managing your virtual mac…

752 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question