passing local printers through remote desktop

  • Thread starter Thread starter Thomas Juracek
  • Start date Start date
T

Thomas Juracek

Guest
I cannot get local printers to pass through a remote desktop session unless
(I surmise) the non-routable IP networks are the same. Is there a way around
this, or do I need to configure all my domains with the same non-routable IP
address scheme to allow a local printer to be used in a RDP session? The
same prohibition appears to apply to the copy/paste commands when applied at
the file level.

Thank you for you help.
--
Tom Juracek
 
Re: passing local printers through remote desktop

Redirecting printers doesn't rely on the IP schedme at all. What errors are
you receiving in the event logs of the server and workstation? How are you
testing this? Print drivers are installed on the terminal server? the
check box to redirect printers is checked?

Jeff Pitsch
Microsoft MVP - Terminal Services

"Thomas Juracek" <ThomasJuracek@discussions.microsoft.com> wrote in message
news:05AF9E92-5BAF-41D8-AADD-E07D361FF0E1@microsoft.com...
>I cannot get local printers to pass through a remote desktop session unless
> (I surmise) the non-routable IP networks are the same. Is there a way
> around
> this, or do I need to configure all my domains with the same non-routable
> IP
> address scheme to allow a local printer to be used in a RDP session? The
> same prohibition appears to apply to the copy/paste commands when applied
> at
> the file level.
>
> Thank you for you help.
> --
> Tom Juracek
 
Re: passing local printers through remote desktop

When I go to select a printer, it should appear as (PrinterX on Laptop) in
the printer selection box. Instead it is not listed at all. When I am at
one office, my local IP address is 192.168.x.x. This is consistent with the
IP scheme where the RDP is being run.

When I go to a second office, the IP scheme is 172.16.172.x and running
everything exactly the same results in a local printer not showing in the
printer selection box.

Thanks
--
Tom Juracek


"Jeff Pitsch" wrote:

> Redirecting printers doesn't rely on the IP schedme at all. What errors are
> you receiving in the event logs of the server and workstation? How are you
> testing this? Print drivers are installed on the terminal server? the
> check box to redirect printers is checked?
>
> Jeff Pitsch
> Microsoft MVP - Terminal Services
>
> "Thomas Juracek" <ThomasJuracek@discussions.microsoft.com> wrote in message
> news:05AF9E92-5BAF-41D8-AADD-E07D361FF0E1@microsoft.com...
> >I cannot get local printers to pass through a remote desktop session unless
> > (I surmise) the non-routable IP networks are the same. Is there a way
> > around
> > this, or do I need to configure all my domains with the same non-routable
> > IP
> > address scheme to allow a local printer to be used in a RDP session? The
> > same prohibition appears to apply to the copy/paste commands when applied
> > at
> > the file level.
> >
> > Thank you for you help.
> > --
> > Tom Juracek
>
>
>
 
Re: passing local printers through remote desktop

And from both offices, you are connecting to the same terminal
Server?
Have you checked the EventLog on the server from errors or warnings?
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?VGhvbWFzIEp1cmFjZWs=?=
<ThomasJuracek@discussions.microsoft.com> wrote on 24 jul 2008 in
microsoft.public.windows.terminal_services:

> When I go to select a printer, it should appear as (PrinterX on
> Laptop) in the printer selection box. Instead it is not listed
> at all. When I am at one office, my local IP address is
> 192.168.x.x. This is consistent with the IP scheme where the
> RDP is being run.
>
> When I go to a second office, the IP scheme is 172.16.172.x and
> running everything exactly the same results in a local printer
> not showing in the printer selection box.
>
> Thanks
 
Re: passing local printers through remote desktop

Yes. I am using the same laptop from both locations, connecting to the same
terminal, running the same program. There are only two differences between
the locations I am aware of. First, at the terminal server location the IP
scheme is 192.168.x.x and the terminal server is part of a domain. AT my
location number 1, I have a small wireless network that uses the same
192.168.x.x IP scheme and no domain. Everything works grand. At location
number 2, IP address sceme is 172.16.172.x and there is a domain at this
location. Crazy thing, my computer is part of the domain at the second
location. At location 2, I can print to the printer directly from my
desktop, but once in Remote Desktop, that same printer is no longer available.

Does this help?
--
Tom Juracek


"Vera Noest [MVP]" wrote:

> And from both offices, you are connecting to the same terminal
> Server?
> Have you checked the EventLog on the server from errors or warnings?
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private email ___
>
> =?Utf-8?B?VGhvbWFzIEp1cmFjZWs=?=
> <ThomasJuracek@discussions.microsoft.com> wrote on 24 jul 2008 in
> microsoft.public.windows.terminal_services:
>
> > When I go to select a printer, it should appear as (PrinterX on
> > Laptop) in the printer selection box. Instead it is not listed
> > at all. When I am at one office, my local IP address is
> > 192.168.x.x. This is consistent with the IP scheme where the
> > RDP is being run.
> >
> > When I go to a second office, the IP scheme is 172.16.172.x and
> > running everything exactly the same results in a local printer
> > not showing in the printer selection box.
> >
> > Thanks
>
 
Re: passing local printers through remote desktop

again, IP scheme has nothing to do with redirection at all. None, zero,
zilch. People connect from all over the world to terminal services and
print just fine. that would be impossible if printing was in some way
related to IP schemes.

You have yet to answer if there are any events in the event logs. My guess
is you'll come across something there.

Jeff Pitsch
Microsoft MVP - Terminal Services


"Thomas Juracek" <ThomasJuracek@discussions.microsoft.com> wrote in message
news:AB25AA35-5D76-45F1-A6FA-CA312A1F5340@microsoft.com...
> Yes. I am using the same laptop from both locations, connecting to the
> same
> terminal, running the same program. There are only two differences
> between
> the locations I am aware of. First, at the terminal server location the
> IP
> scheme is 192.168.x.x and the terminal server is part of a domain. AT my
> location number 1, I have a small wireless network that uses the same
> 192.168.x.x IP scheme and no domain. Everything works grand. At location
> number 2, IP address sceme is 172.16.172.x and there is a domain at this
> location. Crazy thing, my computer is part of the domain at the second
> location. At location 2, I can print to the printer directly from my
> desktop, but once in Remote Desktop, that same printer is no longer
> available.
>
> Does this help?
> --
> Tom Juracek
>
>
> "Vera Noest [MVP]" wrote:
>
>> And from both offices, you are connecting to the same terminal
>> Server?
>> Have you checked the EventLog on the server from errors or warnings?
>> _________________________________________________________
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>> TS troubleshooting: http://ts.veranoest.net
>> ___ please respond in newsgroup, NOT by private email ___
>>
>> =?Utf-8?B?VGhvbWFzIEp1cmFjZWs=?=
>> <ThomasJuracek@discussions.microsoft.com> wrote on 24 jul 2008 in
>> microsoft.public.windows.terminal_services:
>>
>> > When I go to select a printer, it should appear as (PrinterX on
>> > Laptop) in the printer selection box. Instead it is not listed
>> > at all. When I am at one office, my local IP address is
>> > 192.168.x.x. This is consistent with the IP scheme where the
>> > RDP is being run.
>> >
>> > When I go to a second office, the IP scheme is 172.16.172.x and
>> > running everything exactly the same results in a local printer
>> > not showing in the printer selection box.
>> >
>> > Thanks
>>
 
Re: passing local printers through remote desktop

OK, thanks Jeff. I am not really sure where to look, so I have the event
viewer open on my local machine. I assume I want to look at the log under
Microsoft that gets to Terminal Services - RDP. I will log onto all systems
right now and see if any messages are generated. Unfortunately, I am at the
location where everything has worked in the past, so may not get an error
message. Will post again shortly.
--
Tom Juracek


"Jeff Pitsch" wrote:

> again, IP scheme has nothing to do with redirection at all. None, zero,
> zilch. People connect from all over the world to terminal services and
> print just fine. that would be impossible if printing was in some way
> related to IP schemes.
>
> You have yet to answer if there are any events in the event logs. My guess
> is you'll come across something there.
>
> Jeff Pitsch
> Microsoft MVP - Terminal Services
>
>
> "Thomas Juracek" <ThomasJuracek@discussions.microsoft.com> wrote in message
> news:AB25AA35-5D76-45F1-A6FA-CA312A1F5340@microsoft.com...
> > Yes. I am using the same laptop from both locations, connecting to the
> > same
> > terminal, running the same program. There are only two differences
> > between
> > the locations I am aware of. First, at the terminal server location the
> > IP
> > scheme is 192.168.x.x and the terminal server is part of a domain. AT my
> > location number 1, I have a small wireless network that uses the same
> > 192.168.x.x IP scheme and no domain. Everything works grand. At location
> > number 2, IP address sceme is 172.16.172.x and there is a domain at this
> > location. Crazy thing, my computer is part of the domain at the second
> > location. At location 2, I can print to the printer directly from my
> > desktop, but once in Remote Desktop, that same printer is no longer
> > available.
> >
> > Does this help?
> > --
> > Tom Juracek
> >
> >
> > "Vera Noest [MVP]" wrote:
> >
> >> And from both offices, you are connecting to the same terminal
> >> Server?
> >> Have you checked the EventLog on the server from errors or warnings?
> >> _________________________________________________________
> >> Vera Noest
> >> MCSE, CCEA, Microsoft MVP - Terminal Server
> >> TS troubleshooting: http://ts.veranoest.net
> >> ___ please respond in newsgroup, NOT by private email ___
> >>
> >> =?Utf-8?B?VGhvbWFzIEp1cmFjZWs=?=
> >> <ThomasJuracek@discussions.microsoft.com> wrote on 24 jul 2008 in
> >> microsoft.public.windows.terminal_services:
> >>
> >> > When I go to select a printer, it should appear as (PrinterX on
> >> > Laptop) in the printer selection box. Instead it is not listed
> >> > at all. When I am at one office, my local IP address is
> >> > 192.168.x.x. This is consistent with the IP scheme where the
> >> > RDP is being run.
> >> >
> >> > When I go to a second office, the IP scheme is 172.16.172.x and
> >> > running everything exactly the same results in a local printer
> >> > not showing in the printer selection box.
> >> >
> >> > Thanks
> >>
>
>
>
 
Re: passing local printers through remote desktop

I just attempted a print and it worked from the same location that it usually
works from. I am running the remote desktop on a Windows XP computer (this
is the computer I am taking over to execute the software I want to run). My
computer (the laptop I am actually typing on) is Windows Vista, but I don't
think that makes any difference.

The XP computer does not appear to have an event log that I can find. Does
it need to be enabled?
--
Tom Juracek


"Jeff Pitsch" wrote:

> again, IP scheme has nothing to do with redirection at all. None, zero,
> zilch. People connect from all over the world to terminal services and
> print just fine. that would be impossible if printing was in some way
> related to IP schemes.
>
> You have yet to answer if there are any events in the event logs. My guess
> is you'll come across something there.
>
> Jeff Pitsch
> Microsoft MVP - Terminal Services
>
>
> "Thomas Juracek" <ThomasJuracek@discussions.microsoft.com> wrote in message
> news:AB25AA35-5D76-45F1-A6FA-CA312A1F5340@microsoft.com...
> > Yes. I am using the same laptop from both locations, connecting to the
> > same
> > terminal, running the same program. There are only two differences
> > between
> > the locations I am aware of. First, at the terminal server location the
> > IP
> > scheme is 192.168.x.x and the terminal server is part of a domain. AT my
> > location number 1, I have a small wireless network that uses the same
> > 192.168.x.x IP scheme and no domain. Everything works grand. At location
> > number 2, IP address sceme is 172.16.172.x and there is a domain at this
> > location. Crazy thing, my computer is part of the domain at the second
> > location. At location 2, I can print to the printer directly from my
> > desktop, but once in Remote Desktop, that same printer is no longer
> > available.
> >
> > Does this help?
> > --
> > Tom Juracek
> >
> >
> > "Vera Noest [MVP]" wrote:
> >
> >> And from both offices, you are connecting to the same terminal
> >> Server?
> >> Have you checked the EventLog on the server from errors or warnings?
> >> _________________________________________________________
> >> Vera Noest
> >> MCSE, CCEA, Microsoft MVP - Terminal Server
> >> TS troubleshooting: http://ts.veranoest.net
> >> ___ please respond in newsgroup, NOT by private email ___
> >>
> >> =?Utf-8?B?VGhvbWFzIEp1cmFjZWs=?=
> >> <ThomasJuracek@discussions.microsoft.com> wrote on 24 jul 2008 in
> >> microsoft.public.windows.terminal_services:
> >>
> >> > When I go to select a printer, it should appear as (PrinterX on
> >> > Laptop) in the printer selection box. Instead it is not listed
> >> > at all. When I am at one office, my local IP address is
> >> > 192.168.x.x. This is consistent with the IP scheme where the
> >> > RDP is being run.
> >> >
> >> > When I go to a second office, the IP scheme is 172.16.172.x and
> >> > running everything exactly the same results in a local printer
> >> > not showing in the printer selection box.
> >> >
> >> > Thanks
> >>
>
>
>
 
Re: passing local printers through remote desktop

Third post this morning, I found the event viewer...will report
momentarily.....

Found nothing in the event logs. What I did find was that printers that are
passed through eventually show up as purged and deleted when the RDP session
has ended. But there is no indication that any printers are connected.

Maybe I am looking in wrond location, but I checked all three logs.

I am sure this is somehow related to the inability to copy entire files
between the remote desktop and the local desktop. Must have something to do
with passing through permissions, maybe?

Just seems strange that it works in one location and not another. Could it
be a permissions issue in the second location?
--
Tom Juracek


"Jeff Pitsch" wrote:

> again, IP scheme has nothing to do with redirection at all. None, zero,
> zilch. People connect from all over the world to terminal services and
> print just fine. that would be impossible if printing was in some way
> related to IP schemes.
>
> You have yet to answer if there are any events in the event logs. My guess
> is you'll come across something there.
>
> Jeff Pitsch
> Microsoft MVP - Terminal Services
>
>
> "Thomas Juracek" <ThomasJuracek@discussions.microsoft.com> wrote in message
> news:AB25AA35-5D76-45F1-A6FA-CA312A1F5340@microsoft.com...
> > Yes. I am using the same laptop from both locations, connecting to the
> > same
> > terminal, running the same program. There are only two differences
> > between
> > the locations I am aware of. First, at the terminal server location the
> > IP
> > scheme is 192.168.x.x and the terminal server is part of a domain. AT my
> > location number 1, I have a small wireless network that uses the same
> > 192.168.x.x IP scheme and no domain. Everything works grand. At location
> > number 2, IP address sceme is 172.16.172.x and there is a domain at this
> > location. Crazy thing, my computer is part of the domain at the second
> > location. At location 2, I can print to the printer directly from my
> > desktop, but once in Remote Desktop, that same printer is no longer
> > available.
> >
> > Does this help?
> > --
> > Tom Juracek
> >
> >
> > "Vera Noest [MVP]" wrote:
> >
> >> And from both offices, you are connecting to the same terminal
> >> Server?
> >> Have you checked the EventLog on the server from errors or warnings?
> >> _________________________________________________________
> >> Vera Noest
> >> MCSE, CCEA, Microsoft MVP - Terminal Server
> >> TS troubleshooting: http://ts.veranoest.net
> >> ___ please respond in newsgroup, NOT by private email ___
> >>
> >> =?Utf-8?B?VGhvbWFzIEp1cmFjZWs=?=
> >> <ThomasJuracek@discussions.microsoft.com> wrote on 24 jul 2008 in
> >> microsoft.public.windows.terminal_services:
> >>
> >> > When I go to select a printer, it should appear as (PrinterX on
> >> > Laptop) in the printer selection box. Instead it is not listed
> >> > at all. When I am at one office, my local IP address is
> >> > 192.168.x.x. This is consistent with the IP scheme where the
> >> > RDP is being run.
> >> >
> >> > When I go to a second office, the IP scheme is 172.16.172.x and
> >> > running everything exactly the same results in a local printer
> >> > not showing in the printer selection box.
> >> >
> >> > Thanks
> >>
>
>
>
 
Re: passing local printers through remote desktop

You looked at the server logs correct? Are you the administrator of these
machines? If you log into the server as an admin can you see any
redirected printers from that session? yes, you will have to get help to
troubleshoot this from a second party. What permissions? You said the one
site that doesn't work doesn't belong to a Active Directory domain. If it
did, I would say look to see if there are any GPO's affecting the site (if
it's a separate site in AD).

How are you trying to copy files? Over copy/paste or drive redirection?
You can't copy files over copy/paste, that has to be done through drive
redirection.
"Thomas Juracek" <ThomasJuracek@discussions.microsoft.com> wrote in message
news:992CE047-F6EF-449D-AA93-85D169826252@microsoft.com...
> Third post this morning, I found the event viewer...will report
> momentarily.....
>
> Found nothing in the event logs. What I did find was that printers that
> are
> passed through eventually show up as purged and deleted when the RDP
> session
> has ended. But there is no indication that any printers are connected.
>
> Maybe I am looking in wrond location, but I checked all three logs.
>
> I am sure this is somehow related to the inability to copy entire files
> between the remote desktop and the local desktop. Must have something to
> do
> with passing through permissions, maybe?
>
> Just seems strange that it works in one location and not another. Could
> it
> be a permissions issue in the second location?
> --
> Tom Juracek
>
>
> "Jeff Pitsch" wrote:
>
>> again, IP scheme has nothing to do with redirection at all. None, zero,
>> zilch. People connect from all over the world to terminal services and
>> print just fine. that would be impossible if printing was in some way
>> related to IP schemes.
>>
>> You have yet to answer if there are any events in the event logs. My
>> guess
>> is you'll come across something there.
>>
>> Jeff Pitsch
>> Microsoft MVP - Terminal Services
>>
>>
>> "Thomas Juracek" <ThomasJuracek@discussions.microsoft.com> wrote in
>> message
>> news:AB25AA35-5D76-45F1-A6FA-CA312A1F5340@microsoft.com...
>> > Yes. I am using the same laptop from both locations, connecting to the
>> > same
>> > terminal, running the same program. There are only two differences
>> > between
>> > the locations I am aware of. First, at the terminal server location
>> > the
>> > IP
>> > scheme is 192.168.x.x and the terminal server is part of a domain. AT
>> > my
>> > location number 1, I have a small wireless network that uses the same
>> > 192.168.x.x IP scheme and no domain. Everything works grand. At
>> > location
>> > number 2, IP address sceme is 172.16.172.x and there is a domain at
>> > this
>> > location. Crazy thing, my computer is part of the domain at the second
>> > location. At location 2, I can print to the printer directly from my
>> > desktop, but once in Remote Desktop, that same printer is no longer
>> > available.
>> >
>> > Does this help?
>> > --
>> > Tom Juracek
>> >
>> >
>> > "Vera Noest [MVP]" wrote:
>> >
>> >> And from both offices, you are connecting to the same terminal
>> >> Server?
>> >> Have you checked the EventLog on the server from errors or warnings?
>> >> _________________________________________________________
>> >> Vera Noest
>> >> MCSE, CCEA, Microsoft MVP - Terminal Server
>> >> TS troubleshooting: http://ts.veranoest.net
>> >> ___ please respond in newsgroup, NOT by private email ___
>> >>
>> >> =?Utf-8?B?VGhvbWFzIEp1cmFjZWs=?=
>> >> <ThomasJuracek@discussions.microsoft.com> wrote on 24 jul 2008 in
>> >> microsoft.public.windows.terminal_services:
>> >>
>> >> > When I go to select a printer, it should appear as (PrinterX on
>> >> > Laptop) in the printer selection box. Instead it is not listed
>> >> > at all. When I am at one office, my local IP address is
>> >> > 192.168.x.x. This is consistent with the IP scheme where the
>> >> > RDP is being run.
>> >> >
>> >> > When I go to a second office, the IP scheme is 172.16.172.x and
>> >> > running everything exactly the same results in a local printer
>> >> > not showing in the printer selection box.
>> >> >
>> >> > Thanks
>> >>
>>
>>
>>
 
Back
Top