Re: Event ID 1111 on printer redirection

Tech-Archive recommends: Speed Up your PC by fixing your registry



You're welcome, Mike. Glad the problem is solved!

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

"=?Utf-8?B?TWlrZQ==?=" <Mike@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on
27 okt 2005 in microsoft.public.win2000.termserv.apps:

> Vera,
>
> You are right. It was a driver/name mismatch. The client at
> the remote end was using a HP LaserJet 1300 PCL 6 driver, and I
> had installed an HP LaserJet 1300 PCL 5e driver. After I
> figured that out and updated the driver on the server, it seems
> to be working now, although I'm not sure how it printed a test
> page before I updated the driver, but nonetheless it is working.
> Thanks so much for your response!
>
> Mike
>
>
> "Vera Noest [MVP]" wrote:
>
>> Maybe a driver name mismatch?
>> Check this for instructions on how to map the client driver to
>> the server driver:
>>
>> 239088 - Windows 2000 Terminal Services Server Logs Events
>> 1111, 1105, and 1106
>> http://support.microsoft.com/?kbid=239088
>>
>> _________________________________________________________
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>> TS troubleshooting: http://ts.veranoest.net
>> ___ please respond in newsgroup, NOT by private email ___
>>
>> "=?Utf-8?B?TWlrZQ==?=" <Mike@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote
>> on 26 okt 2005 in microsoft.public.win2000.termserv.apps:
>>
>> > Hi,
>> >
>> > I set up a remote user to print a couple of weeks ago, had
>> > her do a test page, it printed successfully and I thought I
>> > was done with this issue. She called me this morning, and
>> > can't print (hasn't printed since the test page 2 weeks ago),
>> > and when I look at the event viewer, there are Event ID 1111
>> > errors when she tries to print, telling me the driver is
>> > unknown. How can I fix this. The printer is a HP LaserJet
>> > 1300, and like I said, the 1st time I set it up it printed a
>> > test page for the client successfully. I tried to reinstall
>> > the driver on the server, but that didn't help. Any advice
>> > would be appreciated!
>> >
>> > Mike
.



Relevant Pages

  • core install of Solaris 9 (sparc) package list can be trimmed ?
    ... This is a server that will have very specific reasons ... system SUNWadmr System & Network Administration Root ... system SUNWeu8os American English/UTF-8 L10N For OS Environment User Files ... system R SUNWfcip Sun FCIP IP/ARP over FibreChannel Device Driver ...
    (comp.unix.solaris)
  • Re: 2008 SBS no longer boots
    ... driver issue initially, the fact that it seems to happen randomly now ... weird with a hardware problem that consistently doesn't get through boot ... other customer, even a 2 week old one, the problem immediately returned. ... There was a time when a server was fired up with a specialized OS and had a battery of tests run against each component to purposefully stress it. ...
    (microsoft.public.windows.server.sbs)
  • Re: 2008 SBS no longer boots
    ... Intel raid card for Server 2003. ... install with one raid driver, or with the other raid driver. ... Any thermal issues and a lot of other hardware problems should show up ... other customer, even a 2 week old one, the problem immediately returned. ...
    (microsoft.public.windows.server.sbs)
  • Re: AD replication not working
    ... Verifying that the local machine cls21, is a Directory Server. ... The DFS Replication Event Log. ... Driver RICOH Aficio 3035 PCL 6 required for printer ... and then clear the Log spooler warning events check box. ...
    (microsoft.public.windows.server.active_directory)
  • Re: AD replication not working
    ... Dcdiag states that cls21 and cls12 are having the PDCEmulator role. ... Verifying that the local machine cls21, is a Directory Server. ... The DFS Replication Event Log. ... Driver RICOH Aficio 3035 PCL 6 required for printer ...
    (microsoft.public.windows.server.active_directory)