Can't access share sometimes and some strange performance issues

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?
Traction ITSupport TeamAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Make sure VMware Tools is installed.

Are you using the VMXNET3 network interface, if not switch to it, and replace the E1000.
0
gheistCommented:
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
Traction ITSupport TeamAuthor Commented:
@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
The Ultimate Tool Kit for Technolgy Solution Provi

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy for valuable how-to assets including sample agreements, checklists, flowcharts, and more!

gheistCommented:
Can we guess host build number somehow?
Can you confirm you are using vmxnet3?
0
Traction ITSupport TeamAuthor Commented:
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
gheistCommented:
Heard of security patches? 5.5 Update 2a you know...
0
Traction ITSupport TeamAuthor Commented:
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
gheistCommented:
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

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Server OS

From novice to tech pro — start learning today.