Terminal Server printing issue...

[Brad Pears]

One of our dealers is having problems printing from their terminal server
session. They are using a Dell desktop, which has XP Pro installed. The
default printer is an HP LaserJet 2100 and is connected to an HP Printer
Server. in the print driver, the printer is configured as port:
IP_192.168.1.10 and is a standard TCP/IP port.

The dealer logs onto our Windows 2003 terminal server. When they log on, it
is not trying to connect a printer at all!

The dealer also has a Dell laptop they used to use to connect to us. The
laptop has Windows ME installed for the OS and has the same networked
default printer set up. When they connect to the same Windows 2003 terminal
server using this laptop, it does install the printer driver etc.. and they
can print just fine from their TS session.

I have made sure that the 'Printers' item has been selected in the RDP
connection settings on the XP Pro machine that they are unable to print
from.

I am at a loss as to why the Windows ME machine installs the printer
properly and makes it available in their TS session while the XP Pro machine
does not even attempt to install the printer - as if the 'printers' item is
not even checked!

Can anyone shed any light on this issue perhaps?

Thanks, Brad

PS... As a side note, the security tab is not available for whatever reason.
Could there be an issue with that perhaps?

[TP]

Brad,

On the XP Pro machine, please install the 5.2.3790.1830 version
of the Remote Desktop Client. The install file is located on your
2003 SP1 server here:

C:\WINDOWS\system32\clients\tsclient\win32\msrdpcli.msi

Thanks.

-TP

Post by Brad Pears
One of our dealers is having problems printing from their terminal
server session. They are using a Dell desktop, which has XP Pro
installed. The default printer is an HP LaserJet 2100 and is
connected to an HP Printer Server. in the print driver, the printer
is configured as port: IP_192.168.1.10 and is a standard TCP/IP port.
The dealer logs onto our Windows 2003 terminal server. When they log
on, it is not trying to connect a printer at all!
The dealer also has a Dell laptop they used to use to connect to us.
The laptop has Windows ME installed for the OS and has the same
networked default printer set up. When they connect to the same
Windows 2003 terminal server using this laptop, it does install the
printer driver etc.. and they can print just fine from their TS
session.
I have made sure that the 'Printers' item has been selected in the RDP
connection settings on the XP Pro machine that they are unable to
print from.
I am at a loss as to why the Windows ME machine installs the printer
properly and makes it available in their TS session while the XP Pro
machine does not even attempt to install the printer - as if the
'printers' item is not even checked!
Can anyone shed any light on this issue perhaps?
Thanks, Brad
PS... As a side note, the security tab is not available for whatever
reason. Could there be an issue with that perhaps?

[Brad Pears]

The one I have on my Win2K3 machine is not that version - it is 5.2.3790.0
(you are referring to the version of file "mstsc.exe" correct?)

Where can I get the one you are indicating - or will the one I have do?

Also, once installed on our dealers machine, will they have to delete the
connection they have configured there already and create a new connection to
ensure they are using the most recent version of mstsc.exe - or will it
automatically be using the new correct version??

As a test, I installed the more recent version on my own machine, and it did
not replace the "mstsc.exe" version that is located in windows\system32 at
all. It is still the same old version I had before installing the newer one.
If I delete that file and launch an existing remote desktop connection, a
new copy of the OLD mstsc.exe is placed back into the system32 directory
automatically!

Should I also be copying the newer mstsc.exe and the associated .dll file
from program files over to the system32 dir to prevent a screw up?

Thanks, Brad

Brad,
On the XP Pro machine, please install the 5.2.3790.1830 version of the
Remote Desktop Client. The install file is located on your 2003 SP1
C:\WINDOWS\system32\clients\tsclient\win32\msrdpcli.msi
Thanks.
-TP

Post by Brad Pears
One of our dealers is having problems printing from their terminal
server session. They are using a Dell desktop, which has XP Pro
installed. The default printer is an HP LaserJet 2100 and is
connected to an HP Printer Server. in the print driver, the printer
is configured as port: IP_192.168.1.10 and is a standard TCP/IP port.
The dealer logs onto our Windows 2003 terminal server. When they log
on, it is not trying to connect a printer at all!
The dealer also has a Dell laptop they used to use to connect to us.
The laptop has Windows ME installed for the OS and has the same
networked default printer set up. When they connect to the same
Windows 2003 terminal server using this laptop, it does install the
printer driver etc.. and they can print just fine from their TS
session. I have made sure that the 'Printers' item has been selected in
the RDP
connection settings on the XP Pro machine that they are unable to
print from.
I am at a loss as to why the Windows ME machine installs the printer
properly and makes it available in their TS session while the XP Pro
machine does not even attempt to install the printer - as if the
'printers' item is not even checked!
Can anyone shed any light on this issue perhaps?
Thanks, Brad
PS... As a side note, the security tab is not available for whatever
reason. Could there be an issue with that perhaps?

[TP]

Hi Brad,

The version you have will work. I was referring to the
2003 SP1 version. You have not installed SP1 yet?

When you install the 5.2.3790.0 version, it should
create a new shortcut that points to
C:\Program Files\Remote Desktop\mstsc.exe, as well
as re-point .rdp file association. The original mstsc.exe
version will stay in system32, no need to delete it.

If you delete or otherwise modify the version in system32,
system file protection will copy the original version back.

The newer client will use the existing connection settings,
no need to create a new connection.

-TP

Post by Brad Pears
The one I have on my Win2K3 machine is not that version - it is
5.2.3790.0 (you are referring to the version of file "mstsc.exe"
correct?)
Where can I get the one you are indicating - or will the one I have do?
Also, once installed on our dealers machine, will they have to delete
the connection they have configured there already and create a new
connection to ensure they are using the most recent version of
mstsc.exe - or will it automatically be using the new correct
version??
As a test, I installed the more recent version on my own machine, and
it did not replace the "mstsc.exe" version that is located in
windows\system32 at all. It is still the same old version I had
before installing the newer one. If I delete that file and launch an
existing remote desktop connection, a new copy of the OLD mstsc.exe
is placed back into the system32 directory automatically!
Should I also be copying the newer mstsc.exe and the associated .dll
file from program files over to the system32 dir to prevent a screw
up?
Thanks, Brad

[Brad Pears]

Thanks a lot for that - it worked!! I also found the newest RDP client -
ver 6.0 for XP SP2 machines and beyond. Do you have any comments on that
version of RDP?

Thanks Brad

Post by TP
Hi Brad,
The version you have will work. I was referring to the 2003 SP1 version.
You have not installed SP1 yet?
When you install the 5.2.3790.0 version, it should create a new shortcut
that points to C:\Program Files\Remote Desktop\mstsc.exe, as well as
re-point .rdp file association. The original mstsc.exe version will stay
in system32, no need to delete it.
If you delete or otherwise modify the version in system32, system file
protection will copy the original version back.
The newer client will use the existing connection settings, no need to
create a new connection.
-TP

Post by Brad Pears
The one I have on my Win2K3 machine is not that version - it is
5.2.3790.0 (you are referring to the version of file "mstsc.exe"
correct?) Where can I get the one you are indicating - or will the one I
have
do? Also, once installed on our dealers machine, will they have to delete
the connection they have configured there already and create a new
connection to ensure they are using the most recent version of
mstsc.exe - or will it automatically be using the new correct
version?? As a test, I installed the more recent version on my own
machine, and
it did not replace the "mstsc.exe" version that is located in
windows\system32 at all. It is still the same old version I had
before installing the newer one. If I delete that file and launch an
existing remote desktop connection, a new copy of the OLD mstsc.exe
is placed back into the system32 directory automatically!
Should I also be copying the newer mstsc.exe and the associated .dll
file from program files over to the system32 dir to prevent a screw
up? Thanks, Brad

[TP]

It has some bugs and different behavior. These two
combine to create net effects of reduced usability,
confused users, and increased help desk calls.

I generally only recommend it to people who need to
use the new features available when connecting to
Vista or Longhorn Server.

-TP

Post by Brad Pears
Thanks a lot for that - it worked!! I also found the newest RDP
client - ver 6.0 for XP SP2 machines and beyond. Do you have any
comments on that version of RDP?
Thanks Brad

[Brad Pears]

Thanks for that!

It has some bugs and different behavior. These two combine to create net
effects of reduced usability, confused users, and increased help desk
calls.
I generally only recommend it to people who need to use the new features
available when connecting to Vista or Longhorn Server.
-TP

Post by Brad Pears
Thanks a lot for that - it worked!! I also found the newest RDP
client - ver 6.0 for XP SP2 machines and beyond. Do you have any
comments on that version of RDP?
Thanks Brad