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 wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
clues my dns is messed up ?
- Thread starter mitzysman
- Start date
- Thread starter
- #3
well sometimes servers won't logon (get stuck at "Loading your personal setting" and I think dns could be the culprit at least my antivirus vendor is asking me to check it.
also when I add or change an user account at another sites AD server the PDCe doesn't always reflect the change for several hours, which doens't seem right to me I thought they should replicate within a few minutes.
also when I add or change an user account at another sites AD server the PDCe doesn't always reflect the change for several hours, which doens't seem right to me I thought they should replicate within a few minutes.
mlichstein
MIS
If you think you have DNS problems, you should run netdiag /v on your DNS server(s).
- Thread starter
- #5
mlichstein
MIS
If you have multiple DCs, it wouldn't be a bad idea to run it on all of them.
You may also want to run dcdiag /v on the servers, too.
You may also want to run dcdiag /v on the servers, too.
From the PC/Server having problems open a command prompt and type nslookup and see where your DNS is pointing. If you get "unknown" or you do not return the correct value you have DNS problems. Nslookup is the tool to diagnose any DNS problems. Make sure you have Reverse Lookup Zones configured which will solve alot of DNS issues with name resolution. Common problem is that the "servername" can resolve to an ip but the ip cannot resolve the "servername". DC's DNS should point to themselves.
This is somewhere to start.
This is somewhere to start.
sebjenkins
Technical User
For some reason, from yesterday I am no longer able to connect to any on my Windows 2000 servers using their name through the Start->Run menu.
ie. type \\wvip_fileserver\ in the Run box and click O.K. generates an error: \\wvip_fileserver\ 'the network name cannot be found'
At this point I would expect a new window to open displaying available shares and print queues. This has always worked o.k. until now.
This is also true of my other Windows 2000 servers on this site.
However, I am to connect to them through the network browser and I am also able to ping their IP addresses and also ping their host name: ping wvip_fileserver. All sucessful results.
My Mac and Windows clients connect to this o.k. through the Chooser using Appletalk.
The strange thing is that when I rebooted this server, the shares are reachable from a clients RUN menu for about 1 min then 'bang' they are no longer available and you get the error message again.
I am stumped !
Any ideas ?
Many thanks !!
Seb.
ie. type \\wvip_fileserver\ in the Run box and click O.K. generates an error: \\wvip_fileserver\ 'the network name cannot be found'
At this point I would expect a new window to open displaying available shares and print queues. This has always worked o.k. until now.
This is also true of my other Windows 2000 servers on this site.
However, I am to connect to them through the network browser and I am also able to ping their IP addresses and also ping their host name: ping wvip_fileserver. All sucessful results.
My Mac and Windows clients connect to this o.k. through the Chooser using Appletalk.
The strange thing is that when I rebooted this server, the shares are reachable from a clients RUN menu for about 1 min then 'bang' they are no longer available and you get the error message again.
I am stumped !
Any ideas ?
Many thanks !!
Seb.
Did you try nslookup to test your DNS? Also you can repair your AD DNS entries using this command "netdiag /fix" on your DC's. Please read this:
Let me know if you tried nslookup to verify DNS.
SOKO
Let me know if you tried nslookup to verify DNS.
SOKO
If you go to a command prompt and type nslookup and then get a response that is something like unkown [can't remember exact message] this means your DNS is not working properly. Let me know how you make out...i have other suggestions but try these first to eliminate some issues.
SOKO
SOKO
Ok so you have 1 DC at this point with all 5 FSMO roles on it. Correct me if i have any information wrong.
You have DNS setup on ROSE-CLEARCC which is the your primary DC with all FSMO roles. (Windows2000)
You have DNS setup on ROSCLEARDC1 which is the server you are trying to make secondary DC. (Windows2003)
The DNS on ROSCLEARDC1 is pointing to ROSE-CLEARCC.
Correct??
Next:
On ROSE-CLEARCC check your TCP/IP settings and make sure you have setting correct.
1. Right-click My Network Places, and then click Properties.
2. Right-click Local Area Connection, and then click Properties.
3. Click Internet Protocol (TCP/IP), and then click Properties.
4. Click Advanced, and then click the DNS tab. Configure the DNS information as:
5. Configure the DNS server addresses to point to the DNS server that you configured in previous steps.
6. Make sure both boxes are checked for:
*Register this connection's address in DNS.
*Use this connection's DNS suffix in DNS registration
7. DNS suffix for this connection (should be your domain name)
example: If your servers fully qualified name is:
ROSE-CLEARCC.mydomain.com
***Then you would put mydomain.com in the DNS suffix box
The DNS server can be the domain controller’s own IP address. This is most likely to happen if it is the first server or if no dedicated DNS server will be configured. (In your case it should point to your primary DC)
Verify that the Register this connection's addresses in DNS check box is selected.
Purge the cache and force the registration of the host (A) records. At a command prompt, type the following commands, pressing ENTER after each command:
ipconfig /flushdns
ipconfig /registerdns
If the ipconfig /registerdns command generates the following error message
Error: The system cannot find the file specified. : Refreshing DNS names
Start and enable the DHCP Client service on this computer, and then run the ipconfig /registerdns command again. (Or just reboot the server)
Restart the Netlogon service to register the SRV records. At a command prompt, type the following commands, pressing ENTER after each command:
net stop netlogon
net start netlogon
Verify that the host (A) record and SRV "subfolders" appear in the DNS forward lookup zone that you created or verified earlier in this document. You can use the F5 key to refresh the DNS Server tool's view of the database.
IF THERE IS NO (A) RECORD FOR EITHER DC THEN MANUALLY CREATE ONE. Creating one is straight forward. I will assume you know how. If not, ask.
Good luck!
SOKO
You have DNS setup on ROSE-CLEARCC which is the your primary DC with all FSMO roles. (Windows2000)
You have DNS setup on ROSCLEARDC1 which is the server you are trying to make secondary DC. (Windows2003)
The DNS on ROSCLEARDC1 is pointing to ROSE-CLEARCC.
Correct??
Next:
On ROSE-CLEARCC check your TCP/IP settings and make sure you have setting correct.
1. Right-click My Network Places, and then click Properties.
2. Right-click Local Area Connection, and then click Properties.
3. Click Internet Protocol (TCP/IP), and then click Properties.
4. Click Advanced, and then click the DNS tab. Configure the DNS information as:
5. Configure the DNS server addresses to point to the DNS server that you configured in previous steps.
6. Make sure both boxes are checked for:
*Register this connection's address in DNS.
*Use this connection's DNS suffix in DNS registration
7. DNS suffix for this connection (should be your domain name)
example: If your servers fully qualified name is:
ROSE-CLEARCC.mydomain.com
***Then you would put mydomain.com in the DNS suffix box
The DNS server can be the domain controller’s own IP address. This is most likely to happen if it is the first server or if no dedicated DNS server will be configured. (In your case it should point to your primary DC)
Verify that the Register this connection's addresses in DNS check box is selected.
Purge the cache and force the registration of the host (A) records. At a command prompt, type the following commands, pressing ENTER after each command:
ipconfig /flushdns
ipconfig /registerdns
If the ipconfig /registerdns command generates the following error message
Error: The system cannot find the file specified. : Refreshing DNS names
Start and enable the DHCP Client service on this computer, and then run the ipconfig /registerdns command again. (Or just reboot the server)
Restart the Netlogon service to register the SRV records. At a command prompt, type the following commands, pressing ENTER after each command:
net stop netlogon
net start netlogon
Verify that the host (A) record and SRV "subfolders" appear in the DNS forward lookup zone that you created or verified earlier in this document. You can use the F5 key to refresh the DNS Server tool's view of the database.
IF THERE IS NO (A) RECORD FOR EITHER DC THEN MANUALLY CREATE ONE. Creating one is straight forward. I will assume you know how. If not, ask.
Good luck!
SOKO
Hey Lander215 they deleted your post below so i replied to this post for your answer...wondered how my post ended up here...anyway answer to the question below is in my posts above.
lander215 (IS/IT--Management) has responded to the question "Having problems adding another DC to an existing Windows 2000 AD DC" in the Microsoft: Windows 2000 Server forum in Tek-Tips.
Come to to view.
You were notified of this activity because you requested it. To turn off notification, log in to the Tek-Tips site click on the red checkmark next to the "Having problems adding another DC to an existing Windows 2000 AD DC" thread. Contact sitesupport@tek-tips.com if you have any problems or questions regarding this feature.
Regards,
Tek-Tips Forums
P.S. Start and moderate your own Tek-Tips Group! Click below for more information.
lander215 (IS/IT--Management) has responded to the question "Having problems adding another DC to an existing Windows 2000 AD DC" in the Microsoft: Windows 2000 Server forum in Tek-Tips.
Come to to view.
You were notified of this activity because you requested it. To turn off notification, log in to the Tek-Tips site click on the red checkmark next to the "Having problems adding another DC to an existing Windows 2000 AD DC" thread. Contact sitesupport@tek-tips.com if you have any problems or questions regarding this feature.
Regards,
Tek-Tips Forums
P.S. Start and moderate your own Tek-Tips Group! Click below for more information.
- Status
Similar threads
- Locked
- Question
