My ISP provides the DNS/IP's but I setup a router using one of IP's provided by the ISP and their DNS, behind the router I have 15 XP workstations and a windows 2000 server ,Xeon 2.6 , 2GB RAM, using DHCP, the router assigns the IP's to the workstations and the server, every workstation takes over 15 minutes to boot , "applying user settings" takes too long. What Am I doing wrong ?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
slow boot xp workstation to windows 2000 server with AD 1
- Thread starter tomas47
- Start date
the problem is the workstations are using the ISP DNS. I take it they are all part of a 2k domain. Is the Server the AD DC as well ? you would need to configure the workstations to use your own DNS server(probably your 2k server is already a DNS server) Then configure your DNS to forward to the ISP DNS.
-
1
- #3
wconsulting
IS-IT--Management
I wrote this answer on another tech site and I'd like more feed back from users on this issue...
"I too had beaten my head against the wall with this XP slow logon issue. I tried all of the fixes I could find online....from the asynchronous loading of networking fixes ( ) to all of the DNS forwarding tricks I could find ( ). I was CONVINCED that it was a DNS issue, but I think most LAN IT techs get a little weak when it comes to DNS (I know I do). Anyway, I'd be curious to know what your server's fully qualified domain name is. Here is what I've found. server.companyname.com is what my server names were. Without DNS tweaking that I haven't successfully found/done, I finally got brave and ran dcpromo to "demote" my active directory server to a stand alone server. Once this was done I ran dcpromo again to recreate the active directory server only THIS TIME NAMING IT SERVER.COMPANYNAME.LOCAL The .local part is THE difference. I don't know of any other way of renaming a Windows 2000 active directory server name. Now keep in mind that this is a drastic change and all of your users accounts/passwords etc will be lost and have to be recreated. But all of my XP machines logon on in an instant now. If there is an easier way to "fix" this I'm all ears, but I haven't found a "fix" anywhere else online. Let me know if this helps."
Kevin
"I too had beaten my head against the wall with this XP slow logon issue. I tried all of the fixes I could find online....from the asynchronous loading of networking fixes ( ) to all of the DNS forwarding tricks I could find ( ). I was CONVINCED that it was a DNS issue, but I think most LAN IT techs get a little weak when it comes to DNS (I know I do). Anyway, I'd be curious to know what your server's fully qualified domain name is. Here is what I've found. server.companyname.com is what my server names were. Without DNS tweaking that I haven't successfully found/done, I finally got brave and ran dcpromo to "demote" my active directory server to a stand alone server. Once this was done I ran dcpromo again to recreate the active directory server only THIS TIME NAMING IT SERVER.COMPANYNAME.LOCAL The .local part is THE difference. I don't know of any other way of renaming a Windows 2000 active directory server name. Now keep in mind that this is a drastic change and all of your users accounts/passwords etc will be lost and have to be recreated. But all of my XP machines logon on in an instant now. If there is an easier way to "fix" this I'm all ears, but I haven't found a "fix" anywhere else online. Let me know if this helps."
Kevin
- Thread starter
- #4
- Thread starter
- #5
bofhrevenge2
MIS
tomas47 i take it you are running active directory if so it sounds like moorethan is correct as regards the DNS issue.
If your Domain Controller is running DNS (it more than likely will be if it's your only DC) then your client PC's should point to this for DNS name resolution, the DNS server will then forward any requests that it doesn't know about to your ISP (as long as it isn't configured as a root server).
Keep in mind here that 2000/XP stations use DNS to locate resources if you point your stations to your ISP then your stations will ask there for the IP of your servers. As the ISP doesn't know the answer the station stalles for a while before eventually resorting to sending a broadcast message.
"Horsey to king bish three
If your Domain Controller is running DNS (it more than likely will be if it's your only DC) then your client PC's should point to this for DNS name resolution, the DNS server will then forward any requests that it doesn't know about to your ISP (as long as it isn't configured as a root server).
Keep in mind here that 2000/XP stations use DNS to locate resources if you point your stations to your ISP then your stations will ask there for the IP of your servers. As the ISP doesn't know the answer the station stalles for a while before eventually resorting to sending a broadcast message.
"Horsey to king bish three
bofhrevenge2
MIS
Just in case you decide that this is the problem take a look at this FAQ.
faq96-3017
"Horsey to king bish three
faq96-3017
"Horsey to king bish three
- Status
Similar threads
- Locked
- Question
- Locked
- Question
