Re: RWW/RDP Client Software?
- From: Richard K <RichardK@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sun, 15 Jun 2008 06:24:01 -0700
Larry, you are correct in everything you state. To clarify Computer C it too
is a remote computer with it's own local printers. When computer C connects
to Computer A I can see the printers on computer C.... all of the printers.
The printers on computer C are a mix of local (USB) and network printers and
not the same as on computer A. The key is I can see ALL of the printers.
As to Franks's point the Samsung ML2510 connected to Computer A is a USB
connection.
"Larry Struckmeyer [SBS-MVP]" wrote:
Richard:.
There is still some confusion in my understanding of what you are reporting.
Please clarify if the following is not correct.
Computer A (remote, XP Home) connects to Workstation B via the Connect to My
PC on RWW, and *cannot* print to Printer X or Printer Y which are installed
on Computer A, and both of which are USB devices, neither of which have ever
been installed on Workstation B.
Now, Computer C (remote, OS ??) connects to Workstation (same or different
????) via the Connect to My PC on RWW and *can* print to Printer (same or
different ????), which is or is not USB, installed on Computer C, and which
has or has not been installed on Workstation ????.
In my brief experience, the *exact* printer driver, with the *exact* name
(the device name, not the description), must exist on both computers, the
one you RDP from and the one you RDP to.
This can be tricky, as some USB devices will only install if the software is
installed and then the device is physically attached, and some will only
install if the device is physically attached and then the software is
installed.
--
Larry
Please post the resolution to
your issue so that all can benefit.
"Richard K" <RichardK@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:F91615B2-F1FF-4724-8DA1-DF94C625CF1D@xxxxxxxxxxxxxxxx
OK, following up from Cliff.... Yes I go to servername.domain.com\remote,
then log in, then select "Connect to client computer". Going the \remote
route is RWW to me vs. going the Remote Desktop Connection-RDC
(Accessories\communication) route directly to the server.
The first printer I tried to connect is a multi-function device and I know
people have talked about problems there. The 2nd printer is a Samsung
ML2510
laser via USB (laser printing only). I was also curious about the latest
service packs/updates on the home computer because as I said when I do
this
from another home computer then printers map. To me that spells the
server
and office computer are fine, it's THIS particualar Windows XP home
computer
that has the problem.
I did notice in the logs on the office computer where it talks about
missing
drivers when connecting so I installed the drivers on the office computer
but
still get the same messages. I am trying the route of this home computer
needs some updates in terms of service packs, windows update etc. I am
going
to see what updates it needs an apply them then try again. If it still
does
not work then I will post the exact messages from the event viewer logs.
I
will get to this by tomorrow morning and update this thread with my
results.
Thanks!
-Richard
"Frank McCallister" wrote:
Hi Richard
This is usually because of the type of printer installed, especially
multi-function USB Printers. What type printer are you working with?
--
Frank McCallister [SBS-MVP]
COMPUMAC
"Richard K" wrote:
That's what I am doing. I RWW into the
http:\\servername.domain.com\remote
then Connect to a client computer. When I do this from this Windows XP
home
computer no printers get mapped. When I try to remote in from another
computer it maps printers so it's not the SBS or the office computer
but
something with THIS windows XP home computer.
"Cliff Galiher" wrote:
RWW uses an activeX control that is installed at the time the RWW
site is
accessed. Like all activeX controls, it is identified by a UUID so,
if they
are using RWW, they have the version they need. Installing a new RDP
client
on the XP home machine will not fix your problem.
It is far more likely that the problem is the multi-hop situation you
are
trying to do. Beyond the security implications of logging into a
server
unnecessarily, it also adds an extra burden in routing printer
traffic. You
should look at removing the server from the equation and connect to
the
internal clients directly via RWW.
-Cliff
"Richard K" <RichardK@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:018D8B27-ED80-4EC7-8B8F-EC3B4ECB6A9C@xxxxxxxxxxxxxxxx
I have a client using Windows XP Home at a remote location. They
RWW into
the server then connect to their client. No problems until they
are not
able
to see their Windows XP Home printers while connected to the office
computer.
I have gone through the standard stuff like making sure check boxes
are
set
for remote printing and even made sure the matched set print
drivers where
at
home and on the office computer. The Event logs on the home
computer tell
me
there is an issue with drivers.
What I am thinking is the home computer does not have the latest
RDP and
ActiveX software on their home machine. What are the latest
versions and
how
can I download/install them on the home computer?
--Richard
- Follow-Ups:
- Re: RWW/RDP Client Software?
- From: Larry Struckmeyer [SBS-MVP]
- Re: RWW/RDP Client Software?
- References:
- Re: RWW/RDP Client Software?
- From: Cliff Galiher
- Re: RWW/RDP Client Software?
- From: Frank McCallister
- Re: RWW/RDP Client Software?
- From: Richard K
- Re: RWW/RDP Client Software?
- From: Larry Struckmeyer [SBS-MVP]
- Re: RWW/RDP Client Software?
- Prev by Date: Re: Moving Companyweb from old server to new server
- Next by Date: Re: Moving Companyweb from old server to new server
- Previous by thread: Re: RWW/RDP Client Software?
- Next by thread: Re: RWW/RDP Client Software?
- Index(es):
Relevant Pages
|
