\\domain.local slow to load

[mrbios]

Interesting issue here...

Typing in \\domain.local takes a good 10-20 seconds to show anything in the window, but typing in \\domain.local\folder\ always comes up instantly, going back from the sub folder to \\domain.local also takes a while.

Most likely in connection to this we're getting some PCs with quite slow group policy loading times when you first turn them on.

No errors in domain controllers event logs stick out at all, domain controllers are all operating normally when logged in to, general network operation apart from group policy loading times and applying computer settings when a PC is turned on are all fine.

Also takes a long time to produce rsop data but doesn't bring up any errors.

Any ideas?

 

[mrbios]

i can ping it fine but it does take 2-3 seconds before pinging starts, not sure if that's actually a problem. Also no DNS errors to note, nor has the configuration been changed at all in months, and everything else resolves fine and apart from PCs taking a long time to load policies there are no other issues noticed by users on the network during normal use.

and there's probably 5-10 GPs per client maximum

 

[mrbios]

i suggest you go to work over the weekend, drink a bottle of vodka, change your admin password (while drunk) then sleep it off...

in the morning you will not be able to remember the password and your companys IT systems will be much safer

Thank you edscdk, this is the best post I've ever seen on ocuk

Anyway back to the topic at hand.... Seems the slow loading of \\domain.local and the delay in pinging it is only an issue on one of my 9 DCs, I've run the AD replication status tool and been given no errors, i've done dcdiag etc and there's no errors, I've rebooted the server (you never know eh?) and still no joy.

I feel I'm getting closer to finding out the problem with this bit now, although I was hoping the slow loading of domain.local was linked to the issue with PCs taking some time to load policies in the morning, but that doesn't appear to be the case now as the DC having the problem isn't the DC those PCs see.

How many DC's in the environment? 9
What O/S version and what domain/functional level? 2008R2 for both
Does it happen to all machines within the same site? Yes
Are all the DC's in the same site? No
Does it happen when machines connect to one or other DC? (Cmd --> type "SET") No

 

[mrbios]

Do a dcdiag /v on it

I did dcdiag /c /v and the only error to note was this one:

      Starting test: VerifyEnterpriseReferences

         The following problems were found while verifying various important DN

         references.  Note, that  these problems can be reported because of

         latency in replication.  So follow up to resolve the following

         problems, only if the same problem is reported on all DCs for a given

         domain or if  the problem persists after replication has had

         reasonable time to replicate changes. 
            [1] Problem: Missing Expected Value

             Base Object: CN=PDC1,OU=Domain Controllers,DC=Archway,DC=local

             Base Object Description: "DC Account Object"

             Value Object Attribute Name: msDFSR-ComputerReferenceBL

             Value Object Description: "SYSVOL FRS Member Object"

             Recommended Action: See Knowledge Base Article: Q312862

             
            LDAP Error 0x5e (94) - No result present in message. 
         ......................... ICT_DC failed test

         VerifyEnterpriseReferences

I've checked that out and i don't appear to have any attribute attached to that machine account starting with msDFSR, is this because i haven't migrated FRS to DFSR?

EDIT: Whether it's related or not I can't believe i've never migrated SYSVOL from FRS to DFSR.... just been checking and i've never done it, guess i should get cracking on that, is it safe to do during normal hours or is it best waiting for minimum users on the system?

 

[mrbios]

When you said there was a delay before it started pinging, was that by IP address, or hostname?

Is there any improvement if you do 'ipconfig /flushdns' from a client and then try?

The delay only occours when pinging the "domain.local". Pinging the DC it's resolving either by hostname or IP resolves instantly.

 

[mrbios]

Really ****ed off with this problem, i've fixed it now, and let me just say it turned out to be a hell of a lot simpler than a network problem.

Want to know what it was? Of course you do..........The apple mobile device and bonjour services. Soon as i stop either one of those (only seems to happen when they're both running) the problem goes away, unbelievable! That would explain why it never had a set pattern to where this problem occoured, it was only happening to people who use ipads :/

 

[mrbios]

Phew! Isn't apple such a pain ?

Corrected that for you

Another apple problem for the ever growing list today....we use uniflow print management and had just installed mobile print which also has a module for apples air print. Anyway long story short our printers are on a different vlan to the wireless and airprint needs to be on the same subnet as the uniflow server else you cant see the printers in airprint .... More crap from the bonjour service apparently :/ yay

 

[mrbios]

Don't forget .. Apple products just work... as said above.. unless they are in a complicated network.

.... and no apple administrators.

Must admit though, i don't even like them outside of a network