created the print queue configuration, there is no problem reading this configuration and all of the print jobs functions as expected. However, when a Windows 2000, Windows XP, or Windows Server 2003 client makes a connection to this shared printer on the Windows NT 4.0 print server, it is vended the added
Figure 80: Mixed
Symptoms of driver incompatibility in a mixed OS environment
There is no single set of symptoms to be seen when client and server printer drivers are not compatible, but common symptoms include the clients not being able to see the proper queue configuration with respect to installed device options and default settings. Other problems in functionality can include the inability to print in landscape or from a specific paper tray.
When an incompatible mix of
In the example illustrated in the following figure, there is a Windows NT 4.0 print server and a Windows 2000 print server. The Windows 2000 client illustrated in this figure is a laptop computer user who occasionally travels between different office locations for business.
In Event #1, at the home office, the Windows 2000 client makes a connection to the local print server. This local print server is running Windows NT 4.0 and contains only a
In Event #2, the client takes a business trip to a remote site. While at the remote site, the client user needs to print and makes a connection to a shared printer. The server for this shared printer at the remote site is hosted from a print server that has been migrated to Windows 2000 and contains a
208 | Print server operating system migration | Software Technical Reference ENWW |