Local area network printing problem 1

[noblehill]

Hello!

A strange problem occured: one workstation inside my domain can't print to some network printers in the domain. This is not a user account or profile problem, the problem is clearly workstation related. All users have the same problem on the same workstation, but not on any other workstation. All workstations are running Win XP Pro.

All network printers can be installed just fine, but two of the printers can't be used. The error message is "Could not get device information". No error codes that could guide me. When I look at the printers on the server side, there are sessions open for the workstation giving me trouble. Any ideas?

 

[jimp56]

what application(s) are generating this error? i have seen this in ms-access - sometimes you have to go in and specify a printer rather than leave it at the default/auto settings.

also, can you print a test page directly from the printer object?

 

[bcastner]

And for the problematic workstations, what is the port defined for these printers? TCP/IP, DOT4, or \\server_name\printer_name ?

 

[noblehill]

Thanks for your answers! I think the problem is not application related, I can't print from any application or a testpage. TCP/IP is the defined port for all printers.

 

[noblehill]

More news: now I have another workstation with a printing problem. When a document is printed from MS Word to a specific printer, the printout is not ok. There are added spaces, like for example a word "time" was spelled "tim e". But the spelling is correct and there are no invisible characters. Sometimes characters are condensed, there's no space at all between characters. The printout from other printers or even from the same printer sent from a different workstation looks just fine. I'm beginning to think that somehow the workstations fail to get the correct driver from the server. I'll keep digging into this.

 

[carty]

I've seen this before too and the way I've got around it is to add the printer as a local printer but create a new standard TCP/IP port while doing so. You may need to install the drivers for the printer locally though.

As for the printing fonts not right, I'd suggest updating the printer driver.

 

[rmaznj]

I like cartys idea. I have done that too, kinda like creating a "ghost" printer. It has worked for me in the past, oddly enough mostly when running some kinds of DOS applications.

 

[noblehill]

Thanks, everyone! Both problems solved, the connectivity problem by uninstalling xp sp2 and the font problem by installing the printer drivers locally. I'm sorry it took me a while to test your ideas, hell just broke loose in the office and I couldn't attend to any minor problems.

 

[carty]

Haha, good ol' SP2.

Hell broke loose? Playing Doom 3 eh?