Printing to a network printer

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

ppm19702002@yahoo.com - 23 Jan 2007 03:32 GMT

We have a Mac environment but found and purchased a program that is PC
only. We have it running on a Dell 1800 Server, running Windows Server
2003, and are connecting via Terminal Services/RDC....all of which has
worked surprisingly easy and well....except when printing. I can
connect, work in the program, but when I go to print, RDC crashes on my
Intel Macs.

I have tried setting up the network printer (from Toshiba) as both PCL
and as Postscript L3. The program won't print from the Server using
Postscript Level 3, but prints fine is I choose the PCL driver. From
my Mac, under any driver, it simply crashes....but it does
print....several seconds after the crash my document prints. I then
have to restart RDC and can usually go right back to where I was in the
program.

Anyone have a clue on a fix for this?

Reply to this Message

William Smith - 24 Jan 2007 04:49 GMT

> We have a Mac environment but found and purchased a program that is PC
> only. We have it running on a Dell 1800 Server, running Windows Server
[quoted text clipped - 12 lines]
>
> Anyone have a clue on a fix for this?

This is a known issue with RDC and Intel Macs but unfortunately one
without a resolution. Let's hope Microsoft releases a universal RDC
client with Office 2008 or better yet earlier!

bill

Signature

William M. Smith
(Microsoft Interop MVP - Mac/Windows)

Reply to this Message

ppm19702002@yahoo.com - 25 Jan 2007 19:06 GMT

Let's hope it's this quarter...or this month. We only use one
Application on our Windows server, and it's a critical one. We had
hoped we could use it va RDC, but that is obvously not going to work.
I don't want to buy 15 new computers so I can run one App. If I can't
find a way around it, we'll go back to the drawing board, and do what
we probably shold have done at the start: buy an application that runs
on a Mac.

On Jan 23, 11:49 pm, William Smith <meckli...@REM0VETH1S.comcast.net>
wrote:

> In article <1169523155.165999.174...@51g2000cwl.googlegroups.com>,
>
[quoted text clipped - 22 lines]
> William M. Smith
> (Microsoft Interop MVP - Mac/Windows)

Reply to this Message

William Smith - 26 Jan 2007 03:24 GMT

> Let's hope it's this quarter...or this month. We only use one
> Application on our Windows server, and it's a critical one. We had
[quoted text clipped - 3 lines]
> we probably shold have done at the start: buy an application that runs
> on a Mac.

You might also have a look at rdesktop found here
<http://www.rdesktop.org/>. I've never used this before but it may be an
alternative.

bill

Signature

William M. Smith
(Microsoft Interop MVP - Mac/Windows)

Reply to this Message

ppm19702002@yahoo.com - 26 Jan 2007 03:44 GMT

I downloaded it, and it would not launch. The site mentioned that this
sometimes occurred, and gave some Unix code to edit in Terminal. That
part scares me. I know zero about programming or using Terminal. I
wish Microsoft would step up to the plate and fix their software.
Someone suggested buying Windows and running our Intel Macs using
Windows XP and connecting via the Windows Terminal Services client. I
can't see investing more in software that may or may not work...and
since I have 20 Macs, and only 8 are Intel machines, it still would not
work for all.

On Jan 25, 10:24 pm, William Smith <meckli...@REM0VETH1S.comcast.net>
wrote:

> In article <1169752008.262543.205...@l53g2000cwa.googlegroups.com>,
>
[quoted text clipped - 13 lines]
> William M. Smith
> (Microsoft Interop MVP - Mac/Windows)

Reply to this Message

dbatchelor@lfh.co.uk - 31 Jan 2007 11:11 GMT

Hi,

We have the same problem - until they get this sorted have you tried
tsclient?

It works the same, you just have to install extra software from your
mac install disc - see link.

http://desktopecho.com/tsclientx/

you might find it useful.

Reply to this Message

Mac Forum / Applications / Other MS Products / January 2007

Printing to a network printer