Can't print to QMS printer

G

Guest

More details from an earlier post:

I have a couple of pc's running XP with SP2 and MS Office 2003 with SP3.
Don't know exactly when the problem started, but sometime around these new
service packs, I think.

I also have a Minolta QMS Magicolor 3100 laser printer on the same network.
Most programs can print to the QMS from these two pc's just fine, except
Word. In Word, I select File - Print - choose the QMS printer - Word gives me
the error: it has encountered a problem and will shut down. Sorry for the
inconvenience ...". It tries to recover the document.

I can print to the same QMS printer from other pc's with SP2 on my network
using Word.

I tried a link someone provided earlier about printing to loopback
addresses, but I'm not using an address for the printer in any loopback ip
range. The driver is loaded on our Server 2003 and works for other pc's. I've
tried removing and re-installing the printer on these pc's. I've loaded the
Office cd and did the Repair option. Even ran AdAware and Spybot. Nothing
helps. Any ideas???

Thanks!
Jim
 
Y

yo_matt1

Unfortunately, I don't have a solution but I can report the exact sam
problem on my XP SP2 machine and a Magicolor 3100 when printing fro
Word. I have tried both reinstalling printer drivers from QMS and th
Microsoft patch suggested in a reply to an earlier version of this pos
without sucess. Oddly, printing from another application like Adobe
works just fine. Anyone from Microsoft or QMS listening?
 
B

Bigskyflyzzz

I ran into exactly the same problem printing to our Magicolor 3100 fro
a SP2 machine. I uninstalled SP2 and the problem magically went away.
 
T

Tightscot

I Had the same problem.... this was what i found.

All the pcs running XP PRO were fine, there was 1 pc running XP HOME,
this HOME machine was having the exact same problems (word crashing
etc). I solved the problem by changing the 'workgroup' of the XP HOME
pc to be the same name as the Domain name. I also changed the
permissions on the shared printer so that 'everyone' had 'full access
rights'
This solved the problem.

Hope that helps.. :)

Tightscot
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top