Windows Print server DNS Resolver
we have windows print servers ,where the print queues are set up and drivers are installed.
from windows clients, users or sometimes help desk will add printers by typing \\printservername\queuenam
at this point they should be able to add network printers to their PCs
Sometimes (and that is what I do not understand) it happens that engineers will have to run Ipconfig/flushdns on the print server itself to fix windows client printer connection to print server
To my understand that command needs to be run on the windows Client instead.
Can anyone explain why they run the command on print server ?
Thank you
from windows clients, users or sometimes help desk will add printers by typing \\printservername\queuenam
at this point they should be able to add network printers to their PCs
Sometimes (and that is what I do not understand) it happens that engineers will have to run Ipconfig/flushdns on the print server itself to fix windows client printer connection to print server
To my understand that command needs to be run on the windows Client instead.
Can anyone explain why they run the command on print server ?
Thank you
Don't know why but your printer problem comes not from DNS Server (delete dns cache) but rather from the dns cache of the print server. With ipconfig /flushdns your erase & discard negative cache entries.
Do you use printer wsd ports?
WSD ports work fine if properly configured. That it how we set up modern HP Printers. However, TCP/IP ports can work very well also.
ASKER
Let me rephrase it.
These servers are separate: DNS server , Windows Print Server, Windows 7 client.
From Windows 7 , when you add a printer like this : \\Printservername\Printque
well let's break it down:
\\Printservername : this will query DNS server for the name of Printservername
if it is able to map it then the Windows7 client will be able to reach Printservername.
\Printquename, this is treated as a "share", it will popup right after you type \\Printerservername\
Well, as conclusion, I do not see what Print server DNS cache has to do with the process I described above other than rendering the share name and why do Administrators have to flush print server DNS cache to resolve the issue.
These servers are separate: DNS server , Windows Print Server, Windows 7 client.
From Windows 7 , when you add a printer like this : \\Printservername\Printque
well let's break it down:
\\Printservername : this will query DNS server for the name of Printservername
if it is able to map it then the Windows7 client will be able to reach Printservername.
\Printquename, this is treated as a "share", it will popup right after you type \\Printerservername\
Well, as conclusion, I do not see what Print server DNS cache has to do with the process I described above other than rendering the share name and why do Administrators have to flush print server DNS cache to resolve the issue.
ASKER
If you say Printqueuename when created on Print server is cached on the print server DNS cache itself and each time you browse to it with \\printservername\printque
ASKER
Any comments on this ?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thank you
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.
Also, the next time this happens, do not change the server, but try to access the printer by IP address. There could also be a DNS issue.