salterclan
asked on
Losing Printer Host(A) Records in upgraded Windows Server 2008 environment (also Access Points)
This is a large production environment with approximately 70 printers and 200 computers (at this location) across 5 floors so we have 5 subnnets. the problem is across all subnets. We moved one week ago from Server 2003 to 2008 for our DC's including our DHCP server. Approximately 4 days later we started getting printers who had their Host record disappear in in ForwardLookup but almost inevitably we had the PTR record remaing in Reverse lookup. I'm not looking for an answer like, change all of the printers to a Static IP and use reservations. This system was here before me and they aren't going to let me make such a change. plus our printers move relatively often from floor to floor so static ip's would be a pain anyway.
Other Details:
Each Printer has a DHCP account that allows them to update their info
If I clear the PTR record and then reboot the Jet Direct and the flush the DNS cache on our Print Server it will solve the issue as it queries DHCP again. Almost all printers are on the single File and Print but the issue isn't related to the one machine. We do have a few networked printers on other billing machines that exhibit the same behavior.
We turned off WINS
We are scavenging records on a 7 day interval
I have screenshot attached in the word file showing our DNS settings in DHCP.
Our wireless Access points are showing Similar behavior.
IPv4-Properties.doc
Other Details:
Each Printer has a DHCP account that allows them to update their info
If I clear the PTR record and then reboot the Jet Direct and the flush the DNS cache on our Print Server it will solve the issue as it queries DHCP again. Almost all printers are on the single File and Print but the issue isn't related to the one machine. We do have a few networked printers on other billing machines that exhibit the same behavior.
We turned off WINS
We are scavenging records on a 7 day interval
I have screenshot attached in the word file showing our DNS settings in DHCP.
Our wireless Access points are showing Similar behavior.
IPv4-Properties.doc
ASKER
Let me answer some of those questions now and get back to you.
The new Windows 2008 server is a completely new build and it has the same name as the old DNS server so the IP address didn't change.
We have no Windows 2003 DC servers at this site. We do have other sites in the forest that have Wiondows 2003 Dc's
I don't know what you mean but are the printers setup to update DNS. Could please elaborate?
I will look into disabling IPv6 now. I think it is already disabled, just not removed but I will check.
thanks
The new Windows 2008 server is a completely new build and it has the same name as the old DNS server so the IP address didn't change.
We have no Windows 2003 DC servers at this site. We do have other sites in the forest that have Wiondows 2003 Dc's
I don't know what you mean but are the printers setup to update DNS. Could please elaborate?
I will look into disabling IPv6 now. I think it is already disabled, just not removed but I will check.
thanks
ASKER
Also, I don't think the support article you sent applies. I don't see any zone issues, and we haven't had any DNS errors in the eventlog, except a few relating to a specific device that had been shut off.
ASKER
I read this while browsing on disabling IPv6. Cosidering I have no zones setup for IPv6 are you sure this is needed? See below
Domain Name System
If you disable either the IPv4 or the IPv6 stack after you have installed the domain name system (DNS) Server role, you will experience timeouts and delays in DNS queries.
Do not enable or disable the IPv4 or the IPv6 stack unless necessary.
If you must enable or disable either stack after installing the DNS Server role, restart the DNS Server service.
If you cannot restart the DNS Server service, manually remove the invalid forwarders for the disabled stack. For example, if the IPv6 stack is disabled, remove the IPv6 forwarders.
Domain Name System
If you disable either the IPv4 or the IPv6 stack after you have installed the domain name system (DNS) Server role, you will experience timeouts and delays in DNS queries.
Do not enable or disable the IPv4 or the IPv6 stack unless necessary.
If you must enable or disable either stack after installing the DNS Server role, restart the DNS Server service.
If you cannot restart the DNS Server service, manually remove the invalid forwarders for the disabled stack. For example, if the IPv6 stack is disabled, remove the IPv6 forwarders.
Can you run a dcdiag and post results. Please post ipconfig /all for one of the systems that get DHCP this doesn't have to be a printer a workstation will do.
What I mean are the printers set to update a DNS server with it's interface for example if you go to your TCP\IP properties on a Windows machine then click Advance and DNS tab you will see register this connection with DNS.
What I mean are the printers set to update a DNS server with it's interface for example if you go to your TCP\IP properties on a Windows machine then click Advance and DNS tab you will see register this connection with DNS.
The above statement can fixed with a quick restart of the DNS service.
Once disabling IPv6 you run ipconfig /flushdns, ipconfig /registerdns, and dcdiag /fix.
I have not experienced timeouts myself after disabling IPv6 and if I did the fix would be to restart the DNS service.
Once disabling IPv6 you run ipconfig /flushdns, ipconfig /registerdns, and dcdiag /fix.
I have not experienced timeouts myself after disabling IPv6 and if I did the fix would be to restart the DNS service.
ASKER
I'm including the DCDiagnostic I just ran. I ran dcdiag and dcdiag /dnsall. At the bottom of the file is my ipconfig /all. I'd already ran the diagnostics and except for an error related to Read only DNS I think it passed with flying colors. I will go ahead and add the registry setting and see if I can restart the Server in a few minutes during our lunch hour.
DC-Diagnostic.txt
DC-Diagnostic.txt
ASKER
I made the registry change but won't be able to reboot the server for another 4 hours. I'll send an update as soon as I am able to make that change.
Let me know Thanks!
ASKER
I am including a Word Document with a few error messages that happened on the DC Server. Most importantly I made the registry change and rebooted the DC and it's still there. Maybe you can help me understand that one. Either way, I am still having the issue this morning.
Followup-Doc.doc
Followup-Doc.doc
ASKER
one more update. This not related to only printers. Rarely would we need to do Nslookups on workstations but I decided to run a test and we have workstations with the exact same issue. Going to reboot one now and see if it solves the problem without any outside interference in DNS.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Sorry about that I must have deleted the emails or just didn't see that you responded.
ASKER
It's definitely not a problem. I have it working now which is the important thing.
Now I get to setup new DC's in all our other remote offices. I wonder if I will run into the same issues there. 2003 Dc's where I have to copy the DHCP and DNS settings over to a new 2008 DC.
Now I get to setup new DC's in all our other remote offices. I wonder if I will run into the same issues there. 2003 Dc's where I have to copy the DHCP and DNS settings over to a new 2008 DC.
You shouldn't have to. I have had to do it once when Windows 2008 server first came out.
Are the printers setup to update DNS?
Do you still have Windows 2003 DNS servers?
http://support.microsoft.com/kb/953317
Are the printers still pointing to the old DNS IP address?