Posted 13 December 2010 - 01:05 PM
I support a network consisting of a Windows domain running off a Windows 2003 domain controller/file server/print server where most of the clients are running Windows XP (balance are Mac OS X machines). I've been experimenting lately with Windows 7 Professional, but am finding that any time I add a printer in Windows 7 and connect to one of the shared printers hosted on the Server 2003 machine, all other clients are unable to use the printer. The blocking happens gradulally; when the printer is first installed, the XP users will occasionally get an error when printing (complains that drivers aren't installed for the printer), but will usually be able to print. If after setting up that printer I actually print a page from the Win7 machine, that will ultimately block them completely. They'll get the missing drivers error any time they try to print or try to open the Properties window for that printer.
The printers in question are Kyocera Mita 3035 multi-purpose machines; all drivers are installed on the server, and this has worked well with all other client machines. The network is new within the last four years, with Cat.6 cabling and gigabit ethernet (copper) switches in between. The server is a Dell PowerEdge server running Windows Server 2003 R2 SP2, with all updates applied.
I'm hoping this is something that someone has seen before. For now I've built a workaround by setting up another shared printer on the server specifically for the Windows 7 machine; so far so good. But since I'm only testing with one Windows 7 machine I'm not sure whether I'll have the same issue with multiple Win7 machines trying to share a single printer on the server.
Thanks for any tips or ideas you might be willing to share.