Re: Printing to a TCP/IP printer

From: Vera Noest [MVP] (vera.noest_at_remove-this.hem.utfors.se)
Date: 10/28/04 

Date: Thu, 28 Oct 2004 11:15:02 -0700

I would suggest a different approach:

The remote Windows XP client can print to this printer, correct?
Assuming it can, the printer is defined on the XP client in the
users profile as a (local) network printer.

If you then start a rdp session from the XP client to the Terminal
Server, why is the printer not autocreated in the users session?
It should be, assuming that you have configured rdp to
autoredirect client printers. Also make sure that you run at least
rdp 5.2 on the client (which supports redirection of network
printers).

Have you checked the EventLog on the TS? Maybe the only thing you
have to fix is to map the printer driver to a native driver on the
server.

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
http://hem.fyristorg.com/vera/IT
 --- please respond in newsgroup, NOT by private email ---

"=?Utf-8?B?Qm9iUw==?=" <BobS@discussions.microsoft.com> wrote on
28 okt 2004 in microsoft.public.win2000.termserv.clients:

> Vera,
>
> Thanks for the reply. I have a couple of questions about what
> you wrote. You can see my reply to Mike D for complete details
> about the set up, but basically, the IP address scheme for the
> home office local network (behind the firewall) is
> 192.168.0.xxx, and the IP address scheme at the remote site,
> behind their DSL router/firewall is 192.168.3.xxx. So, I am not
> sure:
>
> 1. How to set the printer up at the Terminal Server end. The
> Xerox tech that delivered the printer installed it (the driver &
> software) as though the printer were actually there at the
> Terminal Server, but with an IP address matching the scheme for
> the remote office.
>
> 2. If the VPN that is established before logging into the
> terminal server is keeping the computer from senting stuff out
> to other IP's at the remote site.
>
> The client logon scripts need to be flexible enough for the to
> log on at the remote site, or to a local workstation at the home
> office.
>
> Thanks again for your reply.
>
> Bob Showalter, Packer International
> PackerIntl@qwest.net
>
>
> "Vera Noest [MVP]" wrote:
>
>> One way is to install the printer on the TS (thereby in effect
>> making the TS function as a PrintServer as well). If you have a
>> separate PrintServer, that would be even better.
>>
>> Once the printer is reachable throughout the network, your
>> clients can connect to it on their XP clients, making it the
>> default printer. It will then automatically be redirected into
>> their rdp session
>>
>> Or define this printer as the default printer for TS users in a
>> login script. You'll need some sort of utility to do this:
>> Defprint.exe controls local printers (local to the TS),
>> Con2prt.exe controls network printers, or use a KiXtart script.
>>
>> Examples (check for correct syntax!)
>>
>> if %Clientname% == CLIENT01 DefPrint.exe /d "HP OfficeJet"
>>
>> if %clientname% == CLIENT01 con2prt.exe \\PrintServer\printer01
>>
>> if %clientname% = "CLIENT01"
>> SetDefaultPrinter ("\\TS\printer01")
>> endif
>>
>> Defprint.exe can be downloaded here:
>> http://www.dcug.de/phpnuke/html/modules.php?
>> name=Downloads&d_op=MostPopular
>>
>> con2prt.exe is part of the NT Resource Kit.
>> KiXtart can be downloaded from http://www.kixtart.org
>>
>> --
>> Vera Noest
>> MCSE,CCEA, Microsoft MVP - Terminal Server
>> http://hem.fyristorg.com/vera/IT
>> *----------- Please reply in newsgroup -------------*
>>
>> "=?Utf-8?B?Qm9iUw==?=" <BobS@discussions.microsoft.com> wrote
>> on 28 okt 2004:
>>
>> > I have several computers at remote sites that connect to the
>> > terminal server and are able to print fine to their local
>> > LPT1 printers. I now have a TCP/IP printer at a new remote
>> > office. Could someone provide a bit of guidance as to how I
>> > have to set up this printer on the server for it to map back
>> > to the remote site when running in application mode. The
>> > remote site is using Windows XP Professional. The printer is
>> > a Xerox M20i.
>> >
>> > Thanks a bunch.
>> >
>> > Bob

Relevant Pages

  • Re: ASP.NET -> SQL Server : Impersonation not working!
    ... when we use implicit impersonation like: ... session which doesn't have network credential for further network hop. ... the asp.net use clientside credential to access the remote sqlserver will ... browser, when the IIS accept the clientside credential, it ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: How Can I Allow Access From The Internet to Only Selected User
    ... users, groups, client ip address ranges, client computer naming conventions ... All users can access Terminal Server from inside the network ... "select remote users" and enter in th administrators group. ...
    (microsoft.public.windows.terminal_services)
  • Re: RWW Disconnecting
    ... I understand that remote client encounts following error message when RWW ... I strongly suggest that we rerun the Configure E-mail and Internet ... 825763 How to configure Internet access in Windows Small Business Server ...
    (microsoft.public.windows.server.sbs)
  • Re: VPN on Small Business Server 2k3
    ... IP address of the internal nic on the SBS box? ... XP client that is trying to connect? ... but could not browse the network. ... > The remote client is connecting from an outside site. ...
    (microsoft.public.windows.server.sbs)
  • Re: Remote desktop over a VPN
    ... from SBS LAN client computer I can always ping to any ... client in the remote network, but just "sometimes" I can remote desktop ...
    (microsoft.public.windows.server.sbs)
Loading