64 Bit Server 2008 and 32 Bit XP Print Clients

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • KenB
    Geek Extraordinaire

    2,500+ Posts
    • Dec 2007
    • 3945

    #1

    64 Bit Server 2008 and 32 Bit XP Print Clients

    Hi, Gang,

    Just installed an MP C4000 at a client who has a shiny brand new 64 bit 2008 Server.

    I was easily able to install the 64 bit 2008 driver on the Server, and add the 32 bit XP PCL6 as additional drivers.

    Everybody could print just fine, both in color and B&W.

    Until today, that is...

    When I (foolishly) attempted to implement User Codes to limit access to color printing, all color printing stopped, even when a correct User Code is used. (I connected my notebook to the network, printing directly to the MFP, and all was good, verifying that the machine was cool.)

    Updating all firmware to current versions on the little beast made no difference.

    My hunch is that the User Code isn't getting passed to the printer, either by Server 2008, or the "extra" 32 bits.

    I have not done a packet capture just yet, but I will if needed. Besides, it's way harder tom parse a PCL6 print stream than PCL5.

    The Ricoh help desk did "somewhat" acknowledge this to be an issue, but could not confirm it.

    Not a peep about it on the TSC site, at least that I could find.

    Would Basic or Windows authentication work better, or possibly using the alternative approach of installing the driver locally, then uploading it to the Server?

    While I'm not a fan of the PCL5 driver on the newer boxes (issues...), maybe that would help, or the RPCS, or the Universal PCL? No PostScript, though; the option t'aint there.

    Thanks,
    “I think you should treat good friends like a fine wine. That’s why I keep mine locked up in the basement.” - Tim Hawkins
  • cobiray
    Passing Duplication Xpert

    1,000+ Posts
    • Mar 2008
    • 1199

    #2
    I've had this issue with several accounts, not just with 64 bit 2008 Server. The best bet I had had to do with rights, but the admins never seem to think it's their problem. My only solution was to load drivers locally and then use the user codes. This solution has worked at all places, once I was able to get user rights to add local printers.
    the savin2535 is displaying well bet the hiter lamp is not shining and the lamp had been tested o.k.please kindly help.
    Samir: No, not again. I... why does it say paper jam when there is no paper jam? I swear to God, one of these days, I just kick this piece of shit out the window.
    Michael Bolton: You and me both, man. That thing is lucky I'm not armed.

    Comment

    • Captain Scott
      Trusted Tech

      100+ Posts
      • Dec 2008
      • 166

      #3
      This is worth a try!

      Populate the servers driver with a invalid usercode eg. 0000. Add the network printer on the clients pc and change the dummy code to a valid one. I would be interested if this works, I have heard of a similar situation where this was a work around.

      Comment

      • df3036
        Trusted Tech

        100+ Posts
        • Feb 2009
        • 109

        #4
        What happens if you use the Default Editor found on the TSC to force a popup for the user code?
        Kittens give Morbo gas.

        A+, Network+, Server+, PDI+

        Comment

        Working...