I have experienced several problems with those models on a client/server environment, server is a windows server 2008, 32 bits, on client side there are both, windows xp professional 32 bits, windows system 7 32 bits and a few client computers with windows vista enterprise edition, when we connect for the first time to the server's shared printer, printer works well, but a few days later, with no apparent pattern, when the client wants to print a document, they receive a message saying that no drivers available for the printer, and then we must to delete the printer from the client computer and reconnect it from the server. Anybody have experienced same problem?
Taskalfa 300i & 400ci, driver problems over windows server 2008 32 bit
Collapse
X
-
Thanls a lot foy your response Frits, can you send me the file that you have mentioned to this e-mail please? rchias@hotmail.com
RegardsComment
-
I'm having this same situation on a CS-6030. Drivers are version 5.1.1405, Server 2008, workstation Windows 7. Can you give us the gist of the bulletin? =^..^=If you'd like a serious answer to your request:
1) demonstrate that you've read the manual
2) demonstrate that you made some attempt to fix it.
3) if you're going to ask about jams include the jam code.
4) if you're going to ask about an error code include the error code.
5) You are the person onsite. Only you can make observations.
blackcat: Master Of The Obvious =^..^=Comment
-
The problem is the reverse. The Server 2008 loads and works fine. It's the Windows 7 32 bit workstations that lose functionality. It's an Exchange server, so the driver on the server is shared to all users. The XP 32 bit and Vista 32 bit workstations have no problem, only the two new Windows 7 workstations. And all the PCs on the network are 32 bit, so the single 5.1.1405 x86 driver should be suitable for all.
The IT guy has successfully created one functioning Win7 print driver, and cannot say if he did anything differently. Since there are multiple machines on multiple servers we're not quite there yet. =^..^=If you'd like a serious answer to your request:
1) demonstrate that you've read the manual
2) demonstrate that you made some attempt to fix it.
3) if you're going to ask about jams include the jam code.
4) if you're going to ask about an error code include the error code.
5) You are the person onsite. Only you can make observations.
blackcat: Master Of The Obvious =^..^=Comment
-
It occurs to me that we did not try to use the Universal Driver. When I get back around to that issue that will be the next attempt. =^..^=If you'd like a serious answer to your request:
1) demonstrate that you've read the manual
2) demonstrate that you made some attempt to fix it.
3) if you're going to ask about jams include the jam code.
4) if you're going to ask about an error code include the error code.
5) You are the person onsite. Only you can make observations.
blackcat: Master Of The Obvious =^..^=Comment
-
Pointandprint.doc Here is a Microsoft Document that helps to solve this issue for windows 7, but i'm still experiencing the problem with windows vistaComment
-
We have had the same issue with a 2K8 32bits printserver with XP 32bits clients (thin and thick), with the 5.1.1405 driverpackage. After deleting the driver and updating to 5.1.2406 the problem dissapeared.
When you have similar issues with W7 and server2K3, (0X000002 errors or printers not working after some time), this I solved by a Microsoft hotfix http://download.microsoft.com/downlo...940157-x86.msu
Regards,
RobbertComment
-
hi frits, please i have the same problem and i really need the file to fix the problem. please my email: is darius.slncss@gmail.comComment
Comment