Printer Auto Create Problems 1

[bluewhaleCA]

Hello list. I've searched and browsed most of the morning trying to find a 'cure' to remote printing issues and wanted to see if I'm on target yet.

We are running Metaframe XP FR3 with a TINY load: I've never seen more than 6 users connected at one time. The EE's located in our remote office have intermittent problems with not being able to print to their local printers from within their Metaframe sessions. In the past I've gone into the MF server at night, stopped the spooling process and deleted the jobs which would not delete earlier. Then reboot the MF server and the users were able to print locally again. This is no longer working.

I have just downloaded and will be looking at project compatibility from DABCC.COM.

I have to wonder tho: this problem occurs to different people... it lasts for weeks or months then disappears. While 2 users might not be able to print locally at the same moment the other 4 in that office or at home ARE able to print locally.

One other note: the problem occurs to Domain admins as well, so it doesn't appear to be a rights issue.

Is using Project Compatibility 3 the best path to take here? Any thoughts deeply appreciated.


Paul

 

[ascotta]

I would try deleting these local printers as well as removing the print jobs.

When a user logs off and their is still something in the print queue the user can connect as many times as they like but local printing will not work, kind of an orphaned printer scenario.

1. Delete print jobs
2. Stop and start the spooler until all print jobs disappear
3. delete the printers
4. Stop and start spooler again Just to make sure
5. re-boot if required but I don't think it should be.



Cheers
Scott

 

[Ogi]

Hi,

What are the client names for these devices, are they the same?

It sounds to me if user1 logs in and prints that's ok, then it stops! Since user1 logged in and printed, user2 logged in. User2 can print without any issue. If user2 logs out, user1 can print.

I'd be more inclined to check each Client to see what they are called! I've got that were I am, so have gone round and checked certain machines and renamed them from within Citrix Program Neighborhood.

Cheers,
Carl.

 

[StumptAgain]

You may want to check the print drivers that are being used. I have just spent the better part of two weeks trying to figure out a very similar scenario and it turned out that a faulty .dll was the culprit.
Once it was removed things have been working great. Check out

http://www.printingsupport.com

for a slew of Citrix printing answers. There is a great cross-compatibility checklist there.

 

[tecknic]

Stunptagain is right focus your research in the drivers section. Expecially if the domain admin have the same problem. Are you using generic drivers or you install the printers drivers? I haven't work with XP but so I'm don't know it's behavior but rebooting is not an option. you can stop and restart the spooling service anytime when nobody prints. it takes few secondes only and will be transparent with the users. You may run some test directly with the users printer. As Admin you can see all users printers and make modifications if nescessary.

I recommende not to install printers manufacturer driver, specially HP, they tent to install all kind of crap that can distablelize your server. if you can stick to the flatfile.

Nick

 

[Ogi]

Nick,

FYI...

Download the "Corporate" HP drivers and they work without issue, that is why they are named such. They've removed all the rubbish and just provide the drivers. I've got 140 HP printer drivers installed on my server, and very really do they cause an issue!


Cheers,
Carl.

 

[Ogi]

Nick,

FYI...

Download the "Corporate" HP drivers and they work without issue, that is why they are named such. They've removed all the rubbish and just provide the drivers. I've got 140 HP printer drivers installed on my server, and very rarely do they cause an issue!


Cheers,
Carl.

 

[tecknic]

Hi Carl, They may have upgrade their way of releasing drivers. my experience is that they are very intrusive. and I don't like that.

I may take a look on the new hp printers I will have to connect.

thanks for the tips!

Nick

 

[Ogi]

Hi,

On the corporate drivers, they don't try to upgrade themselves, HP spent a lot of time in creating these types of drivers as the Citrix community complained to them, which is why they now create these special drivers.

I agree with you though, stay away from CD's and the drivers that are "all singing, all dancing"!!!

Cheers,
Carl.

 

[bluewhaleCA]

I appreciate all the info. I was unable, for some reason, to stop the print spool service last week on the Metaframe Server but now have been able to do so and all is well once again.

As no one gave Project Comppatibility a ringing endorsement I think I'll put it on the shelf for now. If problems continue : well, first thing would be to get the ' corporate ' HP drivers mentioned above. I just visited the HP driver site ( for the Laserjet 2200 in this case ) and did not see a ' corporate ' designation on any of the drivers for XP. Would these ' new ' slimmed down drivers be kept somewhere other than the driver download page for X printer?

Thanks again for your help.


Paul

 

[Ogi]

Hi,

You need the "Corporate" drivers for the Citrix Servers, the clients can run which ever drivers you want!

Be aware, the only problem then will be the difference with printer driver names. If they are different, use CMC to map the differences.

Cheers,
Carl.

 

[bluewhaleCA]

Hey Carl:

I was unable to find anything trying a search at HP's driver site using the word ' corporate '. By referring to them as Corporate drivers, could those of you who use them be speaking about the driver by itself vs with a 'bundle' ? as in

http://h20000.www2.hp.com/bizsuppor...5469&cc=us&Submit.y=8&Submit.x=1&swEnvOID=181

Here the driver is 1.5 megs, but the 'bundle' is 4 megs.

And of course the problem continues today, so I guess I shall be looking at project Compatibility 3.0 after all
:{


Thanks


Paul

 

[Ogi]

Hi,

Correct, download only the driver and never the bundles!

Cheers,
Carl.