HP 9500n HP Color LaserJet 9500n and 9500hdn - Software Technical Reference - Page 268

Symptoms of driver incompatibility in a mixed OS environment, PCL 6

Page 268 highlights

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 version-2 and version-3 printer drivers is present in the environment, unexpected behavior can occur due to some of the more subtle behaviors of Point and Print that are not obvious. The following figures illustrate an environment that contains incompatible version-2 and version-3 printer drivers. This section examines examples of how incompatible drivers can affect printing functionality. 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 version-2 driver for the printer in question. Suppose, for example, that this is the "HP LaserJet 4000 Series PCL 6" version-2 driver. The Windows 2000 client is vended this version-2 printer driver and because client and server are both running the same printer driver, printing works as expected. 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 version-3 driver, which is also the "HP LaserJet 4000 Series PCL 6" printer driver. Now, the client computer already has a printer driver named "HP LaserJet 4000 Series PCL 6", but it is a version-2 driver and Windows 2000 prefers to use a version-3 printer driver when it is available. So in this case, because the print server at the remote site has a matching driver, which is version-3, the Windows 2000 client downloads this version-3 driver and now runs this printer driver. The connection to the remote print server silently upgraded the client computers printer driver to a version-3 driver. While still at the remote site, the client and server are both running the same printer driver and printing works as expected. However at Event #3, when the client returns to the home office and tries to print, problems occur because the printer driver being used on the client is not the same as that being used on the server and these two printer drivers are incompatible with each other. 266 Print server operating system migration Software Technical Reference ENWW

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286

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 version-2 and version-3 printer drivers is present in the environment, unexpected
behavior can occur due to some of the more subtle behaviors of Point and Print that are not obvious. The following
figures illustrate an environment that contains incompatible version-2 and version-3 printer drivers. This section
examines examples of how incompatible drivers can affect printing functionality.
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 version-2 driver for the printer in question. Suppose, for
example, that this is the “HP LaserJet 4000 Series PCL 6” version-2 driver. The Windows 2000 client is vended this
version-2 printer driver and because client and server are both running the same printer driver, printing works as
expected.
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 version-3 driver, which is also the “HP LaserJet 4000
Series PCL 6” printer driver. Now, the client computer already has a printer driver named “HP LaserJet 4000 Series
PCL 6”, but it is a version-2 driver and Windows 2000 prefers to use a version-3 printer driver when it is available. So
in this case, because the print server at the remote site has a matching driver, which is version-3, the Windows 2000
client downloads this version-3 driver and now runs this printer driver.
The connection to the remote print server silently upgraded the client computers printer driver to a version-3 driver.
While still at the remote site, the client and server are both running the same printer driver and printing works as
expected. However at Event #3, when the client returns to the home office and tries to print, problems occur because
the printer driver being used on the client is not the same as that being used on the server and these two printer
drivers are incompatible with each other.
266
Print server operating system migration
Software Technical Reference ENWW