H
Hugga
Hi All
Hopefully this isn't a a difficult one to answer, but I have found my
results to be inconstant with answers on the web.
Consider my setup, where I have 3 Windows XP Pro SP2 computers, with
one acting as a Host for RDP sessions at a company site. The other 2
desktops are at users' homes and therefore on completely different
subnets, however both can VPN in to the network happily and use RDP.
Windows Firewall is on.
Problem:
PC1's printer is using a "Standard TCP/IP Port" to print to a HP
JetDirect based printer. When connected to the Host via RDP, this
printer auto-creates and the port maps to TS001 (or whatever it
happens to be). This is great, no problems, and works how I want.
PC2's printer is also using a "Standard TCP/IP Port" to print to a HP
JetDirect based printer, exactly the same model as PC1. However RDP
auto-creation does not work. But, if I only change the port to be
LPT1 for the printer, the RDP auto-creation works as expected.
I cant explain why the Standard TCP/IP Port works for PC1 but not
PC2. I have checked for the FilterQueueType registry value on PC1 and
it is not there, so this cant be why it works.
My understanding is that Network printers do not redirect under RDP,
however it is my belief that the "Standard TCP/IP Port" is NOT a
network printer; it is a Local Port which points elsewhere and should
redirect (despite Microsoft articles saying it wont redirect a port if
it doesn't start with LPT, COM or USB)
What could be wrong with PC2? I have tried printer drivers,
recreating printers and ports, etc to no avail. Redirection is
obviously working but just not for this port type and I'm stumped if I
know why.
I hope someone can help
Hopefully this isn't a a difficult one to answer, but I have found my
results to be inconstant with answers on the web.
Consider my setup, where I have 3 Windows XP Pro SP2 computers, with
one acting as a Host for RDP sessions at a company site. The other 2
desktops are at users' homes and therefore on completely different
subnets, however both can VPN in to the network happily and use RDP.
Windows Firewall is on.
Problem:
PC1's printer is using a "Standard TCP/IP Port" to print to a HP
JetDirect based printer. When connected to the Host via RDP, this
printer auto-creates and the port maps to TS001 (or whatever it
happens to be). This is great, no problems, and works how I want.
PC2's printer is also using a "Standard TCP/IP Port" to print to a HP
JetDirect based printer, exactly the same model as PC1. However RDP
auto-creation does not work. But, if I only change the port to be
LPT1 for the printer, the RDP auto-creation works as expected.
I cant explain why the Standard TCP/IP Port works for PC1 but not
PC2. I have checked for the FilterQueueType registry value on PC1 and
it is not there, so this cant be why it works.
My understanding is that Network printers do not redirect under RDP,
however it is my belief that the "Standard TCP/IP Port" is NOT a
network printer; it is a Local Port which points elsewhere and should
redirect (despite Microsoft articles saying it wont redirect a port if
it doesn't start with LPT, COM or USB)
What could be wrong with PC2? I have tried printer drivers,
recreating printers and ports, etc to no avail. Redirection is
obviously working but just not for this port type and I'm stumped if I
know why.
I hope someone can help