I have two servers (win2k) with TS , the properties are the same and the
printers drivers too, when I connect to one of them I get (redirect) all my
local printer, and when I connect to the other one, I cen't see none of
them.
any ideas ???

Printer driver names may vary slightly on different clients.
I.e if one client runs W2K Pro and the other runs XP Pro, the same
printer driver may have a slightly different name. And if the name of
the printer driver on the client does not match the name of the
printer driver on the server *exactly*, the printer will not be
autocreated. If that is the problem, you will have to map the printer
driver to the correct driver on the server.

Check this article for details:

239088 - Windows 2000 Terminal Services Server Logs Events 1111,
1105, and 1106
http://support.microsoft.com/?kbid=239088

"ùòéä" <(E-Mail Removed)> wrote in
news:(E-Mail Removed):

> I have two servers (win2k) with TS , the properties are the
> same and the
> printers drivers too, when I connect to one of them I get
> (redirect) all my local printer, and when I connect to the
> other one, I cen't see none of them.
> any ideas ???

Hi
The Evnt Id that I get is 1103, this event is not appear in the document.
Thanks


"Vera Noest [MVP]" <(E-Mail Removed)> ëúá áäåãòä
news:Xns943DD894E8BDAveranoesthemutforsse@207.46.248.16...
> Printer driver names may vary slightly on different clients.
> I.e if one client runs W2K Pro and the other runs XP Pro, the same
> printer driver may have a slightly different name. And if the name of
> the printer driver on the client does not match the name of the
> printer driver on the server *exactly*, the printer will not be
> autocreated. If that is the problem, you will have to map the printer
> driver to the correct driver on the server.
>
> Check this article for details:
>
> 239088 - Windows 2000 Terminal Services Server Logs Events 1111,
> 1105, and 1106
> http://support.microsoft.com/?kbid=239088
>
> "ùòéä" <(E-Mail Removed)> wrote in
> news:(E-Mail Removed):
>
> > I have two servers (win2k) with TS , the properties are the
> > same and the
> > printers drivers too, when I connect to one of them I get
> > (redirect) all my local printer, and when I connect to the
> > other one, I cen't see none of them.
> > any ideas ???

What I have to fill in the "version" section
Thanks

"Vera Noest [MVP]" <(E-Mail Removed)> ëúá áäåãòä
news:Xns943DD894E8BDAveranoesthemutforsse@207.46.248.16...
> Printer driver names may vary slightly on different clients.
> I.e if one client runs W2K Pro and the other runs XP Pro, the same
> printer driver may have a slightly different name. And if the name of
> the printer driver on the client does not match the name of the
> printer driver on the server *exactly*, the printer will not be
> autocreated. If that is the problem, you will have to map the printer
> driver to the correct driver on the server.
>
> Check this article for details:
>
> 239088 - Windows 2000 Terminal Services Server Logs Events 1111,
> 1105, and 1106
> http://support.microsoft.com/?kbid=239088
>
> "ùòéä" <(E-Mail Removed)> wrote in
> news:(E-Mail Removed):
>
> > I have two servers (win2k) with TS , the properties are the
> > same and the
> > printers drivers too, when I connect to one of them I get
> > (redirect) all my local printer, and when I connect to the
> > other one, I cen't see none of them.
> > any ideas ???

OK, then this might help. What SP are you running?

276532 - Windows 2000 Terminal Server Reports Event ID 1103 in the
System Event Log
http://support.microsoft.com/?kbid=276532

--
Vera Noest
MCSE,CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
*----------- Please reply in newsgroup -------------*

"ùòéä" <(E-Mail Removed)> wrote in
news:#Nd$(E-Mail Removed):

> Hi
> The Evnt Id that I get is 1103, this event is not appear in the
> document. Thanks
>
>
> "Vera Noest [MVP]" <(E-Mail Removed)> ëúá
> áäåãòä
> news:Xns943DD894E8BDAveranoesthemutforsse@207.46.248.16...
>> Printer driver names may vary slightly on different clients.
>> I.e if one client runs W2K Pro and the other runs XP Pro, the
>> same printer driver may have a slightly different name. And if
>> the name of the printer driver on the client does not match the
>> name of the printer driver on the server *exactly*, the printer
>> will not be autocreated. If that is the problem, you will have
>> to map the printer driver to the correct driver on the server.
>>
>> Check this article for details:
>>
>> 239088 - Windows 2000 Terminal Services Server Logs Events
>> 1111, 1105, and 1106
>> http://support.microsoft.com/?kbid=239088
>>
>> "ùòéä" <(E-Mail Removed)> wrote in
>> news:(E-Mail Removed):
>>
>> > I have two servers (win2k) with TS , the properties are the
>> > same and the
>> > printers drivers too, when I connect to one of them I get
>> > (redirect) all my local printer, and when I connect to the
>> > other one, I cen't see none of them.
>> > any ideas ???