lesnotours.blogg.se

The reason for the long log in time is that when you have the router and/or public DNS set on workstations, these DNS servers do not know anything about internal DNS records that workstations will look for in an Active Directory domain - so the workstation is probably looking for an internal DNS record at login time and if it is querying a public DNS server or the router, it will sit there waiting for a response - and while it sits there, you'll get the whirly wheel during login. Otherwise, besides checking DNS configuration on the two problem clients, what else should we be checking? With seven PCs logging in and only two of them having problems, can this really be a server-side problem? If so, please elaborate. I will have to look and see how this one and the other one with a similar issue are configured. Most of the time we set the DNS back to dynamic but sometimes we have the server as primary, then the router, then the public DNS servers for their ISP (in this case Comcast). We have to set the server to be DNS in order to join it to the domain.

I will have to look and see how client-side DNS is configured. The one we've been talking about here is slow to login regardless of what domain profile is used. Only two of them have problems with a long login. This particular domain has seven workstations logging into it. Being a domain controller though DNS is configured. DHCP is not enabled the router hands out IPs. Everyone has a specific machine assigned at a desk or in an office and they really only have to use another machine if we happen to be working on theirs.

So we logged her onto the domain, changed her desktop wallpaper, mapped her drive, redirected My Documents, My Pictures, My Videos, and Downloads to her server area.all of which I consider "building a domain profile." Regarding Justin's question, we are not using roaming profiles in any of customer locations. The domain user did exist already but somehow the user had never actually logged onto the domain until the local profile became corrupted. First to reply to Todd, you're pretty close. Hello all and thank you for your replies.