0x80004005 unspecified error / 0x80070043 the network name cannot be found

Hello,

On one of my servers (virtualized on vsphere 5.0 + windows 2008 R2 + Exchange 2010) , when trying to access a remote share (\\srver\share), I am getting the following messages :

0x80004005 unspecified error
0x80070043 the network name cannot be found

Other servers (same OS) are not affected by this message

What we changed recently : As far as I know, an external consultant activated a network policy on another server to secure the wireless connections
2014-08-26-12h14-21.jpg
What I already tried to do :
flushdns
activate network discovery on the connection.

Thanks for your help
hdoumAsked:
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.

hdoumAuthor Commented:
Hi
I read this article : on MS technet and I discovered that there is something weird in the registry under "HKLM>System>CurrentControlSet>Control>NetworkProv ider>Order" :
the value is "PDVFSNP,RDPNP,LanmanWorkstationtdriv怛鄁"
Do you this could cause the problem ? How should I modify the key ?
Thanks
0
hdoumAuthor Commented:
OK I when I enter \\SERVER\SHARE I get the error message
If I enter \\SERVER\SHARE\ with a backslash at the end, the share opens !

I created a backup of the registry and replace the old value for "NetworkProvider>Order" and for NetworkProvider>HWOrder" (they both had the same value)

Now the value is "PDVFSNP,RDPNP,LanmanWorkstation"

Now it's ok. But I am still wondering how this registry key could have been modified with chinese characters ??? Malware ? I am scanning the server with TrendMicro WFBS and we'll see the result.
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
hdoumAuthor Commented:
Still looking for the root cause : how could the registry key be modified ?
0
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
Windows Server 2008

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.