[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1202
  • Last Modified:

Printer doesn't appear in terminal server

I followed other questions in this area but still am not successful.

1 - Using local pc with locally networked printer.  Printer is Brother MFC8220 and prints fine locally.
2 - Downloaded Brother MFC8220 drivers from Brother for Server 2003 and put them in System32 directory on terminal server.
3 - Checked box for using local printer while logged on terminal services.

No Brother appears when I sign on to term services.

0
william_schubert
Asked:
william_schubert
  • 6
  • 5
1 Solution
 
Rant32Commented:
Hi William,

Before anything else, Windows Server 2003 with SP1 supports fall-back color and monochrome drivers for printers that aren't directly supported through drivers. You might try those first before installing any drivers on a production Terminal Server. This is a Group Policy that can be enabled on the TS.

More info: http://www.brianmadden.com/content/content.asp?id=438

<< put them in System32 directory on terminal server. >>

Don't exactly know what you mean by that, but the driver needs to be installed via the print server properties. Open Control Panel > Printers & Faxes, right-click an empty area and select Server Properties. Open the Drivers tab and add the printer driver to your server by browsing to the .INF file.

Be sure to use the latest WHQL certified drivers without any kind of "wizard" software that usually comes with printers. Non-certified drivers are usually not tested in a multi-user TS environment and are known for causing all kinds of problems.
0
 
william_schubertAuthor Commented:
I think that Rant32 already identified the problem.  I had already registered the drivers correctly and had forgotten that.  But during the registration I in fact got the message indicating that the drivers were not certified so that may be the entire problem.  So maybe I'll be able to use a lower level driver from Brother that is certified.
0
 
Rant32Commented:
The TS fallback driver is most recommended, but it is possible that it doesn't print correctly (it's a very generic driver).

Have you got this one?

http://welcome.solutions.brother.com/bsc/public/eu/gb/en/dlf/download_index.html?reg=eu&c=gb&lang=en&prod=mfc8220_eu&type2=1&os=23&flang=English&dlid=

Version 1.04 seems WHQL certified.
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
william_schubertAuthor Commented:
Following your advice, I reconfigured the local printer to a Brother MFC6000 which is a certified driver.  Added the driver locally, did a print test, added the drivers to the server using the ones that were already listed (and said 'certified'), reestablished a session.. and.. .. nothing.  No brother printer there.  
So, I'm kind of back to square one but worse.  I'm pretty sure I have this configured correctly now.  I can see the drivers in Server Properties, the Brother MFC6000 ones but nothing.  
The people who host the server, OnRamp (http://www.onr.com/) have pretty much said that I'm on my own.  I've obviously got admin access to the server remotely so I guess I can do whatever I want.

Think a reboot?

I'm not at the client's business right now but will be going back later.
0
 
Rant32Commented:
The driver name listed in the OEMSETUP.INF file should *exactly* match the printer driver name of the client.

If the problem is driver related, then there should be two error events on the TS at the time of logon. Please post details about those errors, this should clear things up.

Again, using the fall-back driver doesn't use an OEM driver and is recommended as long as you it prints like it should. Are you running 2003 SP1 ?
0
 
william_schubertAuthor Commented:
Thanks for the clues.  I'll be able to test and give more info in a couple of hours once I get through with current client.
0
 
Rant32Commented:
I'll be sound asleep in a couple of hours, but we'll see.
0
 
william_schubertAuthor Commented:
Can't get to TS.  Customer w/ password is not around.  Will post info in the morning.  Thanks.
0
 
william_schubertAuthor Commented:
I rebooted the server just start fresh.  No issues on reboot.  No real log errors other than the usual W32 time stuff.  Logged on remotely and printer is still not picked up.  I have the printer set up on the client end with certified drivers, Brother MFC6000, available in XP and 2003.  The printer seems ok locally with that driver.  Set it up on server end with the Servers properties setup with same certified driver.

Server has SP1.

Logged on as usuer and logon is successful in the event viewer with no errors at all.

I'm at a complete loss.
0
 
Rant32Commented:
<< usual W32 time stuff >>

Uh, no such thing as usual W32Time stuff? Time sync is important (in a domain) and should work.

If there are no related errors in the server's event viewer then the printer redirection is not even attempted.

<< Using local pc with locally networked printer >>
Assuming here the printer is pointing at an MS network printserver (i.e. \\printserver\brotherMFC). This article could apply:
http://support.microsoft.com/support/kb/articles/q264/0/39.asp

Also make sure that client printer redirection is not disabled on the server-side, Control Panel > Terminal Services Configuration > RDP-TCP properties > tab Client Settings. The toggle for Client printers should be OFF.

Also, try installing a good old HP LaserJet 4 on LPT1 on the client. See if that one is redirected.
0
 
william_schubertAuthor Commented:
I see W32 time errors all the time on all kinds of servers.. have for a long time.  Think it is just one error in many attempts.
Anyway, I won't be back at client until tomorrow but will look at it then.  I've seen how the printer is networked but can't describe it without looking again.  Not a server or PC, though.
And, of course, client says the old line 'it worked before you got here'.  Of course the entire system was off line and client was logging in to the local pc's with a cached account from a domain that no longer existed.  But the printer worked.

More followup tomorrow.
0

Featured Post

NFR key for Veeam Agent for Linux

Veeam is happy to provide a free NFR license for one year.  It allows for the non‑production use and valid for five workstations and two servers. Veeam Agent for Linux is a simple backup tool for your Linux installations, both on‑premises and in the public cloud.

  • 6
  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now