In one of our department we have several windows 7 clients that use a Legacy application, every morning, we must do a ipconfig /flushdns along with nbtstat -R, arp -d accompanied with a reboot, then users can print again via the application for entire work day. When they come back in next morning the DNS flush...etc process must be repeated otherwise the App hangs spinning when press the print button. I was thinking DNS cache is expiring and App is try to still use it next morning...etc I don't know if this is a DC issue or client pc issue. Same happens for other network printers used in the Application, hang, until to the temp fix...etc.
For testing, I editing our test pc so the local DNS cache is disabled or set to "1" using MaxDNScacheTTL = 1 and believe it or not, printing worked fine for the 1st time in the morning without DNS flush...etc. So, this leads me to believe maybe client's local DNS cache is not being deleted properly, or, the Legacy App is not using the new cache possibly..etc It appears the client PCs sit over night and DNS cache expires causing the printing issue in the morning.
* Both print server and printers are all static IPs.
Edited by jim_ea, 10 August 2016 - 12:58 PM.