One of our users reported being unable to map one of the network printers ( Windows cannot connect to the printer ). Although we use a script to map drives and printers, this particular printer could not be added using the script nor manually.
When user browsed the server and tried to add the printer manually, he received the following error message:
Connect to Printer
Windows cannot connect to the printer. The specified port is unknown.
I have managed to map the printer manually when I have accessed the print server using IP address instead of the server name.
This was just a temporary solution and I’m yet to figure out what was the issue here. It appears as a DNS issue, but I still can’t confirm the culprit.
What is even more strange, the printer was normally mapped the second day with the script that is using a hostname of the print server.