Yes, Another Printing Problem

I've downloaded and read Claudio's instructions on getting printers not
natively supported in Win2k to work through Terminal Services. It just
doesn't work. I continue to recieve Event ID 1111, asking me to install the
printer driver.

I have also followed Microsoft's recommendations from Knowledge Base Article
239088. Niether of these solutions seem to be working for me. The Event
1111's just keep coming.

Anyone have any further suggestions?

Ok...

1) what is the name of the printer driver on the client?

B) what is the name of the printer driver installed on the
terminal server?

iii) what does the line of the ntprint.inf file look like
that refers to the printer driver name on the client? (it
should look like "client printer driver name" = "server
printer driver name"

-M

>-----Original Message-----
>I've downloaded and read Claudio's instructions on
getting printers not
>natively supported in Win2k to work through Terminal
Services. It just
>doesn't work. I continue to recieve Event ID 1111, asking
me to install the
>printer driver.
>
>I have also followed Microsoft's recommendations from
Knowledge Base Article
>239088. Niether of these solutions seem to be working for
me. The Event
>1111's just keep coming.
>
>Anyone have any further suggestions?
>
>
>.
>

The name of the printer driver on the client is identical to the name of the
Driver. It will be, for example: hp deskjet 630c series

The ntprint.inf file looks like: "hp deskjet 630c series" = "hp deskjet 630c
series"

Thanks for your help!!!

"Matthew Harris [MVP]" <harris@crocker.ucdavis.edu> wrote in message
news:0d3701c34b2e$3c4fd6f0$a001280a@phx.gbl...
> Ok...
>
> 1) what is the name of the printer driver on the client?
>
> B) what is the name of the printer driver installed on the
> terminal server?
>
> iii) what does the line of the ntprint.inf file look like
> that refers to the printer driver name on the client? (it
> should look like "client printer driver name" = "server
> printer driver name"
>
> -M
>
> >-----Original Message-----
> >I've downloaded and read Claudio's instructions on
> getting printers not
> >natively supported in Win2k to work through Terminal
> Services. It just
> >doesn't work. I continue to recieve Event ID 1111, asking
> me to install the
> >printer driver.
> >
> >I have also followed Microsoft's recommendations from
> Knowledge Base Article
> >239088. Niether of these solutions seem to be working for
> me. The Event
> >1111's just keep coming.
> >
> >Anyone have any further suggestions?
> >
> >
> >.
> >

So with this configuration, things don't work correctly?

If it didn't work, try changing the driver mapping on the
server side. Something like:

"hp deskjet 630c series" = "HP Deskjet"

The "HP Deskjet" driver came with the Windows 2000
installation, so you shouldn't need to install additional
drivers.

-M

>-----Original Message-----
>The name of the printer driver on the client is identical
to the name of the
>Driver. It will be, for example: hp deskjet 630c series
>
>The ntprint.inf file looks like: "hp deskjet 630c series"
= "hp deskjet 630c
>series"
>
>Thanks for your help!!!
>
>"Matthew Harris [MVP]" <harris@crocker.ucdavis.edu> wrote
in message
>news:0d3701c34b2e$3c4fd6f0$a001280a@phx.gbl...
>> Ok...
>>
>> 1) what is the name of the printer driver on the client?
>>
>> B) what is the name of the printer driver installed on
the
>> terminal server?
>>
>> iii) what does the line of the ntprint.inf file look
like
>> that refers to the printer driver name on the client?
(it
>> should look like "client printer driver name" = "server
>> printer driver name"
>>
>> -M
>>
>> >-----Original Message-----
>> >I've downloaded and read Claudio's instructions on
>> getting printers not
>> >natively supported in Win2k to work through Terminal
>> Services. It just
>> >doesn't work. I continue to recieve Event ID 1111,
asking
>> me to install the
>> >printer driver.
>> >
>> >I have also followed Microsoft's recommendations from
>> Knowledge Base Article
>> >239088. Niether of these solutions seem to be working
for
>> me. The Event
>> >1111's just keep coming.
>> >
>> >Anyone have any further suggestions?
>> >
>> >
>> >.
>> >
>
>
>.
>