If it does not work, then there is something fundamental wrong with your naming and the solution is beyond the scope of this document. If you do not have any server on your subnet supplying netbios name resolution, hardcoded mappings are your only option. Refer to Section Two of this FAQ for more ideas. This message indicates that your client CAN locate the specified server, which is a good start, but that it cannot find a service of the name you gave. Many clients cannot accept or use service names containing spaces.
Some clients force service names into upper case.
Seeing this message should not affect your ability to mount redirected disks and printers, which is really what all this is about. Make sure that the spool directory specified for the service is writable by the user connected to the service. Make sure that the user specified in the service is permitted to use the printer. Check the debug log produced by smbd. Search for the printer name and see if the log turns up any clues.