I sent this out last week to let people know. We found that using Remote Desktop Connection or the Terminal Services Client under Win XP Pro SP2 to connect to and run our app in remote branches wouldn't allow us to print to our local networked printer. The printer was on a standard TCP/IP port - 192.168.22.23. We tried everything and finally, Francis, one of my associates found the answer in a recent knowledge based article.
http://support.microsoft.com/?kbid=302361 Once we applied the fix, we were able to connect via Remote Desktop Connection (RDC) and the local networked printer showed up in the RDC session. A bug in Win XP Pro SP2 - we're not sure, but its highly suspect. > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > On Behalf Of Andy Davies > Sent: Friday, March 09, 2007 7:50 AM > To: [EMAIL PROTECTED] > Subject: Re: port forwarding printers > > >I want to bypass the remote desktop print function > >because it doesn't work properly with my hp all-in-one > >printer. > > Check the msdn library - there's a paper about multi_fn devices that don't > use lpt: prn: or com: ports > > Andrew Davies MBCS CITP > - AndyD 8-)# > > <snip> _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
