RE: Externe toegang SBS




Hi,

Thanks for your post.

I just found you have submitted a similar post on Feb 11 with the subject "
Extern bureaublad ". Our engineer Miles Li has replied to you with
corresponding suggestions but didn't have your reply in that post.
Therefore, in case you missed Miles's reply on Feb 11, I would like to past
it again as below for your reference.

If you have any feedback or need further assistance from us, please feel
free to post back in this new post. Miles is on a short vacation and will
be right back tomorrow to follow up with you. Thanks for your time and
understanding.


Miles's Reply on Feb 11
+++++++++++++++++++++++++++
From: Miles Li [MSFT]
Date: Wed, 11 Feb 2009 10:16:26 GMT
Subject: RE: Extern bureaublad
Newsgroups: microsoft.public.windows.server.sbs


Hello,

Thank you for posting here.

As you know, the redirected port is generated dynamically with the format
TSXXX. The system controls the port creation and deletion automatically. In
this way, terminal services can ensure that port name is not duplicated for
ports from different terminal sessions. Unfortunately, we cannot configure
the redirected port to have fixed name. As mentioned in the following
Microsoft Knowledge article, the manually created printer is only useful
for a currently running RDP session. The printer should be deleted after
the session logoff. Thank you for your understanding.

How To Manually Add a Redirected Client Printer Using Terminal Services
http://support.microsoft.com/?id=243552

Before we go any further, I'd like to know the reason that you would like
to configure a fixed port. By default, the dynamic port will not prevent us
from printing to a local printer in a terminal session. When local printer
is redirected to the terminal server, a printer is automatically created in
the terminal session and you do not need to add printer manually. In order
to let the printer redirection work in the Windows 2003 terminal server,
you must meet the following requirement:

1. You must enable the printer redirection on the RDP client.
(Start the RDP client with the command MSTSC, Options => "local resources"
=> check the options of the "printers")

2. You must enable the printer redirection on the terminal server.
Start => Terminal Services Configuration => Connections => Double click on
"RDP-TCP", click "Client Settings", and make sure the following check boxes
had NOT been checked in the "Disable the following" tab:
Windows Printer Mapping
LPT/COM port Mapping

3. Use Windows Server 2003 RDP client
Windows 2000 terminal server does not allow network printer to be
redirected. Fortunately, Windows 2003 Terminal server allows it by default.
To use this feature, please install and use the Windows Server 2003 Remote
Desktop client from the following folder on the terminal server:
drive:\%systemroot%\System32\Clients\Tsclient\Win32.

264039 Windows 2000 Terminal Services does not redirect network printers
http://support.microsoft.com/?id=264039

4. On the terminal server, you must have the corresponding printer drivers
installed.
When a client logs on, the Windows 2003-based server checks, the name of
the printer driver on the client and looks for the same printer driver name
in the Windows 2000 Ntprint.inf file. If the name of the driver is not
found, the error messages are logged and the printer is not redirected. So
you must have the corresponding printer drivers with the same name
installed on the terminal server. For more information, please refer to the
following Microsoft Knowledge Base article:

Windows 2000 Terminal Services Server Logs Events 1111, 1105, and 1106
http://support.microsoft.com/default.aspx?scid=kb;EN-US;239088

A new tool for this issue: Terminal Server Printer Driver Redirection Wizard

This tool will examine a remote or local Terminal Server and determine
whether or not printer redirection has failed. For each printer driver that
failed redirection, the tool will prompt the user to select an installed
driver to create a new NTPrintSubs.inf file. This also integrates with a
new Windows Server 2003 SP1 Group Policy to address printer redirection
issues. This is an automation of the KB article 239088 entitled "Windows
2000 Terminal Services Server Logs Events 1111, 1105, and 1106".

You can get the tool from:
http://download.microsoft.com/download/9/f/2/9f237742-e057-4e00-a0d5-62de2eb
f9fbd/TSPDRW_Package.exe

5. Printer redirection does not work with the DOT4 port printers.
By default, printer port names that do not begin with COM, LPT, or USB are
only redirected in Windows Server 2003. By default, multifunction print
devices may not be redirected unless you are running Windows Server 2003
on your local computer because they use DOT4 ports.

You can take a look at the following URL for more information of this
issue:

302361 Printers That Use Ports That Do Not Begin With COM, LPT, or USB Are
Not
http://support.microsoft.com/?id=302361

I hope that the above information can be of assistance. If the problem
continues, please collect the following information so that I can perform
further research on this issue:

1. What is the model of the problematic printer?
2. Can other printers of other customers be redirected to the terminal
server properly?
3. Which port does the problematic printer use?
4. Please perform the following steps to collect the MPSReport of the
terminal server:

1) Download the MPSRPT_SETUPPerf.EXE file from the following website:

http://www.microsoft.com/downloads/details.aspx?FamilyId=CEBF3C7C-7CA5-408F-
88B7-F9C79B7306C0&displaylang=en

2) Double-click to run the MPSRPT_SETUPPerf.EXE file and wait for it to
complete.
3) Send me the .cab file generated in the following folder:
systemroot%\MPSReports\Setup\<Report Type>\Cab

If anything is unclear, please feel free to let me know. I am glad to be of
assistance.


Best regards,
Miles Li

Microsoft Online Partner Support
Microsoft Global Technical Support Center

Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

+++++++++++++++++++++++++++

Thank you for your time and cooperation.


Best regards,
Robbin Meng(MSFT)
Microsoft CSS Online Newsgroup Support

.



Relevant Pages

  • Re: Publishing Windows 2000 Terminal Server on another port
    ... port 9999. ... And then also publish an internal Windows 2003 Terminal Server on RDP ...
    (microsoft.public.windows.server.sbs)
  • Re: How to control the Scanner which connect with a Thin Terminal?
    ... > For TWAIN Redirection on a thin-client device, you MUST use XPe, unless ... > someone has come out with Linux or CE scanner drivers that I'm unaware of. ... >> port. ... >> accessible by terminal server users. ...
    (microsoft.public.windows.terminal_services)
  • Re: Serial port redirection
    ... Does anyone know if you have to use windows 2003 in order ... If you use Windows 2003 and the latest rdp client, ... >COM port, and expects an acknowledgement. ... >MCSE, CCEA, Microsoft MVP - Terminal Server ...
    (microsoft.public.windows.terminal_services)
  • Re: How to control the Scanner which connect with a Thin Terminal?
    ... For TWAIN Redirection on a thin-client device, you MUST use XPe, unless ... someone has come out with Linux or CE scanner drivers that I'm unaware of. ... Microsoft MVP - Terminal Server ... > rdp or ica session, when they are connected to an USB port, but ...
    (microsoft.public.windows.terminal_services)
  • RE: Extern bureaublad
    ... The system controls the port creation and deletion automatically. ... to let the printer redirection work in the Windows 2003 terminal server, ... You must enable the printer redirection on the RDP client. ... Windows Printer Mapping ...
    (microsoft.public.windows.server.sbs)

Quantcast