We help IT Professionals succeed at work.

Network Error Windows Cannot Access Message when connecting to redirected Desktop

JohnMan777
JohnMan777 asked
on
My GP sets users so their desktop is on the server. Two users with new Windows 7 PCs get the message above on a cold boot or restart.  If they log out and back in (not restart), it works fine.  

If they reboot or cold boot and wait at the logon screen for 2 minutes, it works fine.
If they quickly log in they get the error message.  

Windows Cannot Access: \\myserver.mycompany.local\users$\johndoe\Desktop

My theory is these new computers boot to the desktop so fast, the network hasn't had a chance to get ready.

All help is appreciated.

Error message
Comment
Watch Question

CERTIFIED EXPERT
Distinguished Expert 2019

Commented:
Hi.

Try activating this policy (locally on those two), afterwards fire the command gpupdate /force /target:computer at those 2 and restart and test.
Policy: ComputerConfiguration/AdmTemplates/System/Logon/AlwaysWaitForTheNetwork

Author

Commented:
McKnife,

Thank you for your suggestion.  This has not solved the issue.  Any other suggestions are appreciated.
CERTIFIED EXPERT
Distinguished Expert 2019

Commented:
Really? I'm astounded, it ought to. You did really gpupdate /force /target:computername (from an elevated command prompt) and restarted not before that succeeded?

Author

Commented:
I thought it would do the trick too.  

I logged in as myself (domain admin creds)
I did the force, but didn't put in the "/target:computername"

If you feel that would matter, I'll do it again.  Without /target it does both user and computer (so say the docs).
CERTIFIED EXPERT
Distinguished Expert 2019

Commented:
Yes, it does matter. If you just do gpupdate /force, it does NOT do both because of UAC. Only if the command prompt is elevated OR UAC is off, it will do both.

Author

Commented:
I've redone it logging is as me, running command.exe as administrator and using the /computer switch. Unfortunately it's doing the same thing when I log in quickly.
CERTIFIED EXPERT
Distinguished Expert 2019
Commented:
Ok, that was needed just to make sure. Tell you what, we had the same lately and all we could do against was exchange the NIC to some model that initialized quicker than the old one - that worked. Took a PCI Express intel GBit NIC.

Author

Commented:
I will have new NICs in 2 weeks to try. If you are available for paid telephone consulting on other issues, please contact me at john@jcaspary.com or 702.319.1284.  It seems like you know your stuff! Thank you.

Explore More ContentExplore courses, solutions, and other research materials related to this topic.