• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Server 2008 R2 shared printer issues.

C

cyclone3d

Fully [H]
2FA
Joined
Aug 16, 2004
Messages
18,292
Here is what we are trying to do: (server names have been changed to protect the innocent, etc. :D )

3 servers at 3 different locations - all running Server 2008 R2 and all on the same domain

setup:
server01 (has the print server role and printers are shared out)
server02 (has the print server role and printers are shared out)
terminal_server (a terminal server)

We have printers on server01 and on server02 that we need to install on terminal_server.

The printers install just fine onto terminal_server from server01 when browsing and connecting or opening the shared printers.

The printers on server02 give thes error message when trying to connect to or open them from terminal_server:

"The operation could not be completed (error 0x00000709). Double check and make sure that the printer is connected to the network."

However, the printers from server02 will install and work just fine IF I install them as IP printers.

Anybody have any idea why I would not be able to connect to them by share name?

I have already had the firewall guy check the settings and he said that the firewall settings are identical for both sites.
 
Can you ping server02 from the terminal server? If they are both are on the same domain then they should be picking up the same DNS (as long as the DNS is defined by the domain controller), might refresh your security policies and try again.
 
Taco_Island said:
Can you ping server02 from the terminal server? If they are both are on the same domain then they should be picking up the same DNS (as long as the DNS is defined by the domain controller), might refresh your security policies and try again.
Click to expand...

Ping works, tracert works, browsing files on server02 works. you can even see the printer shares from the terminal server.

I have already forced an update of security policies and rebooted server02. None of which made a difference.

I have tried manually giving the terminal server full premissions to the printers.

The guy I was working with that is on the infrastructure team said that it looked like the terminal server was not even trying to connect to server02 in order to connect to the printers.

This makes sense at it errors out immediately.. no pause.. no spinning ring, no nothing. The error just pops up.

It seems like the terminal server doesn't think that server02 even exists.. but only when trying to connect to the printers.
 
Have you checked your spool\printers folder to see if there is a corrupt print job possibly blowing up your spooler? If it is only affecting the printers I would check there, sometimes they don't get cleared out properly.
 
Check the firewall and network discovery settings on your print servers. Connecting by the printers IP means you're completely bypassing the print server(though your wording doesn't make this clear). Since you're hitting the UNC shares, its probably not DNS, but you do need to confirm that your domain controller is handling DNS for every server involved.
 
You must log in or register to reply here.
Back
Top