Jump to content

Recommended Posts

Posted

Hi!

 

We have a sudden problem, literally just started happening this morning, where two windows machines running 8.1 aren't picking up the mapped shares or the printers. Nothing has been changed before the issue began. Any ideas??? It can't be the users because it all works fine when they log on to the windows 7 machines.

 

Manually mapping drives works fine.

Posted

Is the Group Policy Client service running ok on them?

What does a gpresult from the command prompt show?

 

Do you have "Always wait for the network at logon" set in Group Policy?

 

Have you tried doing a gpupdate /force and seeing if that fixes it?

Posted

If DNS isn't working correctly - server or client, then you'll find your computer won't be able to ping or of course resolve your server FQDN for example.

 

Can you ping yourserver.domain.pri for example from a Windows 8 command window? And does it resolve to an IP?

Posted
If DNS isn't working correctly - server or client, then you'll find your computer won't be able to ping or of course resolve your server FQDN for example.

 

Can you ping yourserver.domain.pri for example from a Windows 8 command window? And does it resolve to an IP?

 

Yeah I can ping it that's why it's so weird...

Posted

So are you mapping drives as:

 

\\servername\share or

 

\\servername.domain.pri\share (the FQDN is generally recommended)

 

Are you using GPP or scripts?

Posted
So are you mapping drives as:

 

\\servername\share or

 

\\servername.domain.pri\share (the FQDN is generally recommended)

 

Are you using GPP or scripts?

 

There's a problem connecting to the printers too which makes me think it's not the GPO setting...

Posted
The frustrating thing is there have been no problems literally until this morning....

 

I'd check the event logs for things like Windows Updates or DNS/GPO related errors on the local device. It's the only way we can start to isolate the issue :)

Posted

Yes - it looks as if you could be logging in using cached credentials, before the computer gets an IP.

 

There is a GPO for this, so the computer is forced to wait.

 

Alternatively if you leave the computer on (at the login screen) for more than a minute, it'll probably map as intended once you login.

  • Thanks 1
Posted
Yes - it looks as if you could be logging in using cached credentials, before the computer gets an IP.

 

There is a GPO for this, so the computer is forced to wait.

 

Alternatively if you leave the computer on (at the login screen) for more than a minute, it'll probably map as intended once you login.

 

Ah right. Where is the gpo to force waiting? I'll give this a try Cheers!

Posted
And the Windows 8 computer objects are definitely under this policy? Have you tried running gpupdate /force ?

 

Definitely under these and gpupdate /force brings back the following:

 

"The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition...."

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...