7 replies
by john_doe
by timwalsh
Where does it appear to hang? Does the log-on screen (greyed out once you hit enter) stay on longer, or does the "Applying you personal settings" message stay on longer?
A couple things to try to possibly determine where the problem is:
Disconnect the WS from the router and log on to the local computer. This might help determine if there is a problem with software installation. Have you loaded any other software yet? Are there a large number of applications that start automatically?Reconnect the WS to the router and again log on to the local computer (vs. the domain). Do you see the same behavior you saw when you were disconnected from the router? This might help you determine if router configuration is causing issues.
Disconnect the router from the Internet and log-on to the domain. What behavior do you see? This might help determine if the domain configuration is correct or if somehting from you ISP might be causing problems.
Are you using DHCP from the routeror from your server? Are you running your own DNS or using DNS from your ISP? Does your AD domain have a ".com" or a ".local" domain extension?
by timwalsh
I suspect the problem is a combination of DNS and your Domain name.
Since you have set up a ".com" domain, do you have this domain name register through your ISP with InterNIC? If you just created a domain name and gave it a ".com" extension, that is the majority of your problem.
In Win2K, the domain log-on/authentication process does not use TCP/IP (and thus doesn't reference DNS). Therefore you aren't seeing any log-on error messages. However, you computer then attempts to register its IP address with the DNS server hosting your DNS zone (which in Win2K is usually named the same as your AD domain). Since your WS can't find a DNS server locally doe the DNS zone "yourname.com", it goes to your ISP's DNS server looking for a DNS zone with that name.
If my assumption is correct (from the first question above), there is no DNS zone on your ISP's DNS server for "yourname.com". A search is then run across the rest of the Internet looking for a server hosting a DNS zone withthe name "yourname.com" (which either doesn't exist or does exist but doesn't recognize your attampt to register and thus ignores it. I think that is what is causing your computer to take so long to get to the desktop.
Since probably have a private AD domain, you can't give it a public Internet domain extension.
(continued)
by timwalsh
I would be willing to bet if you check the DNS log in Event Viewer on your server, you will have numerous DNS errors alluding to "cannot find DNS zone "yourname.com."
This is actually probably a fairly common mistake. I haven't seen a lot of written documentation covering setting up a private AD domain, because not very many people will go to that trouble. To have a private AD domainand have it operate properly, you need to do several things:
1. Host your DNS locally and host DHCP on your server. (The DHCP server on your router will only pass information related to your ISP's DNS server and gateway.) Setup DNS to refer only to local resources and set it up as a forwarder to your ISP's DNS server. By doing this, all DNS queries relating to local resources will be answered by your DNS server. Only queries relating to resources outside of your domain (i.e. the Internet) will be forwarded to your ISP.
2. Give your domain a ".local" extension (i.e. yourname.local). This notifies your DNS server that this is only a LOCAL DNS domain and queries related to it are not to be sent outside the local domain. I have only seen this tidbit documented in on reference. Most references on setting up AD domains assume you are a business setting up a domain accessible from the Internet. Unfortunately, you need to rebuild your AD domain to accomplish this.
How did I figure all this out? Can you say "Been there, done that!"
Hope this helps solve your quandry.
by john_doe
by john_doe
by john_doe
This discussion is closed to new replies.
Trending Software posts
Sort by Trending