Has anyone had experience with the KX Driver dropping device options after it has been configured?

Customer has driver installed on server and shared out. For no apparent reason, the driver will drop accessories from the device options list which will then not allow clients to select finishing options. We have most current version installed. Tech support suggested using the KM deleter. Any thoughts?

Have you checked the server to make sure that all of your options are installed on the SERVER the customer may be doing it on the local machine for temporary use and when they are done the device settings will never hold unless done on the server.

Yes, that's the problem. All of the options are selected on the server, but after an unknown amount of time, the server will lose these selected device options and so will the connected client users.

When you start a Terminal Services session with a local printer connected to your client computer, a redirected print queue is created in the Terminal Services session for your local printer. The print queue uses a set of default printer settings that are determined by Terminal Services. The local printer settings that you define or change offline are not used by Terminal Services.

In the Terminal Services session, you can modify the printer settings for your redirected printer if you have the required privileges (for example, you are a member of the Print Administrators group). The changes that you make in the Terminal Services session are persistent; the printer configuration changes are cached on the client computer for subsequent reconnections. When you reconnect, Terminal Services detects the printer configuration settings that are cached on the client computer and uses them.

Under some circumstances, changes that you make on the printer's Device Settings tab do not persist when you reconnect. The printer configuration information may seem to be lost.
Back to the top
CAUSEThe current printing model does not support detecting changes to the Device Sett...The current printing model does not support detecting changes to the Device Settings tab for each redirected printer.
Back to the top
WORKAROUNDTo work around this behavior: When you are using a Terminal Services session, ma...To work around this behavior:
When you are using a Terminal Services session, make the changes that you want on the printer's Device Settings tab for the redirected Terminal Services print queue, then make a change on another tab for the printer. By making the change on another tab, the server is notified that there has been a configuration change. This causes the server to rebuild all cached information, including information from the Device Settings tab.
After you make the configuration change, do not log out or disconnect from the Terminal Services session within the next 60 seconds. This allows Terminal Services to make the configuration change persistent.

Isn't there an option in Autoconfigure to automatically update the device configuration periodically? I think it's on by default - I'd suggest turning it off.

We had a 620 doing this that had an 8030 print sys in it. The fix was to update firmware on the print controller with the compact flash card.
Hope this helps.

I am having the same problem with a KM-6030 on Windows 2008 Server R2. I will update print system firmware and try the above mentioned fix for terminal services.

Thanks.

Have the same problem also, but with a 300ci and a TA 250 in the same account. I actually saw it do it. All of a sudden, the clients can not see the options, you check the server and the options are defaulted back to none. Started out as a once a month thing, now it's twice a week. Hit the auto configure, and it all comes back, till next time. Seems like it all started when some Win 7 clients got on the network, but KM has no clue.

If you can actually see it happen, I would suggest hitting the machine with the "ping x.x.x.x -t" command to see if the printer itself is dropping from the network

TECHBOY...u r money$$$$...absolutely the answer to the issue...free @ no cost to us...excellent work!



DUMMIETEK...give credit always...if credit is due...

Kudos to Techboy!

Had a customer ready to throw us out... It guy didnt think it was the issue until I proved it.

;-)

How did you prove it?

Techboy-

Are you saying we should make sure that client users do not have access to make device setting changes? Because if they did, any changes they make would overide the settings on the server?

I'm going to install the most current driver at this location and make sure that the permissions only allow printing for the end users.

I'm just trying to better understand your advice in the previous post so I can work around this issue - as it has come up again for me. Don't know if this is a driver issue or a problem with Windows.

Thanks

I agree, I'm dealing with straight Server 2008/2003 networks, no terminal sessions. There is something funny going on with the driver. I have to go back tomorrow to a SBS 2008 with a TA 5500ci that keeps dropping the accessories. I tried the PCL driver as suggested, it was stable, but the Calibri font embedded in an Excel sheet prints out all screwed up, and the customer uses it ALOT! I now have 3 accounts escalated to KM for this very issue, and they have no explanation as of yet.
If ANYONE can explain this, I will personally buy the beer.

I had some fits with one yesterday, I had a 2008 64 bit server with 32 bit work stations, I loaded the 32 bit drivers through the print management console on the server, and unchecked SNMP Status enabled under configure in Ports. Everything seem to work fine after that.

Drew, when using the PCL5? Language, do you have the GDI Compatible Mode checked On. I've Ran Across problems with trying to print out certain fonts and especially "Word Art" stuff properly unless GDI Compatible Mode is selected.

Did not check it Eric, honestly don't even know what it does! I have tried un-checking SNMP, but to no avail. My point still stands, why does the KX driver do this? On a bog standard server install, you load the the driver, go to sharing, add support for 64 bit and thats should be it.

quote:

Originally posted by progoffice:
How did you prove it?

I loaded the driver on the admins pc.. I installed the driver with a NEW IP ..
I installed all periphs with "auto-config"...and turned on Job Accounting.
I then changed "print directly to the printer" under the Advanced tab.
Ok'd out... waited 2 minutes thene changed the setting under Advanced back to "Spool print documents so program finishes printing faster" (default setting) saved and tested..

After test was good.. I followed the same procedure with the original IP address.

To this day that machine is still with that customer with NO issues.

The admin had a cached version of the driver on his work pc and home pc. Both had no periphs and job acct turned off. Everytime he logged into the network, the cached version overwrote the driver on the server.

quote:

Originally posted by drewsup:
I agree, I'm dealing with straight Server 2008/2003 networks, no terminal sessions. There is something funny going on with the driver. I have to go back tomorrow to a SBS 2008 with a TA 5500ci that keeps dropping the accessories. I tried the PCL driver as suggested, it was stable, but the Calibri font embedded in an Excel sheet prints out all screwed up, and the customer uses it ALOT! I now have 3 accounts escalated to KM for this very issue, and they have no explanation as of yet.
If ANYONE can explain this, I will personally buy the beer.

I came across this same Calibri font issue on an HP CLJ4700 printer. After some experimenting (thank god this IT was flexible, willing to try a few things) we discovered that changing the default font to anything else resolved the "PostScript" error issue. He told me later on that he had re-loaded Microsoft Office, and the server OS, and the problem persisted for all Microsoft Office programs, but only when Calibri font was used.

His solution was to default each of the Microsoft Office programs to Arial font, and when older/previously created docs with Calibri font were opened, changing font to Arial.

Personally I don't think it's a Kyocera driver thing, I think it's a Microsoft Office thing.

quote:

Originally posted by WeBeJammin:
If you can actually see it happen, I would suggest hitting the machine with the "ping x.x.x.x -t" command to see if the printer itself is dropping from the network

I've seen this myself, and I think that's exactly the problem. The 5.2.1108g driver re-checks the configuration periodically, and it the printer is off-line resets the driver to the base/default settings.

I haven't been able to reproduce the problem crossover-ed to my laptop, but have managed to catch it on the network.

You could go back to the 5.1.xxxx version of the driver that doesn't re-check configuration. Or try to convince IT that there is a network issue worth fixing.