Re: Printing on W3K Terminal Services Client Printers

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Gaurav,
As you can see by my post "Dial Up Client printer problem" on 2-12-2006 the
Dial Up connection does not work even though it works via CAT5 connection.

Thanks
Bruce

"Gaurav Daga [MSFT]" <gauravd@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:OHTO8jPMGHA.3260@xxxxxxxxxxxxxxxxxxxxxxx
Yes - the functionality is agnostic of the type of network connection.

"Bruce P. Barrett" <brucepbarrett@xxxxxxxxxxxx> wrote in message
news:Ba6dnaLzN9tponDeRVn-sg@xxxxxxxxxxxxxxx
Gaurav,
Thanks. I can handle that, as I was anticipating your response.

If possible I would like to know if everything that works when the
Clients are connected via Ethernet
will work the same when we change the connection to dial-up modem???
Clients use XP Home and the server is the Windows 2003 Enterprise
Edition.
Thanks
Bruce


"Gaurav Daga [MSFT]" <gauravd@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:ev3POSqLGHA.2604@xxxxxxxxxxxxxxxxxxxxxxx
If the Clients are disconnected randomly, there is no way for a spooled
job to be sent to the right intended printer on the right Client upon
reconnect. This is because even if the same Client reconnects, it does
so on a different virtual port every time, and the spooler has no way to
associate the pending job to the right printer on this Client.

One thing you could do if you anticipate frequent loss in connections is
spool your print jobs to a file and then print from the file to the
printer. This will obviously require some change to your script/app, but
will give you the flexibility of restarting the print job on the same
Client on the same printer on which it was printing to originally before
the connection got dropped.

"Bruce P. Barrett" <brucepbarrett@xxxxxxxxxxxx> wrote in message
news:NrGdnawOJOcZSHHenZ2dnUVZ_vmdnZ2d@xxxxxxxxxxxxxxx
Gaurav,
Thanks for the reply.
I just got back from testing with the Clients connected via Ethernet.

I deleted all printers on the clients and server. I then added the
printers to the clients and server. Jobs were created and sent to the
appropriate printer with everything working as expected.

I then restarted the server and all of the printers appeared after a
short wait.

I then sent job to each printer and everything worked as expected.

Because we will be using dial-up where connections are lost frequently
I disconnected one of the Clients and I received an error stating that
the printer could not be initialized.
Is there any way to cause the job to be spooled and then printed when
the printer is reconnected???

Assuming that everything works when the Clients are connected via
Ethernet can I presume that everything will work when we change the
connection to dial-up modem??? Clients use XP Home and the server is
the Windows 2003 Enterprise Edition.
I really appreciate any help you can give me as I am struggling
Thanks
Bruce


"Gaurav Daga [MSFT]" <gauravd@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:OAwty9eLGHA.3424@xxxxxxxxxxxxxxxxxxxxxxx
What do you mean by "when you disconnected the terminal the print
output was lost"? If a print job is sent to a redirected printer on
the Client terminal, and the Client is disconnected; the job will be
interrupted. Is this what you are refering to as lost? If yes, it is
expected.

Need more details on the last part where you mention that the printers
disappeared from the Server. Is it that when you ran your BAT file on
printers redirected over the other two Client terminals, the printers
were actually no longer being redirected on the Server?

"Bruce P. Barrett" <brucepbarrett@xxxxxxxxxxxx> wrote in message
news:V-idnSFKHafOznbeRVn-qg@xxxxxxxxxxxxxxx
Sorry I didn't state the problem clearly.
I am converting a Multi-User DOS application to Windows 2003 Server
Terminal Services and need to print orders (text files with embedded
ESC sequences) on "SHARED" Star receipt printer attached to client
terminals (XP Home) over a dial up connection. The orders are
printed using the "PRINT" command in a BAT file with parameters
identifying the terminal name, printer name and file to print.
The command in the BAT file is "PRINT /d:\\W-T01\W-P01
c:\mpmf\orders\w0027.w" where W-T01 is the name of the client
terminal and W-P01 is the name of the printer attached to the
terminal.
We added the printers to the client terminals and server with the
Star drivers attached to LPT1. Initially we tested one dialup
terminal and it seemed to work except when we disconnected the
terminal and print output was lost. Further testing with 2 terminals
caused the printers to disappear from the server.
Thanks
Bruce

"Gaurav Daga [MSFT]" <gauravd@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:%23QS6MNQLGHA.2628@xxxxxxxxxxxxxxxxxxxxxxx
As long as the Client printers are being redirected on the Terminal
Server, you would not have to do anything special to setup print
queues for them. You would just need to setup print queues as you
would for locally installed printers. Did you try and does it not
work? If so, maybe I do not understand the scenario and what you are
attempting - please give step by steps on what you are attempting.

"Bruce P. Barrett" <brucepbarrett@xxxxxxxxxxxx> wrote in message
news:OfudnQsUSOOi61PeRVn-pQ@xxxxxxxxxxxxxxx
Hi,
I need to send information to a W3K Terminal Services client
printer via "Print" command. The print command is created
dynamically containing the Terminal and Printer Ids of the
appropriate printer. In those cases where the terminal is not
connected the document needs to be queued and printed when the
terminal connects.

How do I setup print queues for client printers?

Thanks
Bruce

















.

Relevant Pages

  • Re: .Net Scalability problem
    ... LoadRunner will peak out a server with a few virtual users. ... To get an idea of load, ... Fire off the test client and watch the number of ... > So I think that the MTC generate concurrent connection and per ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Connection lost at same time every hour (sometimes)
    ... After making the two following alterations on the server the problem seems ... After analyze your ipconfig on SBS and client, ... Then, other connection is good, ...
    (microsoft.public.windows.server.sbs)
  • Re: server disconnection - very often
    ... Reason of permanent popups is VMware server aplication on clients. ... Run CEICW to configure the network of SBS: ... Two network adapters - manual router connection to broadband ... Uninstall VMware on client. ...
    (microsoft.public.windows.server.sbs)
  • Re: Lan setup 2 nic
    ... The external nic only has TCP/IP enabled. ... Ipconfig of the server is looking good, but the client is still missing the ... > connection so we have a 2 nic with router setup now. ...
    (microsoft.public.windows.server.sbs)
  • Re: Regular disconnections from remote web workplace
    ... I can connect to office server and all office clients from home at all times ... be physically working right up until the connection is lost. ... If I enter http://companyip from a client I receive the login screen for the ... Click Services tab and select Hide All Microsoft Services and Disable ...
    (microsoft.public.windows.server.sbs)