Re: Printer is not created in W2K3 TS with Windows XP Pro SP2 Clie
- From: "Sean Lamberson" <slamberson(at)mcpafl(dot)org(donotspam)>
- Date: Tue, 16 Aug 2005 12:13:06 -0700
There are no events being logged in the Event Log when the Windows XP Client
connects. I have already looked at that KB article and did not help me. I
thank you for your response.
Sean Lamberson
"Vera Noest [MVP]" wrote:
> Have you checked the EventLog on the Terminal Server to see the
> reason why the printers are not autocreated?
>
> Since the same printers are autocreated from W2K clients, I suspect
> that the printer driver name on XP is slightly different. As an
> example, if the driver is called "HP LaserJet" on W2K and "HP
> Laserjet" on XP, the printer will not be autocreated (case-
> sensitive driver name!).
> If that is the problem, map the printer driver to the corrct name,
> as explained here:
>
> 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?U2VhbiBMYW1iZXJzb24=?="
> <slamberson(at)mcpafl(dot)org(donotspam)> wrote on 16 aug 2005 in
> microsoft.public.windows.terminal_services:
>
> > Our printers are all connected through IP addresses. We have a
> > few that are parallel based that are shared through a print
> > server.
> >
> > "Gregg Hill" wrote:
> >
> >> Sean,
> >>
> >> Are they DOT4 ports or local USB/LPT ports? If they are DOT4
> >> ports, you may need to hack the registry.
> >>
> >> http://support.microsoft.com/default.aspx?scid=kb;en-us;302361
> >>
> >> Gregg Hill
> >>
> >>
> >> "Sean Lamberson" <Sean Lamberson@xxxxxxxxxxxxxxxxxxxxxxxxx>
> >> wrote in message
> >> news:C6225078-1812-497D-B985-599B6E46C660@xxxxxxxxxxxxxxxx
> >> > Our office uses TS for a database application and all of our
> >> > clients have to
> >> > be able to print. We were using W2K Pro with Remote Desktop
> >> > Connection to allow printers to be redirected. This has
> >> > worked fine for almost a year now.
> >> > We just recently purchased 8 new computers with Windows XP
> >> > Pro SP2 and upon
> >> > connecting to TS the printers are not created. These same
> >> > printers are created with no problem when connecting from a
> >> > W2K client. I have searched
> >> > and searched online and cannot find anything wrong with the
> >> > way they are connecting. They have the check box enabled to
> >> > connect printers and disk drives.
> >> >
> >> > Thank you,
> >> > Sean Lamberson
>
.
- Follow-Ups:
- Re: Printer is not created in W2K3 TS with Windows XP Pro SP2 Clie
- From: Vera Noest [MVP]
- Re: Printer is not created in W2K3 TS with Windows XP Pro SP2 Clie
- References:
- Printer is not created in W2K3 TS with Windows XP Pro SP2 Client
- From: Sean Lamberson
- Re: Printer is not created in W2K3 TS with Windows XP Pro SP2 Client
- From: Gregg Hill
- Re: Printer is not created in W2K3 TS with Windows XP Pro SP2 Clie
- From: Sean Lamberson
- Re: Printer is not created in W2K3 TS with Windows XP Pro SP2 Clie
- From: Vera Noest [MVP]
- Printer is not created in W2K3 TS with Windows XP Pro SP2 Client
- Prev by Date: Re: How to Stop Server from advertising?
- Next by Date: Re: Cannot get profile redirection to work
- Previous by thread: Re: Printer is not created in W2K3 TS with Windows XP Pro SP2 Clie
- Next by thread: Re: Printer is not created in W2K3 TS with Windows XP Pro SP2 Clie
- Index(es):
Relevant Pages
|