Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We have a network with Windows 2008 R2 Terminal Servers and a print server, and experience printing problems every morning which disappear after a while. The IT department seems to have no idea what the reason could be.

The users connect using RDP and configure their printers using \\domain\printerId.

Is it recommended to use the FQDN instead? (\\my.domain.local\printerId)?

share|improve this question
it would be valuable to know what kind of printer problems exactly users are experiencing. Also, you suggest that you are using the \\domain\printer notation to connect to printers - is the domain controller your print server? Do you have more than one DC in your domain? Are you using Group Policy or scripts to connect to printers? If so, what is your exact configuration / command line to connect? – the-wabbit Jul 20 '12 at 9:45
Yeah, not really enough information here to propose a good theory. (Maybe why your IT department doesn't know either). You can always try connecting via FQDN or IP, but I wouldn't get my hopes up on that working. – HopelessN00b Jul 20 '12 at 13:00
you should not have to use an FQDN, as long as name resolution is working – Jim B Jul 20 '12 at 13:10
the short answer would be 'it should work either way but you should not waste your time typing extra characters'.If your IT dpt can't fix it I think they may be in the wrong trade. – Sergei Jul 20 '12 at 16:21

Why not just try it out and see if it solves your problem?

In general, I am in favour of FQDN's over Netbios names.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.