I'm not sure I understand the situation correctly. Is this what you are
describing:
1. a Windows 2003 Server running terminal services
2. three client computers, #1 running Windows NT 4.0, #2 running Windows
2000 and #3 running Windows XP?
3. All three clients have a local printer that is on a TCP/IP port that is
associated with a printer on a LAN adapter (either internal or external).
Note that Windows 2000, XP and 2003 all have a "Standard TCP/IP" port type.
Windows NT 4.0 does not, but if you have Print Services for Unix installed,
you could have a printer the printer on an LPR port.
4. you can print from each of the clients to the printer
5. if you logon at client #3, then use Remote Desktop Client to open a
Terminal Services Session on the Windows 2003 server, the local printer is
available in the Terminal Services session and you can print on it
successfully.
6. if you logon at client #1 or #2, then use Remote Desktop Client to open a
Terminal Services Session on the Windows 2003 server, the local printer does
not appear and so you can't print on it.
Is this your situation?
Things to verify:
a. check that all three clients have the current Remote Desktop Client
software - see
http://www.microsoft.com/downloads/...fc-4b4a-40e7-a706-cde7e9b57e79&DisplayLang=en
b. check that the Option to map local printers is selected in the RDP
client:
i. click the Options>> button on the RDP client window (before
connecting)
ii. select the Local Resources tab
iii. make sure there is a check mark beside "Printers" in the "Local
devices" frame
iv. if you made any changes to the Options, select the General tab and
click Save As... (you can either replace the existing .rdp file or create a
new one).
c. on the Windows 2003 server, check the System Event Log for entries with
"Source" of "TermServDevices". These log entries describe problems
associated with mapping client devices (e.g. local printers) into Terminal
Services sessions.
If you see some of these, then most likely the Windows 2003 server does not
have the printer driver installed that matches the printer driver installed
on the #1 and #2 clients.
Managing printer drivers is often a big headache with Terminal Services.
One solution you might try is to add the printer as a local printer on the
Windows 2003 Server using a Standard TCP/IP port. Then, the printer will be
available to all Terminal Services sessions. In a small environment, this
may be a viable solution, although some terminal server gurus might tell you
this is a bad choice.
With the Windows 2000 clients, you could try to install the same driver that
is used on the Windows XP and Windows 2003 server onto those clients.
Drivers for Windows XP will normally work on Windows 2000.
The Windows NT 4.0 clients are more difficult, because the "Version 3"
driver model supported on Windows 2000 and Windows XP won't work on Windows
NT 4.0. If at all possible, upgrade these to Windows 2000 or Windows XP as
this will considerably reduce problems, particularly with printing.
See if there is any help on this in the
microsoft.public.windows.terminalservices or
microsoft.public.win2000.termserv.clients news groups - there's some pretty
knowledgeable people that post there.
If you post again, please state the make and model of the printer - printer
drivers are often very idiosyncratic, so knowing which printer is involved
might get you more specific help.
