PDF

Network Fun Category
Tips and Tricks to maintain networks for the advanced user .
Generated by KnowledgeBuilder - http://www.activecampaign.com/kb

Contents
Network Fun 1
Windows Error Messages 1
Net Use Command 44
Login Script For Newbies 48
How to Deploy Printers with 2003 group policy 52
take stuff your right click that eats memory 58
VLAN on Linux and Switches 67
how to refresh group policy settings on a windows 2000 machine. gotta do it from start-
>run 88
Eliminate Balloon Tips in XP 90
Generated by KnowledgeBuilder - http://www.activecampaign.com/kb

Network Fun
Tips and Tricks to maintain networks for the advanced user .
Windows Error Messages
Windows Error Messages
I was gonna write a tut on this but found out I would of been copying to much info and not
writing it myself.
This little thread will give you a list of all known error codes. I'll include sources and program link at
the bottom.
MS Windows Error Messages
Code Error Message

0 The operation completed successfully.
1 Incorrect function.
2 The system cannot find the file specified.
3 The system cannot find the path specified.
4 The system cannot open the file.
5 Access is denied.
6 The handle is invalid.
7 The storage control blocks were destroyed.
8 Not enough storage is available to process this command.
9 The storage control block address is invalid.
10 The environment is incorrect.
11 An attempt was made to load a program with an incorrect format.
12 The access code is invalid.
13 The data is invalid.
14 Not enough storage is available to complete this operation.
15 The system cannot find the drive specified.
16 The directory cannot be removed.
17 The system cannot move the file to a different disk drive.
18 There are no more files.
19 The media is write protected.
20 The system cannot find the device specified.
21 The device is not ready.
22 The device does not recognize the command.
23 Data error (cyclic redundancy check).
24 The program issued a command but the command length is incorrect.
25 The drive cannot locate a specific area or track on the disk.
26 The specified disk or diskette cannot be accessed.
27 The drive cannot find the sector requested.
28 The printer is out of paper.
29 The system cannot write to the specified device.
30 The system cannot read from the specified device.
31 A device attached to the system is not functioning.
32 The process cannot access the file because it is being used by another process.
33 The process cannot access the file because another process has locked a portion of the file.
36 Too many files opened for sharing.
38 Reached the end of the file.
39 The disk is full.
50 The request is not supported.
51 Windows cannot find the network path. Verify that the network path is correct and the destination
computer is not busy or turned off. If Windows still cannot find the network path, contact your
network administrator.
52 You were not connected because a duplicate name exists on the network. Go to System in
Control Panel to change the computer name and try again.
Generated by KnowledgeBuilder - http://www.activecampaign.com/kb 1 of 90

53 The network path was not found.
54 The network is busy.
55 The specified network resource or device is no longer available.
56 The network BIOS command limit has been reached.
57 A network adapter hardware error occurred.
58 The specified server cannot perform the requested operation.
59 An unexpected network error occurred.
60 The remote adapter is not compatible.
61 The printer queue is full.
62 Space to store the file waiting to be printed is not available on the server.
63 Your file waiting to be printed was deleted.
64 The specified network name is no longer available.
65 Network access is denied.
66 The network resource type is not correct.
67 The network name cannot be found.
68 The name limit for the local computer network adapter card was exceeded.
69 The network BIOS session limit was exceeded.
70 The remote server has been paused or is in the process of being started.
71 No more connections can be made to this remote computer at this time because there are
already as many connections as the computer can accept.
72 The specified printer or disk device has been paused.
80 The file exists.
82 The directory or file cannot be created.
83 Fail on INT 24.
84 Storage to process this request is not available.
85 The local device name is already in use.
86 The specified network password is not correct.
87 The parameter is incorrect.
88 A write fault occurred on the network.
89 The system cannot start another process at this time.
100 Cannot create another system semaphore.
101 The exclusive semaphore is owned by another process.
102 The semaphore is set and cannot be closed.
103 The semaphore cannot be set again.
104 Cannot request exclusive semaphores at interrupt time.
105 The previous ownership of this semaphore has ended.
107 The program stopped because an alternate diskette was not inserted.
108 The disk is in use or locked by another process.
109 The pipe has been ended.
110 The system cannot open the device or file specified.
111 The file name is too long.
112 There is not enough space on the disk.
113 No more internal file identifiers available.
114 The target internal file identifier is incorrect.
117 The IOCTL call made by the application program is not correct.
118 The verify-on-write switch parameter value is not correct.
119 The system does not support the command requested.
120 This function is not supported on this system.
121 The semaphore timeout period has expired.
122 The data area passed to a system call is too small.
123 The filename, directory name, or volume label syntax is incorrect.
124 The system call level is not correct.
125 The disk has no volume label.
126 The specified module could not be found.
127 The specified procedure could not be found.
128 There are no child processes to wait for.
130 Attempt to use a file handle to an open disk partition for an operation other than raw disk I/O.
131 An attempt was made to move the file pointer before the beginning of the file.
132 The file pointer cannot be set on the specified device or file.
133 A JOIN or SUBST command cannot be used for a drive that contains previously joined drives.
134 An attempt was made to use a JOIN or SUBST command on a drive that has already been joined.
135 An attempt was made to use a JOIN or SUBST command on a drive that has already been
substituted.
136 The system tried to delete the JOIN of a drive that is not joined.
137 The system tried to delete the substitution of a drive that is not substituted.
138 The system tried to join a drive to a directory on a joined drive.
139 The system tried to substitute a drive to a directory on a substituted drive.
140 The system tried to join a drive to a directory on a substituted drive.

141 The system tried to SUBST a drive to a directory on a joined drive.
142 The system cannot perform a JOIN or SUBST at this time.
143 The system cannot join or substitute a drive to or for a directory on the same drive.
144 The directory is not a subdirectory of the root directory.
145 The directory is not empty.
146 The path specified is being used in a substitute.
147 Not enough resources are available to process this command.
148 The path specified cannot be used at this time.
149 An attempt was made to join or substitute a drive for which a directory on the drive is the target
of a previous substitute.
150 System trace information was not specified in your CONFIG.SYS file, or tracing is disallowed.
151 The number of specified semaphore events for DosMuxSemWait is not correct.
152 DosMuxSemWait did not execute; too many semaphores are already set.
153 The DosMuxSemWait list is not correct.
154 The volume label you entered exceeds the label character limit of the target file system.
155 Cannot create another thread.
156 The recipient process has refused the signal.
157 The segment is already discarded and cannot be locked.
158 The segment is already unlocked.
159 The address for the thread ID is not correct.
160 One or more arguments are not correct.
161 The specified path is invalid.
162 A signal is already pending.
164 No more threads can be created in the system.
167 Unable to lock a region of a file.
170 The requested resource is in use.
173 A lock request was not outstanding for the supplied cancel region.
174 The file system does not support atomic changes to the lock type.
180 The system detected a segment number that was not correct.
183 Cannot create a file when that file already exists.
186 The flag passed is not correct.
187 The specified system semaphore name was not found.
196 The operating system cannot run this application program.
197 The operating system is not presently configured to run this application.
199 The operating system cannot run this application program.
200 The code segment cannot be greater than or equal to 64K.
203 The system could not find the environment option that was entered.
205 No process in the command subtree has a signal handler.
206 The filename or extension is too long.
207 The ring 2 stack is in use.
208 The global filename characters, * or ?, are entered incorrectly or too many global filename
characters are specified.
209 The signal being posted is not correct.
210 The signal handler cannot be set.
212 The segment is locked and cannot be reallocated.
214 Too many dynamic-link modules are attached to this program or dynamic-link module.
215 Cannot nest calls to LoadModule.
230 The pipe state is invalid.
231 All pipe instances are busy.
232 The pipe is being closed.
233 No process is on the other end of the pipe.
234 More data is available.
240 The session was canceled.
254 The specified extended attribute name was invalid.
255 The extended attributes are inconsistent.
258 The wait operation timed out.
259 No more data is available.
266 The copy functions cannot be used.
267 The directory name is invalid.
275 The extended attributes did not fit in the buffer.
276 The extended attribute file on the mounted file system is corrupt.
277 The extended attribute table file is full.
278 The specified extended attribute handle is invalid.
282 The mounted file system does not support extended attributes.
288 Attempt to release mutex not owned by caller.
298 Too many posts were made to a semaphore.
299 Only part of a ReadProcessMemory or WriteProcessMemory request was completed.
300 The oplock request is denied.

301 An invalid oplock acknowledgment was received by the system.
302 The volume is too fragmented to complete this operation.
303 The file cannot be opened because it is in the process of being deleted.
487 Attempt to access invalid address.
534 Arithmetic result exceeded 32 bits.
535 There is a process on other end of the pipe.
536 Waiting for a process to open the other end of the pipe.
994 Access to the extended attribute was denied.
995 The I/O operation has been aborted because of either a thread exit or an application request.
996 Overlapped I/O event is not in a signaled state.
997 Overlapped I/O operation is in progress.
998 Invalid access to memory location.
999 Error performing inpage operation.
1001 Recursion too deep; the stack overflowed.
1002 The window cannot act on the sent message.
1003 Cannot complete this function.
1004 Invalid flags.
1005 The volume does not contain a recognized file system. Please make sure that all required file
system drivers are loaded and that the volume is not corrupted.
1006 The volume for a file has been externally altered so that the opened file is no longer valid.
1007 The requested operation cannot be performed in full-screen mode.
1008 An attempt was made to reference a token that does not exist.
1009 The configuration registry database is corrupt.
1010 The configuration registry key is invalid.
1011 The configuration registry key could not be opened.
1012 The configuration registry key could not be read.
1013 The configuration registry key could not be written.
1014 One of the files in the registry database had to be recovered by use of a log or alternate copy.
The recovery was successful.
1015 The registry is corrupted. The structure of one of the files containing registry data is corrupted,
or the system's memory image of the file is corrupted, or the file could not be recovered because
the alternate copy or log was absent or corrupted.
1016 An I/O operation initiated by the registry failed unrecoverably. The registry could not read in, or
write out, or flush, one of the files that contain the system's image of the registry.
1017 The system has attempted to load or restore a file into the registry, but the specified file is not
in a registry file format.
1018 Illegal operation attempted on a registry key that has been marked for deletion.
1019 System could not allocate the required space in a registry log.
1020 Cannot create a symbolic link in a registry key that already has subkeys or values.
1021 Cannot create a stable subkey under a volatile parent key.
1022 A notify change request is being completed and the information is not being returned in the
caller's buffer. The caller now needs to enumerate the files to find the changes.
1051 A stop control has been sent to a service that other running services are dependent on.
1052 The requested control is not valid for this service.
1053 The service did not respond to the start or control request in a timely fashion.
1054 A thread could not be created for the service.
1055 The service database is locked.
1056 An instance of the service is already running.
1057 The account name is invalid or does not exist, or the password is invalid for the account name
specified.
1058 The service cannot be started, either because it is disabled or because it has no enabled
devices associated with it.
1059 Circular service dependency was specified.
1060 The specified service does not exist as an installed service.
1061 The service cannot accept control messages at this time.
1062 The service has not been started.
1063 The service process could not connect to the service controller.
1064 An exception occurred in the service when handling the control request.
1065 The database specified does not exist.
1066 The service has returned a service-specific error code.
1067 The process terminated unexpectedly.
1068 The dependency service or group failed to start.
1069 The service did not start due to a logon failure.
1070 After starting, the service hung in a start-pending state.
1071 The specified service database lock is invalid.
1072 The specified service has been marked for deletion.
1073 The specified service already exists.
1074 The system is currently running with the last-known-good configuration.

1075 The dependency service does not exist or has been marked for deletion.
1076 The current boot has already been accepted for use as the last-known-good control set.
1077 No attempts to start the service have been made since the last boot.
1078 The name is already in use as either a service name or a service display name.
1079 The account specified for this service is different from the account specified for other services
running in the same process.
1080 Failure actions can only be set for Win32 services, not for drivers.
1081 This service runs in the same process as the service control manager. Therefore, the service
control manager cannot take action if this service's process terminates unexpectedly.
1082 No recovery program has been configured for this service.
1083 The executable program that this service is configured to run in does not implement the
service.
1084 This service cannot be started in Safe Mode
1100 The physical end of the tape has been reached.
1101 A tape access reached a filemark.
1102 The beginning of the tape or a partition was encountered.
1103 A tape access reached the end of a set of files.
1104 No more data is on the tape.
1105 Tape could not be partitioned.
1106 When accessing a new tape of a multivolume partition, the current block size is incorrect.
1107 Tape partition information could not be found when loading a tape.
1108 Unable to lock the media eject mechanism.
1109 Unable to unload the media.
1110 The media in the drive may have changed.
1111 The I/O bus was reset.
1112 No media in drive.
1113 No mapping for the Unicode character exists in the target multi-byte code page.
1114 A dynamic link library (DLL) initialization routine failed.
1115 A system shutdown is in progress.
1116 Unable to abort the system shutdown because no shutdown was in progress.
1117 The request could not be performed because of an I/O device error.
1118 No serial device was successfully initialized. The serial driver will unload.
1119 Unable to open a device that was sharing an interrupt request (IRQ) with other devices. At
least one other device that uses that IRQ was already opened.
1120 A serial I/O operation was completed by another write to the serial port. (The
IOCTL_SERIAL_XOFF_COUNTER reached zero.)
1121 A serial I/O operation completed because the timeout period expired. (The
IOCTL_SERIAL_XOFF_COUNTER did not reach zero.)
1122 No ID address mark was found on the floppy disk.
1123 Mismatch between the floppy disk sector ID field and the floppy disk controller track address.
1124 The floppy disk controller reported an error that is not recognized by the floppy disk driver.
1125 The floppy disk controller returned inconsistent results in its registers.
1126 While accessing the hard disk, a recalibrate operation failed, even after retries.
1127 While accessing the hard disk, a disk operation failed even after retries.
1128 While accessing the hard disk, a disk controller reset was needed, but even that failed.
1129 Physical end of tape encountered.
1130 Not enough server storage is available to process this command.
1131 A potential deadlock condition has been detected.
1132 The base address or the file offset specified does not have the proper alignment.
1140 An attempt to change the system power state was vetoed by another application or driver.
1141 The system BIOS failed an attempt to change the system power state.
1142 An attempt was made to create more links on a file than the file system supports.
1150 The specified program requires a newer version of Windows.
1151 The specified program is not a Windows or MS-DOS program.
1152 Cannot start more than one instance of the specified program.
1153 The specified program was written for an earlier version of Windows.
1154 One of the library files needed to run this application is damaged.
1155 No application is associated with the specified file for this operation.
1156 An error occurred in sending the command to the application.
1157 One of the library files needed to run this application cannot be found.
1158 The current process has used all of its system allowance of handles for Window Manager
objects.
1159 The message can be used only with synchronous operations.
1160 The indicated source element has no media.
1161 The indicated destination element already contains media.
1162 The indicated element does not exist.
1163 The indicated element is part of a magazine that is not present.
1164 The indicated device requires reinitialization due to hardware errors.

1165 The device has indicated that cleaning is required before further operations are attempted.
1166 The device has indicated that its door is open.
1167 The device is not connected.
1168 Element not found.
1169 There was no match for the specified key in the index.
1170 The property set specified does not exist on the object.
1171 The point passed to GetMouseMovePoints is not in the buffer.
1172 The tracking (workstation) service is not running.
1173 The Volume ID could not be found.
1175 Unable to remove the file to be replaced.
1176 Unable to move the replacement file to the file to be replaced. The file to be replaced has
retained its original name.
1177 Unable to move the replacement file to the file to be replaced. The file to be replaced has been
renamed using the backup name.
1178 The volume change journal is being deleted.
1179 The volume change journal is not active.
1180 A file was found, but it may not be the correct file.
1181 The journal entry has been deleted from the journal.
1200 The specified device name is invalid.
1201 The device is not currently connected but it is a remembered connection.
1202 The local device name has a remembered connection to another network resource.
1203 No network provider accepted the given network path.
1204 The specified network provider name is invalid.
1205 Unable to open the network connection profile.
1206 The network connection profile is corrupted.
1207 Cannot enumerate a noncontainer.
1208 An extended error has occurred.
1209 The format of the specified group name is invalid.
1210 The format of the specified computer name is invalid.
1211 The format of the specified event name is invalid.
1212 The format of the specified domain name is invalid.
1213 The format of the specified service name is invalid.
1214 The format of the specified network name is invalid.
1215 The format of the specified share name is invalid.
1216 The format of the specified password is invalid.
1217 The format of the specified message name is invalid.
1218 The format of the specified message destination is invalid.
1219 Multiple connections to a server or shared resource by the same user, using more than one
user name, are not allowed. Disconnect all previous connections to the server or shared resource
and try again..
1220 An attempt was made to establish a session to a network server, but there are already too
many sessions established to that server.
1221 The workgroup or domain name is already in use by another computer on the network.
1222 The network is not present or not started.
1223 The operation was canceled by the user.
1224 The requested operation cannot be performed on a file with a user-mapped section open.
1225 The remote system refused the network connection.
1226 The network connection was gracefully closed.
1227 The network transport endpoint already has an address associated with it.
1228 An address has not yet been associated with the network endpoint.
1229 An operation was attempted on a nonexistent network connection.
1230 An invalid operation was attempted on an active network connection.
1231 The network location cannot be reached. For information about network troubleshooting, see
Windows Help.
Windows Help.
Windows Help.
1234 No service is operating at the destination network endpoint on the remote system.
1235 The request was aborted.
1236 The network connection was aborted by the local system.
1237 The operation could not be completed. A retry should be performed.
1238 A connection to the server could not be made because the limit on the number of concurrent
connections for this account has been reached.
1239 Attempting to log in during an unauthorized time of day for this account.
1240 The account is not authorized to log in from this station.
1241 The network address could not be used for the operation requested.
1242 The service is already registered.

1243 The specified service does not exist.
1244 The operation being requested was not performed because the user has not been
authenticated.
1245 The operation being requested was not performed because the user has not logged on to the
network. The specified service does not exist.
1246 Continue with work in progress.
1247 An attempt was made to perform an initialization operation when initialization has already
been completed.
1248 No more local devices.
1249 The specified site does not exist.
1250 A domain controller with the specified name already exists.
1251 This operation is supported only when you are connected to the server.
1252 The group policy framework should call the extension even if there are no changes.
1253 The specified user does not have a valid profile.
1254 This operation is not supported on a Microsoft Small Business Server
1255 The server machine is shutting down.
1256 The remote system is not available. For information about network troubleshooting, see
Windows Help.
1257 The security identifier provided is not from an account domain.
1258 The security identifier provided does not have a domain component.
1259 AppHelp dialog canceled thus preventing the application from starting.
1260 Windows cannot open this program because it has been prevented by a software restriction
policy. For more information, open Event Viewer or contact your system administrator.
1261 A program attempt to use an invalid register value. Normally caused by an uninitialized
register. This error is Itanium specific.
1262 The share is currently offline or does not exist.
1263 The kerberos protocol encountered an error while validating the KDC certificate during
smartcard logon.
1264 The kerberos protocol encountered an error while attempting to utilize the smartcard
subsystem.
1265 The system detected a possible attempt to compromise security. Please ensure that you can
contact the server that authenticated you.
1266 The smartcard certificate used for authentication has been revoked. Please contact your
system administrator. There may be additional information in the event log.
1267 An untrusted certificate authority was detected While processing the smartcard certificate
used for authentication. Please contact your system administrator.
1268 The revocation status of the smartcard certificate used for authentication could not be
determined. Please contact your system administrator.
1269 The smartcard certificate used for authentication was not trusted. Please contact your system
administrator.
1270 The smartcard certificate used for authentication has expired. Please contact your system
administrator.
1271 The machine is locked and can not be shut down without the force option.
1273 An application-defined callback gave invalid data when called.
1274 The group policy framework should call the extension in the synchronous foreground policy
refresh.
1275 This driver has been blocked from loading
1276 A dynamic link library (DLL) referenced a module that was neither a DLL nor the process's
executable image.
1300 Not all privileges referenced are assigned to the caller.
1301 Some mapping between account names and security IDs was not done.
1302 No system quota limits are specifically set for this account.
1303 No encryption key is available. A well-known encryption key was returned.
1304 The password is too complex to be converted to a LAN Manager password. The LAN Manager
password returned is a NULL string.
1305 The revision level is unknown.
1306 Indicates two revision levels are incompatible.
1307 This security ID may not be assigned as the owner of this object.
1308 This security ID may not be assigned as the primary group of an object.
1309 An attempt has been made to operate on an impersonation token by a thread that is not
currently impersonating a client.
1310 The group may not be disabled.
1311 There are currently no logon servers available to service the logon request.
1312 A specified logon session does not exist. It may already have been terminated.
1313 A specified privilege does not exist.
1314 A required privilege is not held by the client.
1315 The name provided is not a properly formed account name.
1316 The specified user already exists.

1317 The specified user does not exist.
1318 The specified group already exists.
1319 The specified group does not exist.
1320 Either the specified user account is already a member of the specified group, or the specified
group cannot be deleted because it contains a member.
1321 The specified user account is not a member of the specified group account.
1322 The last remaining administration account cannot be disabled or deleted.
1323 Unable to update the password. The value provided as the current password is incorrect.
1324 Unable to update the password. The value provided for the new password contains values that
are not allowed in passwords.
1325 Unable to update the password. The value provided for the new password does not meet the
length, complexity, or history requirement of the domain.
1326 Logon failure: unknown user name or bad password.
1327 Logon failure: user account restriction. Possible reasons are blank passwords not allowed,
logon hour restrictions, or a policy restriction has been enforced.
1328 Logon failure: account logon time restriction violation.
1329 Logon failure: user not allowed to log on to this computer.
1330 Logon failure: the specified account password has expired.
1331 Logon failure: account currently disabled.
1332 No mapping between account names and security IDs was done.
1333 Too many local user identifiers (LUIDs) were requested at one time.
1334 No more local user identifiers (LUIDs) are available.
1335 The subauthority part of a security ID is invalid for this particular use.
1336 The access control list (ACL) structure is invalid.
1337 The security ID structure is invalid.
1338 The security descriptor structure is invalid.
1340 The inherited access control list (ACL) or access control entry (ACE) could not be built.
1341 The server is currently disabled.
1342 The server is currently enabled.
1343 The value provided was an invalid value for an identifier authority.
1344 No more memory is available for security information updates.
1345 The specified attributes are invalid, or incompatible with the attributes for the group as a
whole.
1346 Either a required impersonation level was not provided, or the provided impersonation level is
invalid.
1347 Cannot open an anonymous level security token.
1348 The validation information class requested was invalid.
1349 The type of the token is inappropriate for its attempted use.
1350 Unable to perform a security operation on an object that has no associated security.
1351 Configuration information could not be read from the domain controller, either because the
machine is unavailable, or access has been denied.
1352 The security account manager (SAM) or local security authority (LSA) server was in the wrong
state to perform the security operation.
1353 The domain was in the wrong state to perform the security operation.
1354 This operation is only allowed for the Primary Domain Controller of the domain.
1355 The specified domain either does not exist or could not be contacted.
1356 The specified domain already exists.
1357 An attempt was made to exceed the limit on the number of domains per server.
1358 Unable to complete the requested operation because of either a catastrophic media failure or a
data structure corruption on the disk.
1359 An internal error occurred.
1360 Generic access types were contained in an access mask which should already be mapped to
nongeneric types.
1361 A security descriptor is not in the right format (absolute or self-relative).
1362 The requested action is restricted for use by logon processes only. The calling process has not
registered as a logon process.
1363 Cannot start a new logon session with an ID that is already in use.
1364 A specified authentication package is unknown.
1365 The logon session is not in a state that is consistent with the requested operation.
1366 The logon session ID is already in use.
1367 A logon request contained an invalid logon type value.
1368 Unable to impersonate using a named pipe until data has been read from that pipe.
1369 The transaction state of a registry subtree is incompatible with the requested operation.
1370 An internal security database corruption has been encountered.
1371 Cannot perform this operation on built-in accounts.
1372 Cannot perform this operation on this built-in special group.
1373 Cannot perform this operation on this built-in special user.
1374 The user cannot be removed from a group because the group is currently the user's primary

group.
1375 The token is already in use as a primary token.
1376 The specified local group does not exist.
1377 The specified account name is not a member of the local group.
1378 The specified account name is already a member of the local group.
1379 The specified local group already exists.
1380 Logon failure: the user has not been granted the requested logon type at this computer.
1381 The maximum number of secrets that may be stored in a single system has been exceeded.
1382 The length of a secret exceeds the maximum length allowed.
1383 The local security authority database contains an internal inconsistency.
1384 During a logon attempt, the user's security context accumulated too many security IDs.
1385 Logon failure: the user has not been granted the requested logon type at this computer.
1386 A cross-encrypted password is necessary to change a user password.
1387 A member could not be added to or removed from the local group because the member does
not exist.
1388 A new member could not be added to a local group because the member has the wrong
account type.
1389 Too many security IDs have been specified.
1390 A cross-encrypted password is necessary to change this user password.
1391 Indicates an ACL contains no inheritable components.
1392 The file or directory is corrupted and unreadable.
1393 The disk structure is corrupted and unreadable.
1394 There is no user session key for the specified logon session.
1395 The service being accessed is licensed for a particular number of connections. No more
connections can be made to the service at this time because there are already as many connections
as the service can accept.
1396 Logon Failure: The target account name is incorrect.
1397 Mutual Authentication failed. The server's password is out of date at the domain controller.
1398 There is a time and/or date difference between the client and server.
1399 This operation can not be performed on the current domain.
1400 Invalid window handle.
1401 Invalid menu handle.
1402 Invalid cursor handle.
1403 Invalid accelerator table handle.
1404 Invalid hook handle.
1405 Invalid handle to a multiple-window position structure.
1406 Cannot create a top-level child window.
1407 Cannot find window class.
1408 Invalid window; it belongs to other thread.
1409 Hot key is already registered.
1410 Class already exists.
1411 Class does not exist.
1412 Class still has open windows.
1413 Invalid index.
1414 Invalid icon handle.
1415 Using private DIALOG window words.
1416 The list box identifier was not found.
1417 No wildcards were found.
1418 Thread does not have a clipboard open.
1419 Hot key is not registered.
1420 The window is not a valid dialog window.
1421 Control ID not found.
1422 Invalid message for a combo box because it does not have an edit control.
1423 The window is not a combo box.
1424 Height must be less than 256.
1425 Invalid device context (DC) handle.
1426 Invalid hook procedure type.
1427 Invalid hook procedure.
1428 Cannot set nonlocal hook without a module handle.
1429 This hook procedure can only be set globally.
1430 The journal hook procedure is already installed.
1431 The hook procedure is not installed.
1432 Invalid message for single-selection list box.
1433 LB_SETCOUNT sent to non-lazy list box.
1434 This list box does not support tab stops.
1435 Cannot destroy object created by another thread.
1436 Child windows cannot have menus.
1437 The window does not have a system menu.

1438 Invalid message box style.
1439 Invalid system-wide (SPI_*) parameter.
1440 Screen already locked.
1441 All handles to windows in a multiple-window position structure must have the same parent.
1442 The window is not a child window.
1443 Invalid GW_* command.
1444 Invalid thread identifier.
1445 Cannot process a message from a window that is not a multiple document interface (MDI)
window.
1446 Popup menu already active.
1447 The window does not have scroll bars.
1448 Scroll bar range cannot be greater than MAXLONG.
1449 Cannot show or remove the window in the way specified.
1450 Insufficient system resources exist to complete the requested service.
1453 Insufficient quota to complete the requested service.
1454 Insufficient quota to complete the requested service.
1455 The paging file is too small for this operation to complete.
1456 A menu item was not found.
1457 Invalid keyboard layout handle.
1458 Hook type not allowed.
1459 This operation requires an interactive window station.
1460 This operation returned because the timeout period expired.
1461 Invalid monitor handle.
1500 The event log file is corrupted.
1501 No event log file could be opened, so the event logging service did not start.
1502 The event log file is full.
1503 The event log file has changed between read operations.
1601 The Windows Installer Service could not be accessed. This can occur if you are running
Windows in safe mode, or if the Windows Installer is not correctly installed. Contact your support
personnel for assistance.
1602 User cancelled installation.
1603 Fatal error during installation.
1604 Installation suspended, incomplete.
1605 This action is only valid for products that are currently installed.
1606 Feature ID not registered.
1607 Component ID not registered.
1608 Unknown property.
1609 Handle is in an invalid state.
1610 The configuration data for this product is corrupt. Contact your support personnel.
1611 Component qualifier not present.
1612 The installation source for this product is not available. Verify that the source exists and that
you can access it.
1613 This installation package cannot be installed by the Windows Installer service. You must install
a Windows service pack that contains a newer version of the Windows Installer service.
1614 Product is uninstalled.
1615 SQL query syntax invalid or unsupported.
1616 Record field does not exist.
1617 The device has been removed.
1618 Another installation is already in progress. Complete that installation before proceeding with
this install.
1619 This installation package could not be opened. Verify that the package exists and that you can
access it, or contact the application vendor to verify that this is a valid Windows Installer package.
1620 This installation package could not be opened. Contact the application vendor to verify that
this is a valid Windows Installer package.
1621 There was an error starting the Windows Installer service user interface. Contact your support
personnel.
1622 Error opening installation log file. Verify that the specified log file location exists and that you
can write to it.
1623 The language of this installation package is not supported by your system.
1624 Error applying transforms. Verify that the specified transform paths are valid.
1625 This installation is forbidden by system policy. Contact your system administrator.
1626 Function could not be executed.
1627 Function failed during execution.
1628 Invalid or unknown table specified.
1629 Data supplied is of wrong type.
1630 Data of this type is not supported.

1631 The Windows Installer service failed to start. Contact your support personnel.
1632 The Temp folder is on a drive that is full or is inaccessible. Free up space on the drive or verify
that you have write permission on the Temp folder.
1633 This installation package is not supported by this processor type. Contact your product vendor.
1634 Component not used on this computer.
1635 This patch package could not be opened. Verify that the patch package exists and that you can
access it, or contact the application vendor to verify that this is a valid Windows Installer patch
package.
1636 This patch package could not be opened. Contact the application vendor to verify that this is a
valid Windows Installer patch package.
1637 This patch package cannot be processed by the Windows Installer service. You must install a
Windows service pack that contains a newer version of the Windows Installer service.
1638 Another version of this product is already installed. Installation of this version cannot continue.
To configure or remove the existing version of this product, use Add/Remove Programs on the
Control Panel.
1639 Invalid command line argument. Consult the Windows Installer SDK for detailed command line
help.
1640 Only administrators have permission to add, remove, or configure server software during a
Terminal services remote session. If you want to install or configure software on the server, contact
your network administrator.
1641 The requested operation completed successfully. The system will be restarted so the changes
can take effect.
1642 The upgrade patch cannot be installed by the Windows Installer service because the program
to be upgraded may be missing, or the upgrade patch may update a different version of the
program. Verify that the program to be upgraded exists on your computer an
1643 The patch package is not permitted by software restriction policy.
1644 One or more customizations are not permitted by software restriction policy.
1700 The string binding is invalid.
1701 The binding handle is not the correct type.
1702 The binding handle is invalid.
1703 The RPC protocol sequence is not supported.
1704 The RPC protocol sequence is invalid.
1705 The string universal unique identifier (UUID) is invalid.
1706 The endpoint format is invalid.
1707 The network address is invalid.
1708 No endpoint was found.
1709 The timeout value is invalid.
1710 The object universal unique identifier (UUID) was not found.
1711 The object universal unique identifier (UUID) has already been registered.
1712 The type universal unique identifier (UUID) has already been registered.
1713 The RPC server is already listening.
1714 No protocol sequences have been registered.
1715 The RPC server is not listening.
1716 The manager type is unknown.
1717 The interface is unknown.
1718 There are no bindings.
1719 There are no protocol sequences.
1720 The endpoint cannot be created.
1721 Not enough resources are available to complete this operation.
1722 The RPC server is unavailable.
1723 The RPC server is too busy to complete this operation.
1724 The network options are invalid.
1725 There are no remote procedure calls active on this thread.
1726 The remote procedure call failed.
1727 The remote procedure call failed and did not execute.
1728 A remote procedure call (RPC) protocol error occurred.
1730 The transfer syntax is not supported by the RPC server.
1732 The universal unique identifier (UUID) type is not supported.
1733 The tag is invalid.
1734 The array bounds are invalid.
1735 The binding does not contain an entry name.
1736 The name syntax is invalid.
1737 The name syntax is not supported.
1739 No network address is available to use to construct a universal unique identifier (UUID).
1740 The endpoint is a duplicate.
1741 The authentication type is unknown.
1742 The maximum number of calls is too small.
1743 The string is too long.

1744 The RPC protocol sequence was not found.
1745 The procedure number is out of range.
1746 The binding does not contain any authentication information.
1747 The authentication service is unknown.
1748 The authentication level is unknown.
1749 The security context is invalid.
1750 The authorization service is unknown.
1751 The entry is invalid.
1752 The server endpoint cannot perform the operation.
1753 There are no more endpoints available from the endpoint mapper.
1754 No interfaces have been exported.
1755 The entry name is incomplete.
1756 The version option is invalid.
1757 There are no more members.
1758 There is nothing to unexport.
1759 The interface was not found.
1760 The entry already exists.
1761 The entry is not found.
1762 The name service is unavailable.
1763 The network address family is invalid.
1764 The requested operation is not supported.
1765 No security context is available to allow impersonation.
1766 An internal error occurred in a remote procedure call (RPC).
1767 The RPC server attempted an integer division by zero.
1768 An addressing error occurred in the RPC server.
1769 A floating-point operation at the RPC server caused a division by zero.
1770 A floating-point underflow occurred at the RPC server.
1771 A floating-point overflow occurred at the RPC server.
1772 The list of RPC servers available for the binding of auto handles has been exhausted.
1773 Unable to open the character translation table file.
1774 The file containing the character translation table has fewer than 512 bytes.
1775 A null context handle was passed from the client to the host during a remote procedure call.
1777 The context handle changed during a remote procedure call.
1778 The binding handles passed to a remote procedure call do not match.
1779 The stub is unable to get the remote procedure call handle.
1780 A null reference pointer was passed to the stub.
1781 The enumeration value is out of range.
1782 The byte count is too small.
1783 The stub received bad data.
1784 The supplied user buffer is not valid for the requested operation.
1785 The disk media is not recognized. It may not be formatted.
1786 The workstation does not have a trust secret.
1787 The security database on the server does not have a computer account for this workstation
trust relationship.
1788 The trust relationship between the primary domain and the trusted domain failed.
1789 The trust relationship between this workstation and the primary domain failed.
1790 The network logon failed.
1791 A remote procedure call is already in progress for this thread.
1792 An attempt was made to logon, but the network logon service was not started.
1793 The user's account has expired.
1794 The redirector is in use and cannot be unloaded.
1795 The specified printer driver is already installed.
1796 The specified port is unknown.
1797 The printer driver is unknown.
1798 The print processor is unknown.
1799 The specified separator file is invalid.
1800 The specified priority is invalid.
1801 The printer name is invalid.
1802 The printer already exists.
1803 The printer command is invalid.
1804 The specified datatype is invalid.
1805 The environment specified is invalid.
1806 There are no more bindings.
1807 The account used is an interdomain trust account. Use your global user account or local user
account to access this server.
1808 The account used is a computer account. Use your global user account or local user account to
access this server.
1809 The account used is a server trust account. Use your global user account or local user account

to access this server.
1810 The name or security ID (SID) of the domain specified is inconsistent with the trust information
for that domain.
1811 The server is in use and cannot be unloaded.
1812 The specified image file did not contain a resource section.
1813 The specified resource type cannot be found in the image file.
1814 The specified resource name cannot be found in the image file.
1815 The specified resource language ID cannot be found in the image file.
1816 Not enough quota is available to process this command.
1817 No interfaces have been registered.
1818 The remote procedure call was cancelled.
1819 The binding handle does not contain all required information.
1820 A communications failure occurred during a remote procedure call.
1821 The requested authentication level is not supported.
1822 No principal name registered.
1823 The error specified is not a valid Windows RPC error code.
1824 A UUID that is valid only on this computer has been allocated.
1825 A security package specific error occurred.
1826 Thread is not canceled.
1827 Invalid operation on the encoding/decoding handle.
1828 Incompatible version of the serializing package.
1829 Incompatible version of the RPC stub.
1830 The RPC pipe object is invalid or corrupted.
1831 An invalid operation was attempted on an RPC pipe object.
1832 Unsupported RPC pipe version.
1898 The group member was not found.
1899 The endpoint mapper database entry could not be created.
1900 The object universal unique identifier (UUID) is the nil UUID.
1901 The specified time is invalid.
1902 The specified form name is invalid.
1903 The specified form size is invalid.
1904 The specified printer handle is already being waited on
1905 The specified printer has been deleted.
1906 The state of the printer is invalid.
1907 The user's password must be changed before logging on the first time.
1908 Could not find the domain controller for this domain.
1909 The referenced account is currently locked out and may not be logged on to.
1910 The object exporter specified was not found.
1911 The object specified was not found.
1912 The object resolver set specified was not found.
1913 Some data remains to be sent in the request buffer.
1914 Invalid asynchronous remote procedure call handle.
1915 Invalid asynchronous RPC call handle for this operation.
1916 The RPC pipe object has already been closed.
1917 The RPC call completed before all pipes were processed.
1918 No more data is available from the RPC pipe.
1919 No site name is available for this machine.
1920 The file can not be accessed by the system.
1921 The name of the file cannot be resolved by the system.
1922 The entry is not of the expected type.
1923 Not all object UUIDs could be exported to the specified entry.
1924 Interface could not be exported to the specified entry.
1925 The specified profile entry could not be added.
1926 The specified profile element could not be added.
1927 The specified profile element could not be removed.
1928 The group element could not be added.
1929 The group element could not be removed.
1930 The printer driver is not compatible with a policy enabled on your computer that blocks NT 4.0
drivers.
1931 The context has expired and can no longer be used.
2000 The pixel format is invalid.
2001 The specified driver is invalid.
2002 The window style or class attribute is invalid for this operation.
2003 The requested metafile operation is not supported.
2004 The requested transformation operation is not supported.
2005 The requested clipping operation is not supported.
2010 The specified color management module is invalid.
2011 The specified color profile is invalid.

2012 The specified tag was not found.
2013 A required tag is not present.
2014 The specified tag is already present.
2015 The specified color profile is not associated with any device.
2016 The specified color profile was not found.
2017 The specified color space is invalid.
2018 Image Color Management is not enabled.
2019 There was an error while deleting the color transform.
2020 The specified color transform is invalid.
2021 The specified transform does not match the bitmap's color space.
2022 The specified named color index is not present in the profile.
2102 The workstation driver is not installed.
2103 The server could not be located.
2104 An internal error occurred. The network cannot access a shared memory segment.
2105 A network resource shortage occurred .
2106 This operation is not supported on workstations.
2107 The device is not connected.
2108 The network connection was made successfully, but the user had to be prompted for a
password other than the one originally specified.
2109 The network connection was made successfully using default credentials.
2114 The Server service is not started.
2115 The queue is empty.
2116 The device or directory does not exist.
2117 The operation is invalid on a redirected resource.
2118 The name has already been shared.
2119 The server is currently out of the requested resource.
2121 Requested addition of items exceeds the maximum allowed.
2122 The Peer service supports only two simultaneous users.
2123 The API return buffer is too small.
2127 A remote API error occurred.
2131 An error occurred when opening or reading the configuration file.
2136 A general network error occurred.
2137 The Workstation service is in an inconsistent state. Restart the computer before restarting the
Workstation service.
2138 The Workstation service has not been started.
2139 The requested information is not available.
2140 An internal Windows 2000 error occurred.
2141 The server is not configured for transactions.
2142 The requested API is not supported on the remote server.
2143 The event name is invalid.
2144 The computer name already exists on the network. Change it and restart the computer.
2146 The specified component could not be found in the configuration information.
2147 The specified parameter could not be found in the configuration information.
2149 A line in the configuration file is too long.
2150 The printer does not exist.
2151 The print job does not exist.
2152 The printer destination cannot be found.
2153 The printer destination already exists.
2154 The printer queue already exists.
2155 No more printers can be added.
2156 No more print jobs can be added.
2157 No more printer destinations can be added.
2158 This printer destination is idle and cannot accept control operations.
2159 This printer destination request contains an invalid control function.
2160 The print processor is not responding.
2161 The spooler is not running.
2162 This operation cannot be performed on the print destination in its current state.
2163 This operation cannot be performed on the printer queue in its current state.
2164 This operation cannot be performed on the print job in its current state.
2165 A spooler memory allocation failure occurred.
2166 The device driver does not exist.
2167 The data type is not supported by the print processor.
2168 The print processor is not installed.
2180 The service database is locked.
2181 The service table is full.
2182 The requested service has already been started.
2183 The service does not respond to control actions.
2184 The service has not been started.

2185 The service name is invalid.
2186 The service is not responding to the control function.
2187 The service control is busy.
2188 The configuration file contains an invalid service program name.
2189 The service could not be controlled in its present state.
2190 The service ended abnormally.
2191 The requested pause or stop is not valid for this service.
2192 The service control dispatcher could not find the service name in the dispatch table.
2193 The service control dispatcher pipe read failed.
2194 A thread for the new service could not be created.
2200 This workstation is already logged on to the local-area network.
2201 The workstation is not logged on to the local-area network.
2202 The specified username is invalid.
2203 The password parameter is invalid.
2204 The logon processor did not add the message alias.
2205 The logon processor did not add the message alias.
2206 The logoff processor did not delete the message alias.
2207 The logoff processor did not delete the message alias.
2209 Network logons are paused.
2210 A centralized logon-server conflict occurred.
2211 The server is configured without a valid user path.
2212 An error occurred while loading or running the logon script.
2214 The logon server was not specified. Your computer will be logged on as STANDALONE.
2215 The logon server could not be found.
2216 There is already a logon domain for this computer.
2217 The logon server could not validate the logon.
2219 The security database could not be found.
2220 The group name could not be found.
2221 The user name could not be found.
2222 The resource name could not be found.
2223 The group already exists.
2224 The account already exists.
2225 The resource permission list already exists.
2226 This operation is only allowed on the primary domain controller of the domain.
2227 The security database has not been started.
2228 There are too many names in the user accounts database.
2229 A disk I/O failure occurred.
2230 The limit of 64 entries per resource was exceeded.
2231 Deleting a user with a session is not allowed.
2232 The parent directory could not be located.
2233 Unable to add to the security database session cache segment.
2234 This operation is not allowed on this special group.
2235 This user is not cached in user accounts database session cache.
2236 The user already belongs to this group.
2237 The user does not belong to this group.
2238 This user account is undefined.
2239 This user account has expired.
2240 The user is not allowed to log on from this workstation.
2241 The user is not allowed to log on at this time.
2242 The password of this user has expired.
2243 The password of this user cannot change.
2244 This password cannot be used now.
2245 The password does not meet the password policy requirements. Check the minimum password
length, password complexity and password history requirements.
2246 The password of this user is too recent to change.
2247 The security database is corrupted.
2248 No updates are necessary to this replicant network/local security database.
2249 This replicant database is outdated; synchronization is required.
2250 This network connection does not exist.
2251 This asg_type is invalid.
2252 This device is currently being shared.
2270 The computer name could not be added as a message alias. The name may already exist on
the network.
2271 The Messenger service is already started.
2272 The Messenger service failed to start.
2273 The message alias could not be found on the network.
2274 This message alias has already been forwarded.
2275 This message alias has been added but is still forwarded.

2276 This message alias already exists locally.
2277 The maximum number of added message aliases has been exceeded.
2278 The computer name could not be deleted.
2279 Messages cannot be forwarded back to the same workstation.
2280 An error occurred in the domain message processor.
2281 The message was sent, but the recipient has paused the Messenger service.
2282 The message was sent but not received.
2283 The message alias is currently in use. Try again later.
2284 The Messenger service has not been started.
2285 The name is not on the local computer.
2286 The forwarded message alias could not be found on the network.
2287 The message alias table on the remote station is full.
2288 Messages for this alias are not currently being forwarded.
2289 The broadcast message was truncated.
2294 This is an invalid device name.
2295 A write fault occurred.
2297 A duplicate message alias exists on the network.
2298 This message alias will be deleted later.
2299 The message alias was not successfully deleted from all networks.
2300 This operation is not supported on computers with multiple networks.
2310 This shared resource does not exist.
2311 This device is not shared.
2312 A session does not exist with that computer name.
2314 There is not an open file with that identification number.
2315 A failure occurred when executing a remote administration command.
2316 A failure occurred when opening a remote temporary file.
2317 The data returned from a remote administration command has been truncated to 64K.
2318 This device cannot be shared as both a spooled and a non-spooled resource.
2319 The information in the list of servers may be incorrect.
2320 The computer is not active in this domain.
2321 The share must be removed from the Distributed File System before it can be deleted.
2331 The operation is invalid for this device.
2332 This device cannot be shared.
2333 This device was not open.
2334 This device name list is invalid.
2335 The queue priority is invalid.
2337 There are no shared communication devices.
2338 The queue you specified does not exist.
2340 This list of devices is invalid.
2341 The requested device is invalid.
2342 This device is already in use by the spooler.
2343 This device is already in use as a communication device.
2351 This computer name is invalid.
2354 The string and prefix specified are too long.
2356 This path component is invalid.
2357 Could not determine the type of input.
2362 The buffer for types is not big enough.
2370 Profile files cannot exceed 64K.
2371 The start offset is out of range.
2372 The system cannot delete current connections to network resources.
2373 The system was unable to parse the command line in this file.
2374 An error occurred while loading the profile file.
2375 Errors occurred while saving the profile file. The profile was partially saved.
2378 This log file has changed between reads.
2380 The source path cannot be a directory.
2381 The source path is illegal.
2382 The destination path is illegal.
2383 The source and destination paths are on different servers.
2385 The Run server you requested is paused.
2389 An error occurred when communicating with a Run server.
2391 An error occurred when starting a background process.
2392 The shared resource you are connected to could not be found.
2400 The LAN adapter number is invalid.
2401 This network connection has files open or requests pending.
2402 Active connections still exist.
2403 This share name or password is invalid.
2404 The device is in use by an active process and cannot be disconnected.
2405 The drive letter is in use locally.

2430 The specified client is already registered for the specified event.
2431 The alert table is full.
2432 An invalid or nonexistent alert name was raised.
2433 The alert recipient is invalid.
2434 A user's session with this server has been deleted because the user's logon hours are no
longer valid.
2440 The log file does not contain the requested record number.
2450 The user accounts database is not configured correctly.
2451 This operation is not permitted when the Netlogon service is running.
2452 This operation is not allowed on the last administrative account.
2453 Could not find domain controller for this domain.
2454 Could not set logon information for this user.
2455 The Netlogon service has not been started.
2456 Unable to add to the user accounts database.
2457 This server's clock is not synchronized with the primary domain controller's clock.
2458 A password mismatch has been detected.
2460 The server identification does not specify a valid server.
2461 The session identification does not specify a valid session.
2462 The connection identification does not specify a valid connection.
2463 There is no space for another entry in the table of available servers.
2464 The server has reached the maximum number of sessions it supports.
2465 The server has reached the maximum number of connections it supports.
2466 The server cannot open more files because it has reached its maximum number.
2467 There are no alternate servers registered on this server.
2470 Try down-level (remote admin protocol) version of API instead.
2480 The UPS driver could not be accessed by the UPS service.
2481 The UPS service is not configured correctly.
2482 The UPS service could not access the specified Comm Port.
2483 The UPS indicated a line fail or low battery situation. Service not started.
2484 The UPS service failed to perform a system shut down.
2500 The program below returned an MS-DOS error code:
2501 The program below needs more memory:
2502 The program below called an unsupported MS-DOS function:
2503 The workstation failed to boot.
2504 The file below is corrupt.
2505 No loader is specified in the boot-block definition file.
2506 NetBIOS returned an error: The NCB and SMB are dumped above.
2507 A disk I/O error occurred.
2508 Image parameter substitution failed.
2509 Too many image parameters cross disk sector boundaries.
2510 The image was not generated from an MS-DOS diskette formatted with /S.
2511 Remote boot will be restarted later.
2512 The call to the Remoteboot server failed.
2513 Cannot connect to the Remoteboot server.
2514 Cannot open image file on the Remoteboot server.
2515 Connecting to the Remoteboot server...
2516 Connecting to the Remoteboot server...
2517 Remote boot service was stopped; check the error log for the cause of the problem.
2518 Remote boot startup failed; check the error log for the cause of the problem.
2519 A second connection to a Remoteboot resource is not allowed.
2550 The browser service was configured with MaintainServerList=No.
2610 Service failed to start since none of the network adapters started with this service.
2611 Service failed to start due to bad startup information in the registry.
2612 Service failed to start because its database is absent or corrupt.
2613 Service failed to start because RPLFILES share is absent.
2614 Service failed to start because RPLUSER group is absent.
2615 Cannot enumerate service records.
2616 Workstation record information has been corrupted.
2617 Workstation record was not found.
2618 Workstation name is in use by some other workstation.
2619 Profile record information has been corrupted.
2620 Profile record was not found.
2621 Profile name is in use by some other profile.
2622 There are workstations using this profile.
2623 Configuration record information has been corrupted.
2624 Configuration record was not found.
2625 Adapter id record information has been corrupted.
2626 An internal service error has occurred.

2627 Vendor id record information has been corrupted.
2628 Boot block record information has been corrupted.
2629 The user account for this workstation record is missing.
2630 The RPLUSER local group could not be found.
2631 Boot block record was not found.
2632 Chosen profile is incompatible with this workstation.
2633 Chosen network adapter id is in use by some other workstation.
2634 There are profiles using this configuration.
2635 There are workstations, profiles or configurations using this boot block.
2636 Service failed to backup Remoteboot database.
2637 Adapter record was not found.
2638 Vendor record was not found.
2639 Vendor name is in use by some other vendor record.
2640 (boot name, vendor id) is in use by some other boot block record.
2641 Configuration name is in use by some other configuration.
2660 The internal database maintained by the DFS service is corrupt
2661 One of the records in the internal DFS database is corrupt
2662 There is no DFS name whose entry path matches the input Entry Path
2663 A root or link with the given name already exists
2664 The server share specified is already shared in the DFS
2665 The indicated server share does not support the indicated DFS namespace
2666 The operation is not valid on this portion of the namespace
2667 The operation is not valid on this portion of the namespace
2668 The operation is ambiguous because the link has multiple servers
2669 Unable to create a link
2670 The server is not DFS Aware
2671 The specified rename target path is invalid
2672 The specified DFS link is offline
2673 The specified server is not a server for this link
2674 A cycle in the DFS name was detected
2675 The operation is not supported on a server-based DFS
2676 This link is already supported by the specified server-share
2677 Can't remove the last server-share supporting this root or link
2678 The operation is not supported for an Inter-DFS link
2679 The internal state of the DFS Service has become inconsistent
2680 The DFS Service has been installed on the specified server
2681 The DFS data being reconciled is identical
2682 The DFS root cannot be deleted - Uninstall DFS if required
2683 A child or parent directory of the share is already in a DFS
2690 DFS internal error
2691 This machine is already joined to a domain.
2692 This machine is not currently joined to a domain.
2693 This machine is a domain controller and cannot be unjoined from a domain.
2694 The destination domain controller does not support creating machine accounts in OUs.
2695 The specified workgroup name is invalid.
2696 The specified computer name is incompatible with the default language used on the domain
controller.
2697 The specified computer account could not be found.
2698 This version of Windows cannot be joined to a domain.
2999 This is the last error in NERR range.
3000 The specified print monitor is unknown.
3001 The specified printer driver is currently in use.
3002 The spool file was not found.
3003 A StartDocPrinter call was not issued.
3004 An AddJob call was not issued.
3005 The specified print processor has already been installed.
3006 The specified print monitor has already been installed.
3007 The specified print monitor does not have the required functions.
3008 The specified print monitor is currently in use.
3009 The requested operation is not allowed when there are jobs queued to the printer.
3010 The requested operation is successful. Changes will not be effective until the system is
rebooted.
3011 The requested operation is successful. Changes will not be effective until the service is
restarted.
3012 No printers were found.
3013 The printer driver is known to be unreliable.
3014 The printer driver is known to harm the system.
3023 There is a problem with a configuration of user specified shut down command file. The UPS

service started anyway.
3029 Local security could not be started because the user accounts database (NET.ACC) was
missing or corrupted, and no usable backup database was present. THE SYSTEM IS NOT SECURE.
3037 @I *LOGON HOURS
3039 Replicator limit for files in a directory has been exceeded.
3040 Replicator limit for tree depth has been exceeded.
3046 Cannot log on. User is currently logged on and argument TRYUSER is set to NO.
3052 The required parameter was not provided on the command line or in the configuration file.
3054 A request for resource could not be satisfied.
3055 A problem exists with the system configuration.
3056 A system error has occurred.
3057 An internal consistency error has occurred.
3058 The configuration file or the command line has an ambiguous option.
3059 The configuration file or the command line has a duplicate parameter.
3060 The service did not respond to control and was stopped with the DosKillProc function.
3061 An error occurred when attempting to run the service program.
3062 The sub-service failed to start.
3064 There is a problem with the file.
3070 memory
3071 disk space
3072 thread
3073 process
3074 Security Failure.
3075 Bad or missing LAN Manager root directory.
3076 The network software is not installed.
3077 The server is not started.
3078 The server cannot access the user accounts database (NET.ACC).
3079 Incompatible files are installed in the LANMAN tree.
3080 The LANMAN\LOGS directory is invalid.
3081 The domain specified could not be used.
3082 The computer name is being used as a message alias on another computer.
3083 The announcement of the server name failed.
3084 The user accounts database is not configured correctly.
3085 The server is not running with user-level security.
3087 The workstation is not configured properly.
3088 View your error log for details.
3089 Unable to write to this file.
3090 ADDPAK file is corrupted. Delete LANMAN\NETPROG\ADDPAK.SER and reapply all ADDPAKs.
3091 The LM386 server cannot be started because CACHE.EXE is not running.
3092 There is no account for this computer in the security database.
3093 This computer is not a member of the group SERVERS.
3094 The group SERVERS is not present in the local security database.
3095 This computer is configured as a member of a workgroup, not as a member of a domain. The
Netlogon service does not need to run in this configuration.
3096 The primary Domain Controller for this domain could not be located.
3098 The service failed to authenticate with the primary domain controller.
3099 There is a problem with the security database creation date or serial number.
3100 The operation failed because a network software error occurred.
3102 The service failed to obtain a long-term lock on the segment for network control blocks (NCBs).
The error code is the data.
3103 The service failed to release the long-term lock on the segment for network control blocks
(NCBs). The error code is the data.
3106 An unexpected network control block (NCB) was received. The NCB is the data.
3107 The network is not started.
3108 A DosDevIoctl or DosFsCtl to NETWKSTA.SYS failed. The data shown is in this format: DWORD
approx CS:IP of call to ioctl or fsctl WORD error code WORD ioctl or fsctl number
3111 An unexpected NetBIOS error occurred. The error code is the data.
3112 An illegal server message block (SMB) was received. The SMB is the data.
3114 Some entries in the error log were lost because of a buffer overflow.
3120 Initialization parameters controlling resource usage other than net buffers are sized so that too
much memory is needed.
3121 The server cannot increase the size of a memory segment.
3124 The server failed to start. Either all three chdev parameters must be zero or all three must be
nonzero.
3129 The server cannot update the AT schedule file. The file is corrupted.
3130 The server encountered an error when calling NetIMakeLMFileName. The error code is the
data.
3132 Longterm lock of the server buffers failed. Check swap disk's free space and restart the system

to start the server.
3140 The service has stopped due to repeated consecutive occurrences of a network control block
(NCB) error. The last bad NCB follows in raw data.
3141 The Message server has stopped due to a lock on the Message server shared data segment.
3151 Unable to display message POPUP due to system VIO call error. The error code is the data.
3152 An illegal server message block (SMB) was received. The SMB is the data.
3160 The workstation information segment is bigger than 64K. The size follows, in DWORD format:
3161 The workstation was unable to get the name-number of the computer.
3162 The workstation could not initialize the Async NetBIOS Thread. The error code is the data.
3163 The workstation could not open the initial shared segment. The error code is the data.
3164 The workstation host table is full.
3165 A bad mailslot server message block (SMB) was received. The SMB is the data.
3166 The workstation encountered an error while trying to start the user accounts database. The
error code is the data.
3167 The workstation encountered an error while responding to an SSI revalidation request. The
function code and the error codes are the data.
3174 The server could not read the AT schedule file.
3175 The server found an invalid AT schedule record.
3176 The server could not find an AT schedule file so it created one.
3185 Local security could not be started because the user accounts database (NET.ACC) was
missing or corrupted, and no usable backup database was present. THE SYSTEM IS NOT SECURE.
3204 The server could not create a thread. The THREADS parameter in the CONFIG.SYS file should
be increased.
3213 Replicator limit for files in a directory has been exceeded.
3214 Replicator limit for tree depth has been exceeded.
3215 Unrecognized message received in mailslot.
3217 Cannot log on. User is currently logged on and argument TRYUSER is set to NO.
3230 A power failure was detected at the server.
3231 The UPS service performed server shut down.
3232 The UPS service did not complete execution of the user specified shut down command file.
3233 The UPS driver could not be opened. The error code is the data.
3234 Power has been restored.
3235 There is a problem with a configuration of user specified shut down command file.
3256 There was an unrecoverable error in the dynamic- link library of the service.
3257 The system returned an unexpected error code. The error code is the data.
3258 The fault-tolerance error log file, LANROOT\LOGS\FT.LOG, is more than 64K.
3259 The fault-tolerance error-log file, LANROOT\LOGS\FT.LOG, had the update in progress bit set
upon opening, which means that the system crashed while working on the error log.
3301 Remote IPC
3302 Remote Admin
3303 Logon server share
3304 A network error occurred.
3400 There is not enough memory to start the Workstation service.
3401 An error occurred when reading the NETWORKS entry in the LANMAN.INI file.
3404 There are too many NETWORKS entries in the LANMAN.INI file.
3408 The program cannot be used with this operating system.
3409 The redirector is already installed.
3411 There was an error installing NETWKSTA.SYS. Press ENTER to continue.
3412 Resolver linkage problem.
3419 You have open files or devices, and a forced disconnection may cause you to lose data.
3420 Default Share for Internal Use
3421 Messenger Service
3500 The command completed successfully.
3501 You used an invalid option.
3503 The command contains an invalid number of arguments.
3504 The command completed with one or more errors.
3505 You used an option with an invalid value.
3510 A command was used with conflicting switches.
3512 The software requires a newer version of the operating system.
3513 More data is available than can be returned by Windows.
3515 This command can be used only on a Windows Domain Controller.
3516 This command cannot be used on a Windows Domain Controller.
3520 These Windows services are started:
3525 Stopping the Workstation service also stops the Server service.
3526 The workstation has open files.
3533 The service is starting or stopping. Please try again later.
3534 The service did not report an error.
3535 An error occurred controlling the device.

3660 These workstations have sessions on this server:
3661 These workstations have sessions with open files on this server:
3666 The message alias is forwarded.
3670 You have these remote connections:
3671 Continuing will cancel the connections.
3676 New connections will be remembered.
3677 New connections will not be remembered.
3678 An error occurred while saving your profile. The state of your remembered connections has not
changed.
3679 An error occurred while reading your profile.
3682 No network services are started.
3683 There are no entries in the list.
3689 The Workstation service is already running. Windows will ignore command options for the
workstation.
3694 The shared queue cannot be deleted while a print job is being spooled to the queue.
3710 An error occurred while opening the Help file.
3711 The Help file is empty.
3712 The Help file is corrupted.
3714 This operation is privileged on systems with earlier versions of the software.
3716 The device type is unknown.
3717 The log file has been corrupted.
3718 Program filenames must end with .EXE.
3719 A matching share could not be found so nothing was deleted.
3720 A bad value is in the units-per-week field of the user record.
3725 An error occurred when the share was deleted.
3726 The user name is invalid.
3727 The password is invalid.
3728 The passwords do not match.
3729 Your persistent connections were not all restored.
3730 This is not a valid computer name or domain name.
3732 Default permissions cannot be set for that resource.
3734 A valid password was not entered.
3735 A valid name was not entered.
3736 The resource named cannot be shared.
3737 The permissions string contains invalid permissions.
3738 You can only perform this operation on printers and communication devices.
3743 The server is not configured for remote administration.
3752 No users have sessions with this server.
3756 This is an invalid response.
3757 No valid response was provided.
3758 The destination list provided does not match the destination list of the printer queue.
3761 The time range specified ends before it starts.
3764 Time supplied is not exactly on the hour.
3765 12 and 24 hour time formats may not be mixed.
3767 An illegal date format has been supplied.
3768 An illegal day range has been supplied.
3769 An illegal time range has been supplied.
3770 Arguments to NET USER are invalid. Check the minimum password length and/or arguments
supplied.
3771 The value for ENABLESCRIPT must be YES.
3773 An illegal country code has been supplied.
3774 The user was successfully created but could not be added to the USERS local group.
3775 The user context supplied is invalid.
3777 Sending files is no longer supported.
3778 You may not specify paths for ADMIN$ and IPC$ shares.
3784 Only disk shares can be marked as cacheable
3802 This schedule date is invalid.
3803 The LANMAN root directory is unavailable.
3804 The SCHED.LOG file could not be opened.
3805 The Server service has not been started.
3806 The AT job ID does not exist.
3807 The AT schedule file is corrupted.
3808 The delete failed due to a problem with the AT schedule file.
3809 The command line cannot exceed 259 characters.
3810 The AT schedule file could not be updated because the disk is full.
3812 The AT schedule file is invalid. Please delete the file and create a new one.
3813 The AT schedule file was deleted.
3814 The syntax of this command is: AT [id] [/DELETE] AT time [/EVERY:date | /NEXT:date] command

The AT command schedules a program command to run at a later date and time on a server. It also
displays the list of programs and commands scheduled to be run.
3815 The AT command has timed-out. Please try again later.
3816 The minimum password age for user accounts cannot be greater than the maximum password
age.
3817 You have specified a value that is incompatible with servers with down-level software. Please
specify a lower value.
3901 ****
3902 **** unexpected end of message ****
3905 Press ESC to exit
3906 ...
3912 Could not locate a time-server.
3915 The user's home directory could not be determined.
3916 The user's home directory has not been specified.
3920 There are no available drive letters left.
3936 This computer is not currently configured to use a specific SNTP server.
3953 The syntax is incorrect.
3960 You specified an invalid file number.
3961 You specified an invalid print job number.
3963 The user or group account specified cannot be found.
3965 The user was added but could not be enabled for File and Print Services for NetWare.
3966 File and Print Services for NetWare is not installed.
3967 Cannot set user properties for File and Print Services for NetWare.
3969 NetWare compatible logon
4000 WINS encountered an error while processing the command.
4001 The local WINS can not be deleted.
4002 The importation from the file failed.
4003 The backup failed. Was a full backup done before?
4004 The backup failed. Check the directory to which you are backing the database.
4005 The name does not exist in the WINS database.
4006 Replication with a nonconfigured partner is not allowed.
4100 The DHCP client has obtained an IP address that is already in use on the network. The local
interface will be disabled until the DHCP client can obtain a new address.
4200 The GUID passed was not recognized as valid by a WMI data provider.
4201 The instance name passed was not recognized as valid by a WMI data provider.
4202 The data item ID passed was not recognized as valid by a WMI data provider.
4203 The WMI request could not be completed and should be retried.
4204 The WMI data provider could not be located.
4205 The WMI data provider references an instance set that has not been registered.
4206 The WMI data block or event notification has already been enabled.
4207 The WMI data block is no longer available.
4208 The WMI data service is not available.
4209 The WMI data provider failed to carry out the request.
4210 The WMI MOF information is not valid.
4211 The WMI registration information is not valid.
4212 The WMI data block or event notification has already been disabled.
4213 The WMI data item or data block is read only.
4214 The WMI data item or data block could not be changed.
4300 The media identifier does not represent a valid medium.
4301 The library identifier does not represent a valid library.
4302 The media pool identifier does not represent a valid media pool.
4303 The drive and medium are not compatible or exist in different libraries.
4304 The medium currently exists in an offline library and must be online to perform this operation.
4305 The operation cannot be performed on an offline library.
4306 The library, drive, or media pool is empty.
4307 The library, drive, or media pool must be empty to perform this operation.
4308 No media is currently available in this media pool or library.
4309 A resource required for this operation is disabled.
4310 The media identifier does not represent a valid cleaner.
4311 The drive cannot be cleaned or does not support cleaning.
4312 The object identifier does not represent a valid object.
4313 Unable to read from or write to the database.
4314 The database is full.
4315 The medium is not compatible with the device or media pool.
4316 The resource required for this operation does not exist.
4317 The operation identifier is not valid.
4318 The media is not mounted or ready for use.
4319 The device is not ready for use.

4320 The operator or administrator has refused the request.
4321 The drive identifier does not represent a valid drive.
4322 Library is full. No slot is available for use.
4323 The transport cannot access the medium.
4324 Unable to load the medium into the drive.
4325 Unable to retrieve the drive status.
4326 Unable to retrieve the slot status.
4327 Unable to retrieve status about the transport.
4328 Cannot use the transport because it is already in use.
4329 Unable to open or close the inject/eject port.
4330 Unable to eject the medium because it is in a drive.
4331 A cleaner slot is already reserved.
4332 A cleaner slot is not reserved.
4333 The cleaner cartridge has performed the maximum number of drive cleanings.
4334 Unexpected on-medium identifier.
4335 The last remaining item in this group or resource cannot be deleted.
4336 The message provided exceeds the maximum size allowed for this parameter.
4337 The volume contains system or paging files.
4338 The media type cannot be removed from this library since at least one drive in the library
reports it can support this media type.
4339 This offline media cannot be mounted on this system since no enabled drives are present
which can be used.
4340 A cleaner cartridge is present in the tape library.
4341 (Y/N) [N]
4342 Error
4343 OK
4344 Y
4345 N
4346 Any
4347 A
4348 P
4349 (not found)
4350 The remote storage service was not able to recall the file.
4351 The remote storage service is not operational at this time.
4352 The remote storage service encountered a media error.
4354 Please type the password:
4358 Type a password for the user:
4359 Type the password for the shared resource:
4360 Type your password:
4361 Retype the password to confirm:
4362 Type the user's old password:
4363 Type the user's new password:
4364 Type your new password:
4365 Type the Replicator service password:
4368 Type your user name:
4372 Print job detail
4378 The following running services can be controlled:
4379 Statistics are available for the following running services:
4381 The syntax of this command is:
4382 The options of this command are:
4383 Please enter the name of the Primary Domain Controller:
4385 Sunday
4386 Monday
4387 Tuesday
4388 Wednesday
4389 Thursday
4390 The file or directory is not a reparse point.
4391 The reparse point attribute cannot be set because it conflicts with an existing attribute.
4392 The data present in the reparse point buffer is invalid.
4393 The tag present in the reparse point buffer is invalid.
4394 There is a mismatch between the tag specified in the request and the tag present in the
reparse point.
4395 W
4396 Th
4397 F
4398 S
4399 Sa
4401 Group name

4402 Comment
4403 Members
4406 Alias name
4407 Comment
4408 Members
4411 User name
4412 Full Name
4413 Comment
4414 User's comment
4415 Parameters
4416 Country code
4417 Privilege level
4418 Operator privileges
4419 Account active
4420 Account expires
4421 Password last set
4422 Password expires
4423 Password changeable
4424 Workstations allowed
4425 Maximum disk space
4426 Unlimited
4427 Local Group Memberships
4428 Domain controller
4429 Logon script
4430 Last logon
4431 Global Group memberships
4432 Logon hours allowed
4433 All
4434 None
4436 Home directory
4437 Password required
4438 User may change password
4439 User profile
4440 Locked
4450 Computer name
4451 User name
4452 Software version
4453 Workstation active on
4454 Windows NT root directory
4455 Workstation domain
4456 Logon domain
4457 Other domain(s)
4458 COM Open Timeout (sec)
4459 COM Send Count (byte)
4460 COM Send Timeout (msec)
4461 DOS session print time-out (sec)
4462 Maximum error log size (K)
4463 Maximum cache memory (K)
4464 Number of network buffers
4465 Number of character buffers
4466 Size of network buffers
4467 Size of character buffers
4468 Full Computer name
4469 Workstation Domain DNS Name
4470 Windows 2002
4481 Server Name
4482 Server Comment
4483 Send administrative alerts to
4484 Software version
4485 Peer Server
4486 Windows NT
4487 Server Level
4488 Windows NT Server
4489 Server is active on
4492 Server hidden
4500 Single Instance Storage is not available on this volume.
4506 Maximum Logged On Users
4507 Maximum concurrent administrators

4508 Maximum resources shared
4509 Maximum connections to resources
4510 Maximum open files on server
4511 Maximum open files per session
4512 Maximum file locks
4520 Idle session time (min)
4526 Share-level
4527 User-level
4530 Unlimited Server
4570 Force user logoff how long after time expires?:
4571 Lock out account after how many bad passwords?:
4572 Minimum password age (days):
4573 Maximum password age (days):
4574 Minimum password length:
4575 Length of password history maintained:
4576 Computer role:
4577 Primary Domain controller for workstation domain:
4578 Lockout threshold:
4579 Lockout duration (minutes):
4580 Lockout observation window (minutes):
4600 Statistics since
4601 Sessions accepted
4602 Sessions timed-out
4603 Sessions errored-out
4604 Kilobytes sent
4605 Kilobytes received
4606 Mean response time (msec)
4607 Network errors
4608 Files accessed
4609 Print jobs spooled
4610 System errors
4611 Password violations
4612 Permission violations
4613 Communication devices accessed
4614 Sessions started
4615 Sessions reconnected
4616 Sessions starts failed
4617 Sessions disconnected
4618 Network I/O's performed
4619 Files and pipes accessed
4620 Times buffers exhausted
4621 Big buffers
4622 Request buffers
4626 Connections made
4627 Connections failed
4630 Bytes received
4631 Server Message Blocks (SMBs) received
4632 Bytes transmitted
4633 Server Message Blocks (SMBs) transmitted
4634 Read operations
4635 Write operations
4636 Raw reads denied
4637 Raw writes denied
4638 Network errors
4639 Connections made
4640 Reconnections made
4641 Server disconnects
4642 Sessions started
4643 Hung sessions
4644 Failed sessions
4645 Failed operations
4646 Use count
4647 Failed use count
4655 The message name forwarding was successfully canceled.
4661 The password was changed successfully.
4664 The message was successfully sent to all users of the network.
4666 The message was successfully sent to all users of this server.
4696 Windows NT Server

4697 Windows NT Workstation
4698 MS-DOS Enhanced Workstation
4700 Server Name Remark
4702 (UNC)
4703 ...
4704 Domain
4706 Invalid network provider. Available networks are:
4710 Disk
4711 Print
4712 Comm
4713 IPC
4714 Status Local Remote Network
4715 OK
4716 Dormant
4717 Paused
4718 Disconnected
4719 Error
4720 Connecting
4721 Reconnecting
4722 Status
4723 Local name
4724 Remote name
4725 Resource type
4726 # Opens
4727 # Connections
4728 Unavailable
4730 Share name Resource Remark
4731 Share name
4732 Resource
4733 Spooled
4734 Permission
4735 Maximum users
4736 No limit
4737 Users
4739 Caching
4740 ID Path User name # Locks
4741 File ID
4742 Locks
4743 Permissions
4744 Share name
4745 Type
4746 Used as
4747 Comment
4750 Computer User name Client Type Opens Idle time
4751 Computer
4752 Sess time
4753 Idle time
4754 Share name Type # Opens
4755 Client type
4756 Guest logon
4770 Manual caching of documents
4771 Automatic caching of documents
4772 Automatic caching of programs and documents
4773 Caching disabled
4774 Automatic
4775 Manual
4776 Documents
4777 Programs
4778 None
4800 Name
4801 Forwarded to
4802 Forwarded to you from
4803 Users of this server
4804 Net Send has been interrupted by a Ctrl+Break from the user.
4810 Name Job # Size Status
4811 jobs
4812 Print
4813 Name

4814 Job #
4815 Size
4816 Status
4817 Separator file
4818 Comment
4819 Priority
4820 Print after
4821 Print until
4822 Print processor
4823 Additional info
4824 Parameters
4825 Print Devices
4826 Printer Active
4827 Printer held
4828 Printer error
4829 Printer being deleted
4830 Printer status unknown
4841 Job #
4842 Submitting user
4843 Notify
4844 Job data type
4845 Job parameters
4846 Waiting
4847 Held in queue
4848 Spooling
4849 Paused
4850 Offline
4851 Error
4852 Out of paper
4853 Intervention required
4854 Printing
4855 on
4862 Driver
4930 User name Type Date
4931 Lockout
4932 Service
4933 Server
4934 Server started
4935 Server paused
4936 Server continued
4937 Server stopped
4938 Session
4939 Logon Guest
4940 Logon User
4941 Logon Administrator
4942 Logoff normal
4943 Logon
4944 Logoff error
4945 Logoff auto-disconnect
4946 Logoff administrator-disconnect
4947 Logoff forced by logon restrictions
4948 Service
4957 Account
4964 Account system settings were modified
4965 Logon restriction
4966 Limit exceeded: UNKNOWN
4967 Limit exceeded: Logon hours
4968 Limit exceeded: Account expired
4969 Limit exceeded: Workstation ID invalid
4970 Limit exceeded: Account disabled
4971 Limit exceeded: Account deleted
4972 Share
4978 Bad password
4979 Administrator privilege required
4980 Access
4984 Access denied
4985 Unknown
4986 Other

4987 Duration:
4988 Duration: Not available
4989 Duration: Less than one second
4990 (none)
4994 Access ended
4995 Log on to network
4996 Logon denied
4997 Program Message Time
4999 Account unlocked by administrator
5000 Log off network
5001 The cluster resource cannot be moved to another group because other resources are
dependent on it.
5002 The cluster resource dependency cannot be found.
5003 The cluster resource cannot be made dependent on the specified resource because it is
already dependent.
5004 The cluster resource is not online.
5005 A cluster node is not available for this operation.
5006 The cluster resource is not available.
5007 The cluster resource could not be found.
5008 The cluster is being shut down.
5009 A cluster node cannot be evicted from the cluster unless the node is down or it is the last node.
5010 The object already exists.
5011 The object is already in the list.
5012 The cluster group is not available for any new requests.
5013 The cluster group could not be found.
5014 The operation could not be completed because the cluster group is not online.
5015 The cluster node is not the owner of the resource.
5016 The cluster node is not the owner of the group.
5017 The cluster resource could not be created in the specified resource monitor.
5018 The cluster resource could not be brought online by the resource monitor.
5019 The operation could not be completed because the cluster resource is online.
5020 The cluster resource could not be deleted or brought offline because it is the quorum resource.
5021 The cluster could not make the specified resource a quorum resource because it is not capable
of being a quorum resource.
5022 The cluster software is shutting down.
5023 The group or resource is not in the correct state to perform the requested operation.
5024 The properties were stored but not all changes will take effect until the next time the resource
is brought online.
5025 The cluster could not make the specified resource a quorum resource because it does not
belong to a shared storage class.
5026 The cluster resource could not be deleted since it is a core resource.
5027 The quorum resource failed to come online.
5028 The quorum log could not be created or mounted successfully.
5029 The cluster log is corrupt.
5030 The record could not be written to the cluster log since it exceeds the maximum size.
5031 The cluster log exceeds its maximum size.
5032 No checkpoint record was found in the cluster log.
5033 The minimum required disk space needed for logging is not available.
5034 The cluster node failed to take control of the quorum resource because the resource is owned
by another active node.
5035 A cluster network is not available for this operation.
5036 A cluster node is not available for this operation.
5037 All cluster nodes must be running to perform this operation.
5038 A cluster resource failed.
5039 The cluster node is not valid.
5040 The cluster node already exists.
5041 A node is in the process of joining the cluster.
5042 The cluster node was not found.
5043 The cluster local node information was not found.
5044 The cluster network already exists.
5045 The cluster network was not found.
5046 The cluster network interface already exists.
5047 The cluster network interface was not found.
5048 The cluster request is not valid for this object.
5049 The cluster network provider is not valid.
5050 The cluster node is down.
5051 The cluster node is not reachable.
5052 The cluster node is not a member of the cluster.

5053 A cluster join operation is not in progress.
5054 The cluster network is not valid.
5055 Mar
5056 The cluster node is up.
5057 The cluster IP address is already in use.
5058 The cluster node is not paused.
5059 No cluster security context is available.
5060 The cluster network is not configured for internal cluster communication.
5061 The cluster node is already up.
5062 The cluster node is already down.
5063 The cluster network is already online.
5064 The cluster network is already offline.
5065 The cluster node is already a member of the cluster.
5066 The cluster network is the only one configured for internal cluster communication between two
or more active cluster nodes. The internal communication capability cannot be removed from the
network.
5067 One or more cluster resources depend on the network to provide service to clients. The client
access capability cannot be removed from the network.
5068 This operation cannot be performed on the cluster resource as it the quorum resource. You
may not bring the quorum resource offline or modify its possible owners list.
5069 The cluster quorum resource is not allowed to have any dependencies.
5070 The cluster node is paused.
5071 The cluster resource cannot be brought online. The owner node cannot run this resource.
5072 The cluster node is not ready to perform the requested operation.
5073 The cluster node is shutting down.
5074 The cluster join operation was aborted.
5075 The cluster join operation failed due to incompatible software versions between the joining
node and its sponsor.
5076 This resource cannot be created because the cluster has reached the limit on the number of
resources it can monitor.
5077 The system configuration changed during the cluster join or form operation. The join or form
operation was aborted.
5078 The specified resource type was not found.
5079 The specified node does not support a resource of this type. This may be due to version
inconsistencies or due to the absence of the resource DLL on this node.
5080 The specified resource name is not supported by this resource DLL. This may be due to a bad
(or changed) name supplied to the resource DLL.
5081 No authentication package could be registered with the RPC server.
5082 You cannot bring the group online because the owner of the group is not in the preferred list
for the group. To change the owner node for the group, move the group.
5083 The join operation failed because the cluster database sequence number has changed or is
incompatible with the locker node. This may happen during a join operation if the cluster database
was changing during the join.
5084 The resource monitor will not allow the fail operation to be performed while the resource is in
its current state. This may happen if the resource is in a pending state.
5085 A non locker code got a request to reserve the lock for making global updates.
5086 The quorum disk could not be located by the cluster service.
5087 The backed up cluster database is possibly corrupt.
5088 A DFS root already exists in this cluster node.
5089 An attempt to modify a resource property failed because it conflicts with another existing
property.
5090 Spain
5091 Denmark
5092 Sweden
5093 Norway
5094 Germany
5095 Australia
5096 Japan
5097 Korea
5098 China (PRC)
5099 Taiwan
5100 Asia
5101 Portugal
5102 Finland
5103 Arabic
5104 Hebrew
5153 The UPS service is about to perform final shut down.
5170 The Workstation must be started with the NET START command.

5175 Remote IPC
5176 Remote Admin
5177 Default share
5291 Never
5292 Never
5293 Never
5295 NET.HLP
5296 NET.HLP
5300 The network control block (NCB) request completed successfully. The NCB is the data.
5301 Illegal network control block (NCB) buffer length on SEND DATAGRAM, SEND BROADCAST,
ADAPTER STATUS, or SESSION STATUS. The NCB is the data.
5302 The data descriptor array specified in the network control block (NCB) is invalid. The NCB is the
data.
5303 The command specified in the network control block (NCB) is illegal. The NCB is the data.
5304 The message correlator specified in the network control block (NCB) is invalid. The NCB is the
data.
5305 A network control block (NCB) command timed-out. The session may have terminated
abnormally. The NCB is the data.
5306 An incomplete network control block (NCB) message was received. The NCB is the data.
5307 The buffer address specified in the network control block (NCB) is illegal. The NCB is the data.
5308 The session number specified in the network control block (NCB) is not active. The NCB is the
data.
5309 No resource was available in the network adapter. The network control block (NCB) request
was refused. The NCB is the data.
5310 The session specified in the network control block (NCB) was closed. The NCB is the data.
5311 The network control block (NCB) command was canceled. The NCB is the data.
5312 The message segment specified in the network control block (NCB) is illogical. The NCB is the
data.
5313 The name already exists in the local adapter name table. The network control block (NCB)
request was refused. The NCB is the data.
5314 The network adapter name table is full. The network control block (NCB) request was refused.
The NCB is the data.
5315 The network name has active sessions and is now de-registered. The network control block
(NCB) command completed. The NCB is the data.
5316 A previously issued Receive Lookahead command is active for this session. The network
control block (NCB) command was rejected. The NCB is the data.
5317 The local session table is full. The network control block (NCB) request was refused. The NCB is
the data.
5318 A network control block (NCB) session open was rejected. No LISTEN is outstanding on the
remote computer. The NCB is the data.
5319 The name number specified in the network control block (NCB) is illegal. The NCB is the data.
5320 The call name specified in the network control block (NCB) cannot be found or did not answer.
5321 The name specified in the network control block (NCB) was not found. Cannot put '*' or 00h in
the NCB name. The NCB is the data.
5322 The name specified in the network control block (NCB) is in use on a remote adapter. The NCB
is the data.
5323 The name specified in the network control block (NCB) has been deleted. The NCB is the data.
5324 The session specified in the network control block (NCB) ended abnormally. The NCB is the
data.
5325 The network protocol has detected two or more identical names on the network. The network
control block (NCB) is the data.
5326 An unexpected protocol packet was received. There may be an incompatible remote device.
The network control block (NCB) is the data.
5333 The NetBIOS interface is busy. The network control block (NCB) request was refused. The NCB
is the data.
5334 There are too many network control block (NCB) commands outstanding. The NCB request was
refused. The NCB is the data.
5335 The adapter number specified in the network control block (NCB) is illegal. The NCB is the data.
5336 The network control block (NCB) command completed while a cancel was occurring. The NCB is
the data.
5337 The name specified in the network control block (NCB) is reserved. The NCB is the data.
5338 The network control block (NCB) command is not valid to cancel. The NCB is the data.
5351 There are multiple network control block (NCB) requests for the same session. The NCB
request was refused. The NCB is the data.
5352 There has been a network adapter error. The only NetBIOS command that may be issued is an
NCB RESET. The network control block (NCB) is the data.
5354 The maximum number of applications was exceeded. The network control block (NCB) request

was refused. The NCB is the data.
5356 The requested resources are not available. The network control block (NCB) request was
5364 A system error has occurred. The network control block (NCB) request was refused. The NCB is
the data.
5365 A ROM checksum failure has occurred. The network control block (NCB) request was refused.
5366 A RAM test failure has occurred. The network control block (NCB) request was refused. The
NCB is the data.
5367 A digital loopback failure has occurred. The network control block (NCB) request was refused.
5368 An analog loopback failure has occurred. The network control block (NCB) request was refused.
5369 An interface failure has occurred. The network control block (NCB) request was refused. The
NCB is the data.
5370 An unrecognized network control block (NCB) return code was received. The NCB is the data.
5380 A network adapter malfunction has occurred. The network control block (NCB) request was
5381 The network control block (NCB) command is still pending. The NCB is the data.
5509 Windows 2000 could not be started as configured. A previous working configuration was used
instead.
5600 Could not share the User or Script path.
5601 The password for this computer is not found in the local security database.
5602 An internal error occurred while accessing the computer's local or network security database.
5705 The change log cache maintained by the Netlogon service for database changes is corrupted.
The Netlogon service is resetting the change log.
5728 Could not load any transport.
5739 This domain has more global groups than can be replicated to a LanMan BDC. Either delete
some of your global groups or remove the LanMan BDCs from the domain.
5742 Service failed to retrieve messages needed to boot remote boot clients.
5743 Service experienced a severe error and can no longer provide remote boot for 3Com 3Start
remote boot clients.
5744 Service experienced a severe system error and will shut itself down.
5760 Service experienced error evaluating RPL configurations.
5761 Service experienced error creating RPL profiles for all configurations.
5762 Service experienced error accessing registry.
5763 Service experienced error replacing possibly outdated RPLDISK.SYS.
5764 Service experienced error adding security accounts or setting file permissions. These accounts
are the RPLUSER local group and the user accounts for the individual RPL workstations.
5765 Service failed to back up its database.
5766 Service failed to initialize from its database. The database may be missing or corrupted.
Service will attempt restoring the database from the backup.
5767 Service failed to restore its database from the backup. Service will not start.
5768 Service successfully restored its database from the backup.
5769 Service failed to initialize from its restored database. Service will not start.
5771 The Remoteboot database was in NT 3.5 / NT 3.51 format and NT is attempting to convert it to
NT 4.0 format. The JETCONV converter will write to the Application event log when it is finished.
5781 Dynamic registration or deregistration of one or more DNS records failed because no DNS
servers are available.
5890 An operation was attempted that is incompatible with the current membership state of the
node.
5891 The quorum resource does not contain the quorum log.
5892 The membership engine requested shutdown of the cluster service on this node.
5893 The join operation failed because the cluster instance ID of the joining node does not match
the cluster instance ID of the sponsor node.
5894 A matching network for the specified IP address could not be found. Please also specify a
subnet mask and a cluster network.
5895 The actual data type of the property did not match the expected data type of the property.
5896 The cluster node was evicted from the cluster successfully, but the node was not cleaned up.
Extended status information explaining why the node was not cleaned up is available.
5897 Two or more parameter values specified for a resource's properties are in conflict.
5898 This computer cannot be made a member of a cluster.
5899 This computer cannot be made a member of a cluster because it does not have the correct
version of Windows installed.
5900 A cluster cannot be created with the specified cluster name because that cluster name is
already in use. Specify a different name for the cluster.
6000 The specified file could not be encrypted.
6001 The specified file could not be decrypted.

6002 The specified file is encrypted and the user does not have the ability to decrypt it.
6003 There is no valid encryption recovery policy configured for this system.
6004 The required encryption driver is not loaded for this system.
6005 The file was encrypted with a different encryption driver than is currently loaded.
6006 There are no EFS keys defined for the user.
6007 The specified file is not encrypted.
6008 The specified file is not in the defined EFS export format.
6009 The specified file is read only.
6010 The directory has been disabled for encryption.
6011 The server is not trusted for remote encryption operation.
6012 Recovery policy configured for this system contains invalid recovery certificate.
6013 The encryption algorithm used on the source file needs a bigger key buffer than the one on the
destination file.
6014 The disk partition does not support file encryption.
6015 This machine is disabled for file encryption.
6016 A newer system is required to decrypt this encrypted file.
6118 The list of servers for this workgroup is not currently available
6200 The Task Scheduler service must be configured to run in the System account to function
properly. Individual tasks may be configured to run in other accounts.
7001 The specified session name is invalid.
7002 The specified protocol driver is invalid.
7003 The specified protocol driver was not found in the system path.
7004 The specified terminal connection driver was not found in the system path.
7005 A registry key for event logging could not be created for this session.
7006 A service with the same name already exists on the system.
7007 A close operation is pending on the session.
7008 There are no free output buffers available.
7009 The MODEM.INF file was not found.
7010 The modem name was not found in MODEM.INF.
7011 The modem did not accept the command sent to it. Verify that the configured modem name
matches the attached modem.
7012 The modem did not respond to the command sent to it. Verify that the modem is properly
cabled and powered on.
7013 Carrier detect has failed or carrier has been dropped due to disconnect.
7014 Dial tone not detected within the required time. Verify that the phone cable is properly
attached and functional.
7015 Busy signal detected at remote site on callback.
7016 Voice detected at remote site on callback.
7017 Transport driver error
7022 The specified session cannot be found.
7023 The specified session name is already in use.
7024 The requested operation cannot be completed because the terminal connection is currently
busy processing a connect, disconnect, reset, or delete operation.
7025 An attempt has been made to connect to a session whose video mode is not supported by the
current client.
7035 The application attempted to enable DOS graphics mode. DOS graphics mode is not supported.
7037 Your interactive logon privilege has been disabled. Please contact your administrator.
7038 The requested operation can be performed only on the system console. This is most often the
result of a driver or system DLL requiring direct console access.
7040 The client failed to respond to the server connect message.
7041 Disconnecting the console session is not supported.
7042 Reconnecting a disconnected session to the console is not supported.
7044 The request to control another session remotely was denied.
7045 The requested session access is denied.
7049 The specified terminal connection driver is invalid.
7050 The requested session cannot be controlled remotely. This may be because the session is
disconnected or does not currently have a user logged on.
7051 The requested session is not configured to allow remote control.
7052 Your request to connect to this Terminal Server has been rejected. Your Terminal Server client
license number is currently being used by another user. Please call your system administrator to
obtain a unique license number.
7053 Your request to connect to this Terminal Server has been rejected. Your Terminal Server client
license number has not been entered for this copy of the Terminal Server client. Please contact your
system administrator.
7054 The system has reached its licensed logon limit. Please try again later.
7055 The client you are using is not licensed to use this system. Your logon request is denied.
7056 The system license has expired. Your logon request is denied.
7057 Remote control could not be terminated because the specified session is not currently being

remotely controlled.
7058 The remote control of the console was terminated because the display mode was changed.
Changing the display mode in a remote control session is not supported.
8001 The file replication service API was called incorrectly.
8002 The file replication service cannot be started.
8003 The file replication service cannot be stopped.
8004 The file replication service API terminated the request. The event log may have more
information.
8005 The file replication service terminated the request. The event log may have more information.
8006 The file replication service cannot be contacted. The event log may have more information.
8007 The file replication service cannot satisfy the request because the user has insufficient
privileges. The event log may have more information.
8008 The file replication service cannot satisfy the request because authenticated RPC is not
available. The event log may have more information.
8009 The file replication service cannot satisfy the request because the user has insufficient
privileges on the domain controller. The event log may have more information.
8010 The file replication service cannot satisfy the request because authenticated RPC is not
available on the domain controller. The event log may have more information.
8011 The file replication service cannot communicate with the file replication service on the domain
controller. The event log may have more information.
8012 The file replication service on the domain controller cannot communicate with the file
replication service on this computer. The event log may have more information.
8013 The file replication service cannot populate the system volume because of an internal error.
The event log may have more information.
8014 The file replication service cannot populate the system volume because of an internal timeout.
The event log may have more information.
8015 The file replication service cannot process the request. The system volume is busy with a
previous request.
8016 The file replication service cannot stop replicating the system volume because of an internal
error. The event log may have more information.
8017 The file replication service detected an invalid parameter.
8200 An error occurred while installing the directory service. For more information, see the event
log.
8201 The directory service evaluated group memberships locally.
8202 The specified directory service attribute or value does not exist.
8203 The attribute syntax specified to the directory service is invalid.
8204 The attribute type specified to the directory service is not defined.
8205 The specified directory service attribute or value already exists.
8206 The directory service is busy.
8207 The directory service is unavailable.
8208 The directory service was unable to allocate a relative identifier.
8209 The directory service has exhausted the pool of relative identifiers.
8210 The requested operation could not be performed because the directory service is not the
master for that type of operation.
8211 The directory service was unable to initialize the subsystem that allocates relative identifiers.
8212 The requested operation did not satisfy one or more constraints associated with the class of
the object.
8213 The directory service can perform the requested operation only on a leaf object.
8214 The directory service cannot perform the requested operation on the RDN attribute of an
object.
8215 The directory service detected an attempt to modify the object class of an object.
8216 The requested cross-domain move operation could not be performed.
8217 Unable to contact the global catalog server.
8218 The policy object is shared and can only be modified at the root.
8219 The policy object does not exist.
8220 The requested policy information is only in the directory service.
8221 A domain controller promotion is currently active.
8222 A domain controller promotion is not currently active
8224 An operations error occurred.
8225 A protocol error occurred.
8226 The time limit for this request was exceeded.
8227 The size limit for this request was exceeded.
8228 The administrative limit for this request was exceeded.
8229 The compare response was false.
8230 The compare response was true.
8231 The requested authentication method is not supported by the server.
8232 A more secure authentication method is required for this server.
8233 Inappropriate authentication.

8234 The authentication mechanism is unknown.
8235 A referral was returned from the server.
8236 The server does not support the requested critical extension.
8237 This request requires a secure connection.
8238 Inappropriate matching.
8239 A constraint violation occurred.
8240 There is no such object on the server.
8241 There is an alias problem.
8242 An invalid dn syntax has been specified.
8243 The object is a leaf object.
8244 There is an alias dereferencing problem.
8245 The server is unwilling to process the request.
8246 A loop has been detected.
8247 There is a naming violation.
8248 The result set is too large.
8249 The operation affects multiple DSAs
8250 The server is not operational.
8251 A local error has occurred.
8252 An encoding error has occurred.
8253 A decoding error has occurred.
8254 The search filter cannot be recognized.
8255 One or more parameters are illegal.
8256 The specified method is not supported.
8257 No results were returned.
8258 The specified control is not supported by the server.
8259 A referral loop was detected by the client.
8260 The preset referral limit was exceeded.
8261 The search requires a SORT control.
8262 The search results exceed the offset range specified.
8301 The root object must be the head of a naming context. The root object cannot have an
instantiated parent.
8302 The add replica operation cannot be performed. The naming context must be writable in order
to create the replica.
8303 A reference to an attribute that is not defined in the schema occurred.
8304 The maximum size of an object has been exceeded.
8305 An attempt was made to add an object to the directory with a name that is already in use.
8306 An attempt was made to add an object of a class that does not have an RDN defined in the
schema.
8307 An attempt was made to add an object using an RDN that is not the RDN defined in the
schema.
8308 None of the requested attributes were found on the objects.
8309 The user buffer is too small.
8310 The attribute specified in the operation is not present on the object.
8311 Illegal modify operation. Some aspect of the modification is not permitted.
8312 The specified object is too large.
8313 The specified instance type is not valid.
8314 The operation must be performed at a master DSA.
8315 The object class attribute must be specified.
8316 A required attribute is missing.
8317 An attempt was made to modify an object to include an attribute that is not legal for its class.
8318 The specified attribute is already present on the object.
8320 The specified attribute is not present, or has no values.
8321 Mutliple values were specified for an attribute that can have only one value.
8322 A value for the attribute was not in the acceptable range of values.
8323 The specified value already exists.
8324 The attribute cannot be removed because it is not present on the object.
8325 The attribute value cannot be removed because it is not present on the object.
8326 The specified root object cannot be a subref.
8327 Chaining is not permitted.
8328 Chained evaluation is not permitted.
8329 The operation could not be performed because the object's parent is either uninstantiated or
deleted.
8330 Having a parent that is an alias is not permitted. Aliases are leaf objects.
8331 The object and parent must be of the same type, either both masters or both replicas.
8332 The operation cannot be performed because child objects exist. This operation can only be
performed on a leaf object.
8333 Directory object not found.
8334 The aliased object is missing.

8335 The object name has bad syntax.
8336 It is not permitted for an alias to refer to another alias.
8337 The alias cannot be dereferenced.
8338 The operation is out of scope.
8339 The operation cannot continue because the object is in the process of being removed.
8340 The DSA object cannot be deleted.
8341 A directory service error has occurred.
8342 The operation can only be performed on an internal master DSA object.
8343 The object must be of class DSA.
8344 Insufficient access rights to perform the operation.
8345 The object cannot be added because the parent is not on the list of possible superiors.
8346 Access to the attribute is not permitted because the attribute is owned by the Security
Accounts Manager (SAM).
8347 The name has too many parts.
8348 The name is too long.
8349 The name value is too long.
8350 The directory service encountered an error parsing a name.
8351 The directory service cannot get the attribute type for a name.
8352 The name does not identify an object; the name identifies a phantom.
8353 The security descriptor is too short.
8354 The security descriptor is invalid.
8355 Failed to create name for deleted object.
8356 The parent of a new subref must exist.
8357 The object must be a naming context.
8358 It is not permitted to add an attribute which is owned by the system.
8359 The class of the object must be structural; you cannot instantiate an abstract class.
8360 The schema object could not be found.
8361 A local object with this GUID (dead or alive) already exists.
8362 The operation cannot be performed on a back link.
8363 The cross reference for the specified naming context could not be found.
8364 The operation could not be performed because the directory service is shutting down.
8365 The directory service request is invalid.
8366 The role owner attribute could not be read.
8367 The requested FSMO operation failed. The current FSMO holder could not be contacted.
8368 Modification of a DN across a naming context is not permitted.
8369 The attribute cannot be modified because it is owned by the system.
8370 Only the replicator can perform this function.
8371 The specified class is not defined.
8372 The specified class is not a subclass.
8373 The name reference is invalid.
8374 A cross reference already exists.
8375 It is not permitted to delete a master cross reference.
8376 Subtree notifications are only supported on NC heads.
8377 Notification filter is too complex.
8378 Schema update failed: duplicate RDN.
8379 Schema update failed: duplicate OID.
8380 Schema update failed: duplicate MAPI identifier.
8381 Schema update failed: duplicate schema-id GUID.
8382 Schema update failed: duplicate LDAP display name.
8383 Schema update failed: range-lower less than range upper.
8384 Schema update failed: syntax mismatch.
8385 Schema deletion failed: attribute is used in must-contain.
8386 Schema deletion failed: attribute is used in may-contain.
8387 Schema update failed: attribute in may-contain does not exist.
8388 Schema update failed: attribute in must-contain does not exist.
8389 Schema update failed: class in aux-class list does not exist or is not an auxiliary class.
8390 Schema update failed: class in poss-superiors does not exist.
8391 Schema update failed: class in subclassof list does not exist or does not satisfy hierarchy rules.
8392 Schema update failed: Rdn-Att-Id has wrong syntax.
8393 Schema deletion failed: class is used as auxiliary class.
8394 Schema deletion failed: class is used as sub class.
8395 Schema deletion failed: class is used as poss superior.
8396 Schema update failed in recalculating validation cache.
8397 The tree deletion is not finished. The request must be made again to continue deleting the
tree.
8398 The requested delete operation could not be performed.
8399 Cannot read the governs class identifier for the schema record.
8400 The attribute schema has bad syntax.

8401 The attribute could not be cached.
8402 The class could not be cached.
8403 The attribute could not be removed from the cache.
8404 The class could not be removed from the cache.
8405 The distinguished name attribute could not be read.
8406 A required subref is missing.
8407 The instance type attribute could not be retrieved.
8408 An internal error has occurred.
8409 A database error has occurred.
8410 The attribute GOVERNSID is missing.
8411 An expected attribute is missing.
8412 The specified naming context is missing a cross reference.
8413 A security checking error has occurred.
8414 The schema is not loaded.
8415 Schema allocation failed. Please check if the machine is running low on memory.
8416 Failed to obtain the required syntax for the attribute schema.
8417 The global catalog verification failed. The global catalog is not available or does not support
the operation. Some part of the directory is currently not available.
8418 The replication operation failed because of a schema mismatch between the servers involved.
8419 The DSA object could not be found.
8420 The naming context could not be found.
8421 The naming context could not be found in the cache.
8422 The child object could not be retrieved.
8423 The modification was not permitted for security reasons.
8424 The operation cannot replace the hidden record.
8425 The hierarchy file is invalid.
8426 The attempt to build the hierarchy table failed.
8427 The directory configuration parameter is missing from the registry.
8428 The attempt to count the address book indices failed.
8429 The allocation of the hierarchy table failed.
8430 The directory service encountered an internal failure.
8431 The directory service encountered an unknown failure.
8432 A root object requires a class of 'top'.
8433 This directory server is shutting down, and cannot take ownership of new floating single-
master operation roles.
8434 The directory service is missing mandatory configuration information, and is unable to
determine the ownership of floating single-master operation roles.
8435 The directory service was unable to transfer ownership of one or more floating single-master
operation roles to other servers.
8436 The replication operation failed.
8437 An invalid parameter was specified for this replication operation.
8438 The directory service is too busy to complete the replication operation at this time.
8439 The distinguished name specified for this replication operation is invalid.
8440 The naming context specified for this replication operation is invalid.
8441 The distinguished name specified for this replication operation already exists.
8442 The replication system encountered an internal error.
8443 The replication operation encountered a database inconsistency.
8444 The server specified for this replication operation could not be contacted.
8445 The replication operation encountered an object with an invalid instance type.
8446 The replication operation failed to allocate memory.
8447 The replication operation encountered an error with the mail system.
8448 The replication reference information for the target server already exists.
8449 The replication reference information for the target server does not exist.
8450 The naming context cannot be removed because it is replicated to another server.
8451 The replication operation encountered a database error.
8452 The naming context is in the process of being removed or is not replicated from the specified
server.
8453 Replication access was denied.
8454 The requested operation is not supported by this version of the directory service.
8455 The replication remote procedure call was cancelled.
8456 The source server is currently rejecting replication requests.
8457 The destination server is currently rejecting replication requests.
8458 The replication operation failed due to a collision of object names.
8459 The replication source has been reinstalled.
8460 The replication operation failed because a required parent object is missing.
8461 The replication operation was preempted.
8462 The replication synchronization attempt was abandoned because of a lack of updates.
8463 The replication operation was terminated because the system is shutting down.

8464 The replication synchronization attempt failed as the destination partial attribute set is not a
subset of source partial attribute set.
8465 The replication synchronization attempt failed because a master replica attempted to sync
from a partial replica.
8466 The server specified for this replication operation was contacted, but that server was unable to
contact an additional server needed to complete the operation.
8467 The version of the Active Directory schema of the source forest is not compatible with the
version of Active Directory on this computer. You must upgrade the operating system on a domain
controller in the source forest before this computer can be added a
8468 Schema update failed: An attribute with the same link identifier already exists.
8469 Name translation: Generic processing error.
8470 Name translation: Could not find the name or insufficient right to see name.
8471 Name translation: Input name mapped to more than one output name.
8472 Name translation: Input name found, but not the associated output format.
8473 Name translation: Unable to resolve completely, only the domain was found.
8474 Name translation: Unable to perform purely syntactical mapping at the client without going out
to the wire.
8475 Modification of a constructed att is not allowed.
8476 The OM-Object-Class specified is incorrect for an attribute with the specified syntax.
8477 The replication request has been posted; waiting for reply.
8478 The requested operation requires a directory service, and none was available.
8479 The LDAP display name of the class or attribute contains non-ASCII characters.
8480 The requested search operation is only supported for base searches.
8481 The search failed to retrieve attributes from the database.
8482 The schema update operation tried to add a backward link attribute that has no corresponding
forward link.
8483 Source and destination of a cross-domain move do not agree on the object's epoch number.
Either source or destination does not have the latest version of the object.
8484 Source and destination of a cross-domain move do not agree on the object's current name.
Either source or destination does not have the latest version of the object.
8485 Source and destination for the cross-domain move operation are identical. Caller should use
local move operation instead of cross-domain move operation.
8486 Source and destination for a cross-domain move are not in agreement on the naming contexts
in the forest. Either source or destination does not have the latest version of the Partitions container.
8487 Destination of a cross-domain move is not authoritative for the destination naming context.
8488 Source and destination of a cross-domain move do not agree on the identity of the source
object. Either source or destination does not have the latest version of the source object.
8489 Object being moved across-domains is already known to be deleted by the destination server.
The source server does not have the latest version of the source object.
8490 Another operation which requires exclusive access to the PDC FSMO is already in progress.
8491 A cross-domain move operation failed such that two versions of the moved object exist - one
each in the source and destination domains. The destination object needs to be removed to restore
the system to a consistent state.
8492 This object may not be moved across domain boundaries either because cross-domain moves
for this class are disallowed, or the object has some special characteristics, eg: trust account or
restricted RID, which prevent its move.
8493 Can't move objects with memberships across domain boundaries as once moved, this would
violate the membership conditions of the account group. Remove the object from any account group
memberships and retry.
8494 A naming context head must be the immediate child of another naming context head, not of
an interior node.
8495 The directory cannot validate the proposed naming context name because it does not hold a
replica of the naming context above the proposed naming context. Please ensure that the domain
naming master role is held by a server that is configured as a global
8496 Destination domain must be in native mode.
8497 The operation can not be performed because the server does not have an infrastructure
container in the domain of interest.
8498 Cross-domain move of non-empty account groups is not allowed.
8499 Cross-domain move of non-empty resource groups is not allowed.
8500 The search flags for the attribute are invalid. The ANR bit is valid only on attributes of Unicode
or Teletex strings.
8501 Tree deletions starting at an object which has an NC head as a descendant are not allowed.
8502 The directory service failed to lock a tree in preparation for a tree deletion because the tree
was in use.
8503 The directory service failed to identify the list of objects to delete while attempting a tree
deletion.
8505 Only an administrator can modify the membership list of an administrative group.
8506 Cannot change the primary group ID of a domain controller account.

8507 An attempt is made to modify the base schema.
8508 Adding a new mandatory attribute to an existing class, deleting a mandatory attribute from an
existing class, or adding an optional attribute to the special class Top that is not a backlink attribute
(directly or through inheritance, for example, by addin
8509 Schema update is not allowed on this DC because the DC is not the schema FSMO Role Owner.
8510 An object of this class cannot be created under the schema container. You can only create
attribute-schema and class-schema objects under the schema container.
8511 The replica/child install failed to get the objectVersion attribute on the schema container on
the source DC. Either the attribute is missing on the schema container or the credentials supplied do
not have permission to read it.
8512 The replica/child install failed to read the objectVersion attribute in the SCHEMA section of the
file schema.ini in the system32 directory.
8513 The specified group type is invalid.
8514 You cannot nest global groups in a mixed domain if the group is security-enabled.
8515 You cannot nest local groups in a mixed domain if the group is security-enabled.
8516 A global group cannot have a local group as a member.
8517 A global group cannot have a universal group as a member.
8518 A universal group cannot have a local group as a member.
8519 A global group cannot have a cross-domain member.
8520 A local group cannot have another cross domain local group as a member.
8521 A group with primary members cannot change to a security-disabled group.
8522 The schema cache load failed to convert the string default SD on a class-schema object.
8523 Only DSAs configured to be Global Catalog servers should be allowed to hold the Domain
Naming Master FSMO role. (Applies only to Windows 2000 servers)
8524 The DSA operation is unable to proceed because of a DNS lookup failure.
8525 While processing a change to the DNS Host Name for an object, the Service Principal Name
values could not be kept in sync.
8526 The Security Descriptor attribute could not be read.
8527 The object requested was not found, but an object with that key was found.
8528 The syntax of the linked attribute being added is incorrect. Forward links can only have syntax
2.5.5.1, 2.5.5.7, and 2.5.5.14, and backlinks can only have syntax 2.5.5.1
8529 Security Account Manager needs to get the boot password.
8530 Security Account Manager needs to get the boot key from floppy disk.
8531 Directory Service cannot start.
8532 Directory Services could not start.
8533 The connection between client and server requires packet privacy or better.
8534 The source domain may not be in the same forest as destination.
8535 The destination domain must be in the forest.
8536 The operation requires that destination domain auditing be enabled.
8537 The operation couldn't locate a DC for the source domain.
8538 The source object must be a group or user.
8539 The source object's SID already exists in destination forest.
8540 The source and destination object must be of the same type.
8542 Schema information could not be included in the replication request.
8543 The replication operation could not be completed due to a schema incompatibility.
8544 The replication operation could not be completed due to a previous schema incompatibility.
8545 The replication update could not be applied because either the source or the destination has
not yet received information regarding a recent cross-domain move operation.
8546 The requested domain could not be deleted because there exist domain controllers that still
host this domain.
8547 The requested operation can be performed only on a global catalog server.
8548 A local group can only be a member of other local groups in the same domain.
8549 Foreign security principals cannot be members of universal groups.
8550 The attribute is not allowed to be replicated to the GC because of security reasons.
8551 The checkpoint with the PDC could not be taken because there too many modifications being
processed currently.
8552 The operation requires that source domain auditing be enabled.
8553 Security principal objects can only be created inside domain naming contexts.
8554 A Service Principal Name (SPN) could not be constructed because the provided hostname is
not in the necessary format.
8555 A Filter was passed that uses constructed attributes.
8556 The unicodePwd attribute value must be enclosed in double quotes.
8557 Your computer could not be joined to the domain. You have exceeded the maximum number of
computer accounts you are allowed to create in this domain. Contact your system administrator to
have this limit reset or increased.
8558 For security reasons, the operation must be run on the destination DC.
8559 For security reasons, the source DC must be NT4SP4 or greater.
8560 Critical Directory Service System objects cannot be deleted during tree delete operations. The

tree delete may have been partially performed.
8563 This version of Windows is too old to support the current directory forest behavior. You must
upgrade the operating system on this server before it can become a domain controller in this forest.
8564 This version of Windows is too old to support the current domain behavior. You must upgrade
the operating system on this server before it can become a domain controller in this domain.
8565 This version of Windows no longer supports the behavior version in use in this directory forest.
You must advance the forest behavior version before this server can become a domain controller in
the forest.
8566 This version of Windows no longer supports the behavior version in use in this domain. You
must advance the domain behavior version before this server can become a domain controller in the
domain.
8567 The version of Windows is incompatible with the behavior version of the domain or forest.
8568 The behavior version cannot be increased to the requested value because Domain Controllers
still exist with versions lower than the requested value.
8569 The behavior version value cannot be increased while the domain is still in mixed domain
mode. You must first change the domain to native mode before increasing the behavior version.
8570 The sort order requested is not supported.
8571 Found an object with a non unique name.
8572 The machine account was created pre-NT4. The account needs to be recreated.
8573 The database is out of version store.
8574 Unable to continue operation because multiple conflicting controls were used.
8575 Unable to find a valid security descriptor reference domain for this partition.
8576 Schema update failed: The link identifier is reserved.
8577 Schema update failed: There are no link identifiers available.
8578 A account group can not have a universal group as a member.
8579 Rename or move operations on naming context heads or read-only objects are not allowed.
8580 Move operations on objects in the schema naming context are not allowed.
8581 A system flag has been set on the object and does not allow the object to be moved or
renamed.
8582 This object is not allowed to change its grandparent container. Moves are not forbidden on this
object, but are restricted to sibling containers.
8583 Unable to resolve completely, a referral to another forest is generated.
8584 The requested action is not supported on standard server.
8585 Could not access a partition of the Active Directory located on a remote server. Make sure at
least one server is running for the partition in question.
8586 The directory cannot validate the proposed naming context (or partition) name because it does
not hold a replica nor can it contact a replica of the naming context above the proposed naming
context. Please ensure that the parent naming context is properl
8587 The thread limit for this request was exceeded.
8588 The Global catalog server is not in the closest site.
8589 The DS cannot derive a service principal name (SPN) with which to mutually authenticate the
target server because the corresponding server object in the local DS database has no
serverReference attribute.
8590 The Directory Service failed to enter single user mode.
8591 The Directory Service cannot parse the script because of a syntax error.
8592 The Directory Service cannot process the script because of an error.
8593 The directory service cannot perform the requested operation because the servers involved
are of different replication epochs (which is usually related to a domain rename that is in progress).
8594 The directory service binding must be renegotiated due to a change in the server extensions
information.
8595 Operation not allowed on a disabled cross ref.
8596 Schema update failed: No values for msDS-IntId are available.
8597 Schema update failed: Duplicate msDS-INtId. Retry the operation.
8598 Schema deletion failed: attribute is used in rDNAttID.
8599 The directory service failed to authorize the request.
8600 The Directory Service cannot process the script because it is invalid.
8601 The remote create cross reference operation failed on the Domain Naming Master FSMO. The
operation's error is in the extended data.
9001 DNS server unable to interpret format.
9002 DNS server failure.
9003 DNS name does not exist.
9004 DNS request not supported by name server.
9005 DNS operation refused.
9006 DNS name that ought not exist, does exist.
9007 DNS RR set that ought not exist, does exist.
9008 DNS RR set that ought to exist, does not exist.
9009 DNS server not authoritative for zone.
9010 DNS name in update or prereq is not in zone.

9016 DNS signature failed to verify.
9017 DNS bad key.
9018 DNS signature validity expired.
9501 No records found for given DNS query.
9502 Bad DNS packet.
9503 No DNS packet.
9504 DNS error, check rcode.
9505 Unsecured DNS packet.
9551 Invalid DNS type.
9552 Invalid IP address.
9553 Invalid property.
9554 Try DNS operation again later.
9555 Record for given name and type is not unique.
9556 DNS name does not comply with RFC specifications.
9557 DNS name is a fully-qualified DNS name.
9558 DNS name is dotted (multi-label).
9559 DNS name is a single-part name.
9560 DNS name contains an invalid character.
9561 DNS name is entirely numeric.
9562 The operation requested is not permitted on a DNS root server.
9601 DNS zone does not exist.
9602 DNS zone information not available.
9603 Invalid operation for DNS zone.
9604 Invalid DNS zone configuration.
9605 DNS zone has no start of authority (SOA) record.
9606 DNS zone has no Name Server (NS) record.
9607 DNS zone is locked.
9608 DNS zone creation failed.
9609 DNS zone already exists.
9610 DNS automatic zone already exists.
9611 Invalid DNS zone type.
9612 Secondary DNS zone requires master IP address.
9613 DNS zone not secondary.
9614 Need secondary IP address.
9615 WINS initialization failed.
9616 Need WINS servers.
9617 NBTSTAT initialization call failed.
9618 Invalid delete of start of authority (SOA)
9619 A conditional forwarding zone already exists for that name.
9620 This zone must be configured with one or more master DNS server IP addresses.
9621 The operation cannot be performed because this zone is shutdown.
9651 Primary DNS zone requires datafile.
9652 Invalid datafile name for DNS zone.
9653 Failed to open datafile for DNS zone.
9654 Failed to write datafile for DNS zone.
9655 Failure while reading datafile for DNS zone.
9701 DNS record does not exist.
9702 DNS record format error.
9703 Node creation failure in DNS.
9704 Unknown DNS record type.
9705 DNS record timed out.
9706 Name not in DNS zone.
9707 CNAME loop detected.
9708 Node is a CNAME DNS record.
9709 A CNAME record already exists for given name.
9710 Record only at DNS zone root.
9711 DNS record already exists.
9712 Secondary DNS zone data error.
9713 Could not create DNS cache data.
9714 DNS name does not exist.
9715 Could not create pointer (PTR) record.
9716 DNS domain was undeleted.
9717 The directory service is unavailable.
9718 DNS zone already exists in the directory service.
9719 DNS server not creating or reading the boot file for the directory service integrated DNS zone.
9751 DNS AXFR (zone transfer) complete.
9752 DNS zone transfer failed.
9753 Added local WINS server.

9801 Secure update call needs to continue update request.
9851 TCP/IP network protocol not installed.
9852 No DNS servers configured for local system.
9901 The specified directory partition does not exist.
9902 The specified directory partition already exists.
9903 The DS is not enlisted in the specified directory partition.
9904 The DS is already enlisted in the specified directory partition.
10004 A blocking operation was interrupted by a call to WSACancelBlockingCall.
10009 The file handle supplied is not valid.
10013 An attempt was made to access a socket in a way forbidden by its access permissions.
10014 The system detected an invalid pointer address in attempting to use a pointer argument in a
call.
10022 An invalid argument was supplied.
10024 Too many open sockets.
10035 A non-blocking socket operation could not be completed immediately.
10036 A blocking operation is currently executing.
10037 An operation was attempted on a non-blocking socket that already had an operation in
progress.
10038 An operation was attempted on something that is not a socket.
10039 A required address was omitted from an operation on a socket.
10040 A message sent on a datagram socket was larger than the internal message buffer or some
other network limit, or the buffer used to receive a datagram into was smaller than the datagram
itself.
10041 A protocol was specified in the socket function call that does not support the semantics of the
socket type requested.
10042 An unknown, invalid, or unsupported option or level was specified in a getsockopt or
setsockopt call.
10043 The requested protocol has not been configured into the system, or no implementation for it
exists.
10044 The support for the specified socket type does not exist in this address family.
10045 The attempted operation is not supported for the type of object referenced.
10046 The protocol family has not been configured into the system or no implementation for it
exists.
10047 An address incompatible with the requested protocol was used.
10048 Only one usage of each socket address (protocol/network address/port) is normally permitted.
10049 The requested address is not valid in its context.
10050 A socket operation encountered a dead network.
10051 A socket operation was attempted to an unreachable network.
10052 The connection has been broken due to keep-alive activity detecting a failure while the
operation was in progress.
10053 An established connection was aborted by the software in your host machine.
10054 An existing connection was forcibly closed by the remote host.
10055 An operation on a socket could not be performed because the system lacked sufficient buffer
space or because a queue was full.
10056 A connect request was made on an already connected socket.
10057 A request to send or receive data was disallowed because the socket is not connected and
(when sending on a datagram socket using a sendto call) no address was supplied.
10058 A request to send or receive data was disallowed because the socket had already been shut
down in that direction with a previous shutdown call.
10059 Too many references to some kernel object.
10060 A connection attempt failed because the connected party did not properly respond after a
period of time, or established connection failed because connected host has failed to respond.
10061 No connection could be made because the target machine actively refused it.
10062 Cannot translate name.
10063 Name component or name was too long.
10064 A socket operation failed because the destination host was down.
10065 A socket operation was attempted to an unreachable host.
10066 Cannot remove a directory that is not empty.
10067 A Windows Sockets implementation may have a limit on the number of applications that may
use it simultaneously.
10068 Ran out of quota.
10069 Ran out of disk quota.
10070 File handle reference is no longer available.
10071 Item is not available locally.
10091 WSAStartup cannot function at this time because the underlying system it uses to provide
network services is currently unavailable.
10092 The Windows Sockets version requested is not supported.
10093 Either the application has not called WSAStartup, or WSAStartup failed.

10101 Returned by WSARecv or WSARecvFrom to indicate the remote party has initiated a graceful
shutdown sequence.
10102 No more results can be returned by WSALookupServiceNext.
10103 A call to WSALookupServiceEnd was made while this call was still processing. The call has
been canceled.
10104 The procedure call table is invalid.
10105 The requested service provider is invalid.
10106 The requested service provider could not be loaded or initialized.
10107 A system call that should never fail has failed.
10108 No such service is known. The service cannot be found in the specified name space.
10109 The specified class was not found.
10110 No more results can be returned by WSALookupServiceNext.
10111 A call to WSALookupServiceEnd was made while this call was still processing. The call has
been canceled.
10112 A database query failed because it was actively refused.
The Program "Error Messages for Windows" written by Gregory Braun is where this info came from.
Home Page www.gregorybraun.com

Program Dowload page http://www.gregorybraun.com/MSWinErr.html
__________________
=
cheyenne1212
View Public Profile
Send a private message to cheyenne1212
Visit cheyenne1212's homepage!
Find More Posts by cheyenne1212

06-21-2003, 12:57 AM
#2
geepod vbmenu_register("postmenu_638350", true);

AntiOnline Member
Join Date: Jun 2002

Posts: 207
the real meanings of the error codes
thought i would include the real meanings of the error codes!
WindowError:001 Windows loaded. System in danger!

WindowError:002 Nothing wrong. YET!
WindowError:003 Dynamic link error. Error in all files!
WindowError:004 Random error. No real error!

WindowError:005 Windows tried to multitask. System confused!
WindowError:006 Disk error. Disk in drive!
WindowError:007 System price error. Too little money spent!
WindowError:008 Terrible error. God only knows what happened!
WindowError:009 Error code error. Error code error reported!
WindowError:00A Broken window. Be careful with the glass!
WindowError:00B Need more disk space. At least 150 mb!
WindowError:00C Memory error. Need more! Need more! Need more!
WindowError:00D Windows closed. Don't look out!
WindowError:00E Windows opened. Don't look in!
WindowError:00F Unexplained error. Tell us what happened!
WindowError:010 Reserved for future error..
WindowError:014 Non existing error. This is not happening!
WindowError:015 Unable to exit Windows. Try the door!
WindowError:016 Door closed. Try CTRL+ALT+DEL.
WindowError:017 Unfixable error. System destroyed!
WindowError:018 User fault! Not ours, not not not!!
WindowError:019 Windows deleted all files. We're really sorry!
WindowError:01A Word dosen't know the word "Chicago". Try Aug'95!
WindowError:01B You're using Windows For Workgroups. You are not a WorkGroup!
WindowError:01C Your using an old version of Win 3.11! Buy a newer!
WindowError:01D Timing error. Try again later!
WindowError:01E Error code failure! Remaining errors lost!
WindowError:01F You can't delete Windows. Windows is instaled!
Net Use Command
Net use
Connects a computer to or disconnects a computer from a shared resource, or displays information

about computer connections. The command also controls persistent net connections. Used without
parameters, net use retrieves a list of network connections.
Syntax
net use [{DeviceName | *}] [\\ComputerName\ShareName[\volume]] [{Password | *}]]

[/user:[DomainName\]UserName] [/user:[DottedDomainName\]UserName] [/user:
[UserName@DottedDomainName] [/savecred] [/smartcard] [{/delete | /persistent:{yes | no}}]
net use [DeviceName [/home[{Password | *}] [/delete:{yes | no}]]
net use [/persistent:{yes | no}]
Top of page
Parameters
DeviceName : Assigns a name to connect to the resource or specifies the device to be

disconnected. There are two kinds of device names: disk drives (that is, D: through Z:) and printers
(that is, LPT1: through LPT3:). Type an asterisk (*) instead of a specific device name to assign the
next available device name.
\\ComputerName\ShareName : Specifies the name of the server and the shared resource. If
ComputerName contains spaces, use quotation marks around the entire computer name from the
double backslash (\\) to the end of the computer name (for example,
"\\Computer Name\Share Name"). The computer name can be from 1 to 15 characters long.

\volume : Specifies a NetWare volume on the server. You must have Client Service for NetWare
installed and running to connect to NetWare servers.
Password : Specifies the password needed to access the shared resource. Type an asterisk (*) to
produce a prompt for the password. The password is not displayed when you type it at the password
prompt.
/user : Specifies a different user name with which the connection is made.
DomainName : Specifies another domain. If you omit DomainName, net use uses the current logged
on domain.
UserName : Specifies the user name with which to log on.
DottedDomainName : Specifies the fully-qualified domain name for the domain where the user
account exists.
/savecred : Stores the provided credentials for reuse.
/smartcard : Specifies the network connection is to use the credentials on a smart card. If multiple
smart cards are available, you are asked to specify the credential.
/delete : Cancels the specified network connection. If you specify the connection with an asterisk
(*), all network connections are canceled.
/persistent:{yes | no} : Controls the use of persistent network connections. The default is the setting
used last. Deviceless connections are not persistent. Yes saves all connections as they are made,
and restores them at next logon. No does not save the connection being made or subsequent
connections. Existing connections are restored at the next logon. Use /delete to remove persistent
connections.
/home : Connects a user to the home directory.
net help command : Displays help for the specified net command.
Top of page
Remarks
•
Connecting and disconnecting from a network resource
Use net use to connect to and disconnect from a network resource, and to view your current
connections to network resources. You cannot disconnect from a shared directory if you use it as
your current drive or an active process is using it.
•
Viewing connection information
To view information about a connection, you can do either of the following:
•

Type net use DeviceName to get information about a specific connection.
•
Type net use to get a list of all the computer's connections.
•
Using deviceless connections
Deviceless connections are not persistent.
•
Connecting to NetWare servers
After you install and run Client Service for NetWare, you can connect to a NetWare server on a
Novell network. Use the same syntax that you use to connect to a Windows Networking server,
except you must include the volume you to which you want to connect.
•
Using quotation marks
If the ServerName that you supply contains spaces, use quotation marks around the text (that is,
"Server Name"). If you omit quotation marks, an error message appears.
Top of page
Examples
To assign the disk-drive device name E: to the Letters shared directory on the \\Financial server,
type:
net use e: \\financial\letters
To assign (map) the disk-drive device name M: to the directory Mike within the Letters volume on
the \\Financial NetWare server, type:
net use m: \\financial\letters\mike
To connect the user identifier Dan as if the connection were made from the Accounts domain, type:
net use d:\\server\share /user:Accounts\Dan

To disconnect from the \\Financial\Public directory, type:
net use f: \\financial\public /delete
To connect to the resource memos shared on the \\Financial 2 server, type:
net use k: "\\financial 2" \memos
To restore the current connections at each logon, regardless of future changes, type:
net use /persistent:yes
Top of page
Formatting legend
Format
Meaning
Italic
Information that the user must supply
Bold
Elements that the user must type exactly as shown
Ellipsis (...)
Parameter that can be repeated several times in a command line
Between brackets ([])
Optional items
Between braces ({}); choices separated by pipe (|). Example: {even|odd}
Set of choices from which the user must choose only one

Courier font
Code or program output
Net services overview
Command-line reference A-Z
Top of page
Login Script For Newbies
TK - M/T Box Computers
http://groups.google.com/group/microsoft.public.windows.server.sbs/browse_thread/thread/3629c5ba
7f960ac7/1812f19f4c341334?hl=en
View profile
Because there have been various requests for login script help, I wanted to post
something that may help those who aren't so familiar with writing a batch file or login script.
DISCLAIMER: I'm not an instructor, I haven't written any books, I don't write code for a living, and
there may be other ways to accomplish the same thing as I have written. This is intended to help
others so please keep your opinions to yourself unless you have something constructive to add that
will benefit others. Additionally, this example script is intended for tutorial purposes and will need
'tweaked' to suit your environment. I take no responsibility for the use of this script in a production
environment. NOTES: There are tremendous amounts of information on the Internet and in books on
how to write scripts, what good practices are, and what variables can be used in a login script (batch
file). This should be enough to get the average person going in short order. If anything is unclear,
or if you have questions, please post them. Remember, you will need to modify this script for your
server name, network share names, drive letters you require, printer names, etc. Okay, with BS out
of the way, let's get going. First, you can find your default login script by clicking Start - Run, type
\\ServerName\netlogon, click OK. This will open a folder with a batch file called
SBS_LOGIN_SCRIPT.bat. Using Notepad, WordPad, or your favorite text editor open this file (note:
you should be able to right-click the file and select edit from the context menu). This file generally
includes only one line used for SBS client setups. Do not remove this line! It can be moved around
within the script, but leave it intact. If you don't already know it, this line will tell you the name of
your server. Now, following will be a clean version of my sample login script followed by a sample
with notes. My notes will start with the "Note:" to help you distinguish the difference. If this helps

even one person, it was worth the time. If you have further questions, please post them for all to
learn from. Enjoy! -TK M/T Box Computers @echo off rem
================================================== rem rem Title:
Login Script rem Author: Your Name rem Date: Self-explanatory rem Description: Network
Login Script rem rem
================================================== :SBS_SETUP rem
Default sbs2k3 client setup \\ServerName\Clients\Setup\setup.exe /s ServerName :MAPDRIVES rem
Connect network drives if exist f:\*.* net use f: /d net use f: \\ServerName\ShareName /persistent:no
if exist g:\*.* net use g: /d net use g: \\ServerName\applications /persistent:no if exist h:\*.* net use
h: /d net use h: \\ServerName\%username% /persistent:no :PRINTERS rem Connect network printers
net use lpt1: \\ServerName\Printer1ShareName /persistent:no net use lpt2:
\\ServerName\Printer2ShareName /persistent:no :END Note: The word 'REM' is a way to add a
remark to your batch file (login script). It is a good idea to use remarks throughout your login
script. This will help later when troubleshooting why the login script is written the way it is. You
should also document dates of changes and why. Note: The command 'ECHO' can be used to turn
display on and off. 'ECHO' followed by words will display those words on the screen. 'ECHO OFF'
will suppress all display until 'ECHO ON' is issued. Note: The @ sign in front of 'ECHO OFF' says to not
display this line also. @echo off rem
================================================== rem rem Title:
Login Script rem Author: Your Name rem Date: Self-explanatory rem Description: Network
Login Script rem rem
================================================== Note: The use of
the colon ':' followed immediately by a word designates the following lines as a section or routine
within your script. This allows you to move back and forth within the login script. This isn't
normally necessary, but I found it helpful to form good script writing habits early on. A batch file
will normally flow from top to bottom executing every line it comes to that is not a remark line, and
that is an actual command. You can skip sections by using the 'GOTO' command. Often times I will
check for the existence of the drive mappings after they should have completed. If they do not
exist I will send the user to an error message section letting them know something failed, with
instructions to reboot and/or contact their IT support. If you would like an example of this also, let
me know and I will post it. :SBS_SETUP rem Default sbs2k3 client setup Note: Leave this line intact
somewhere near the head of your script. As you see here, this is the first actual line that executes
in this script. \\ServerName\Clients\Setup\setup.exe /s ServerName :MAPDRIVES rem Connect
network drives Note: Tests for and deletes drive mapping if it exists (ensures drive letter isn't
erroneously mapped elsewhere). if exist f:\*.* net use f: /d Note: Correctly maps drive letter to
network share. Note: Be sure to modify for your correct server name. net use f:
\\ServerName\ShareName /persistent:no if exist g:\*.* net use g: /d net use g:
\\ServerName\applications /persistent:no if exist h:\*.* net use h: /d Note: I have used the variable
'UserName' below. The system will read this as the login name of the user. If you setup a user
share with each user's login name, this line will correctly map a home drive for each user based on
their login name. Don't forget to set security and permissions on the user shares you setup. net use
h: \\ServerName\%username% /persistent:no :PRINTERS rem Connect network printers Note: This
will map your network printers to LPT ports. This is normally only necessary for older legacy (read:
DOS) programs. Note: Be sure to modify for your correct server name. net use lpt1:
\\ServerName\Printer1ShareName /persistent:no net use lpt2: \\ServerName\Printer2ShareName
/persistent:no :END
More options Aug 16 2005, 11:51 am
Newsgroups: microsoft.public.windows.server.sbs
From: "TK - M/T Box Computers"
Date: Tue, 16 Aug 2005 12:51:13 -0500
Local: Tues, Aug 16 2005 11:51 am
Subject: Login Script Sample for Newbies
Reply to author | Forward | Print | Individual message | Show original | Report this message | Find
messages by this author

Because there have been various requests for login script help, I wanted to
post something that may help those who aren't so familiar with writing a
batch file or login script.
DISCLAIMER: I'm not an instructor, I haven't written any books, I don't

write code for a living, and there may be other ways to accomplish the same
thing as I have written. This is intended to help others so please keep
your opinions to yourself unless you have something constructive to add that
will benefit others. Additionally, this example script is intended for
tutorial purposes and will need 'tweaked' to suit your environment. I take
no responsibility for the use of this script in a production environment.
NOTES: There are tremendous amounts of information on the Internet and in

books on how to write scripts, what good practices are, and what variables
can be used in a login script (batch file). This should be enough to get
the average person going in short order. If anything is unclear, or if you
have questions, please post them. Remember, you will need to modify this
script for your server name, network share names, drive letters you require,
printer names, etc.
Okay, with BS out of the way, let's get going. First, you can find your
default login script by clicking Start - Run, type \\ServerName\netlogon,
click OK. This will open a folder with a batch file called
SBS_LOGIN_SCRIPT.bat. Using Notepad, WordPad, or your favorite text editor
open this file (note: you should be able to right-click the file and select
edit from the context menu). This file generally includes only one line
used for SBS client setups. Do not remove this line! It can be moved
around within the script, but leave it intact. If you don't already know
it, this line will tell you the name of your server.
Now, following will be a clean version of my sample login script followed by

a sample with notes. My notes will start with the "Note:" to help you
distinguish the difference. If this helps even one person, it was worth the
time. If you have further questions, please post them for all to learn
from.
Enjoy!
-TK
M/T Box Computers
@echo off
rem ==================================================
rem
rem Title: Login Script
rem Author: Your Name
rem Date: Self-explanatory
rem Description: Network Login Script
rem
rem ==================================================
:SBS_SETUP
rem Default sbs2k3 client setup
\\ServerName\Clients\Setup\setup.exe /s ServerName
:MAPDRIVES
rem Connect network drives

if exist f:\*.* net use f: /d
net use f: \\ServerName\ShareName /persistent:no
if exist g:\*.* net use g: /d
net use g: \\ServerName\applications /persistent:no
if exist h:\*.* net use h: /d
net use h: \\ServerName\%username% /persistent:no
:PRINTERS
rem Connect network printers
net use lpt1: \\ServerName\Printer1ShareName /persistent:no
:END
Note: The word 'REM' is a way to add a remark to your batch file (login
script). It is a good idea to use remarks throughout your login script.
This will help later when troubleshooting why the login script is written
the way it is. You should also document dates of changes and why.
Note: The command 'ECHO' can be used to turn display on and off. 'ECHO'
followed by words will display those words on the screen. 'ECHO OFF' will
suppress all display until 'ECHO ON' is issued.
Note: The @ sign in front of 'ECHO OFF' says to not display this line also.
@echo off
rem ==================================================
rem
rem Title: Login Script
rem Author: Your Name
rem Date: Self-explanatory
rem Description: Network Login Script
rem
rem ==================================================
Note: The use of the colon ':' followed immediately by a word designates the
following lines as a section or routine within your script. This allows you
to move back and forth within the login script. This isn't normally
necessary, but I found it helpful to form good script writing habits early
on. A batch file will normally flow from top to bottom executing every line
it comes to that is not a remark line, and that is an actual command. You
can skip sections by using the 'GOTO' command. Often times I will check for
the existence of the drive mappings after they should have completed. If
they do not exist I will send the user to an error message section letting
them know something failed, with instructions to reboot and/or contact their
IT support. If you would like an example of this also, let me know and I
will post it.
:SBS_SETUP
rem Default sbs2k3 client setup
Note: Leave this line intact somewhere near the head of your script. As you
see here, this is the first actual line that executes in this script.
\\ServerName\Clients\Setup\setup.exe /s ServerName
:MAPDRIVES
rem Connect network drives
Note: Tests for and deletes drive mapping if it exists (ensures drive letter

isn't erroneously mapped elsewhere).
if exist f:\*.* net use f: /d
Note: Correctly maps drive letter to network share.
Note: Be sure to modify for your correct server name.
net use f: \\ServerName\ShareName /persistent:no
if exist g:\*.* net use g: /d
net use g: \\ServerName\applications /persistent:no
if exist h:\*.* net use h: /d
Note: I have used the variable 'UserName' below. The system will read this
as the login name of the user. If you setup a user share with each user's
login name, this line will correctly map a home drive for each user based on
their login name. Don't forget to set security and permissions on the user
shares you setup.
net use h: \\ServerName\%username% /persistent:no
:PRINTERS
rem Connect network printers
Note: This will map your network printers to LPT ports. This is normally
only necessary for older legacy (read: DOS) programs.
Note: Be sure to modify for your correct server name.
:END
How to Deploy Printers with 2003 group policy
This article was found at:

http://www.windowsnetworking.com/articles_tutorials/Deploying-Printers-Group-Policy-Windows-
R2.html
This article walks you through the steps for deploying printer connections to workstations using new
Group Policy capabilities available in Windows Server 2003 R2. This greatly simplifies the
management of printer connections for workstations and can save administrators a lot of time and
effort.
In a previous article titled Managing Printers with Windows Server 2003 R2, we walked through how
to use the new Print Management console that is part of the R2 platform. This console lets you easily
manage printers and print servers from a single, central point of management and can be used to
manage print servers running Windows 2000 Server, Windows Server 2003, Windows Server 2003
R2, and to a limited extent Windows NT 4.0. In that article we saw how to add print servers and
network printers to this console, and how to create and use print filters to get a quick picture of
what's happening with different printers on your network. This is great, but there's another task that
many administrators would love to automate—deploying printer connections to client
computers on their networks. Group Policy seems the natural way to do this, but Windows Server
2003 and earlier have no capability built into Group Policy to deploy printer connections to client. So
until now, to deploy print connections using Group Policy you had to use third-party tools like
AutoProf Policy Maker (note that since I wrote that article, AutoProf has since been renamed
DesktopStandard and their PolicyMaker product line has been expanded). Well, with R2 the
capability to deploy printer connections using Group Policy is now present, and this article walks you
through an example of how to do this. Then, once you've deployed printers to clients you can use
Group Policy to manage these printers as described in my two earlier articles here on
WindowsNetworking.com, namely Managing Printers Using Group Policy (Part 1) and Managing
Printers Using Group Policy (Part 2).
Preparing for Deployment

There are a couple of steps you need to do first before you can deploy printers with Group Policy.
First, you need to ensure that you've upgraded your Active Directory schema to R2 level. If you're
not sure what level your schema is at, use the following table as a guide:
Platform
Schema Revision
Schema Version
Windows 2000
(none)
13
Windows Server 2003
30
Windows Server 2003 R2
31
Table 1

The key numbers are in the last column, and to find your current, use ADSI Edit, look under the
Schema node, right-click on the object named
CN=Schema,CN=Configuration,DC=forest_root_domain, select Properties and examine the value of
the objectVersion attribute. You want this value to read 31 meaning your forest schema is upgraded
to R2 level. If it isn't, you'll need to run the adprep command to raise the schema level, see this
article from the Windows Server 2003 TechCenter on Microsoft TechNet for more info.
Next, you should have the Group Policy Management Console (GPMC) installed and your Group
Policy infrastructure in place, with Group Policy Objects (GPOs) linked to domains and organizational
units (OUs) in various ways to manage settings for users and computers across your forest. Choose
the GPOs you wish to use to deploy printer connections, or create new GPOs for this purpose and
link them accordingly. Note that you can deploy printer connections two ways: per-user (so that
users have their printers regardless of which computers they use on the network) and per-machine
(all users on the affected machines have access to the same set of printers). Note that per-machine
deployment of printer connections is supported on Windows XP and later. In other words, you can
only deploy printers to Windows 2000 Professional clients on a per-user basis, not per-machine.
For purposes of our walkthrough we'll use the same setup shown in my previous article Managing
Printers with Windows Server 2003 R2 where we installed the Print Management console on BOX161,
an R2-level domain controller in the r2.local domain where there are two other print servers named
BOX162 and BOX163. Here's a figure to get you oriented:
Figure 1: The Print Management Console running on BOX161 shows no deployed printers
Note that nothing currently shows under the Deployed Printers node. The client computer we're
going to deploy a printer to (recall that in Microsoft terminology the word "printer" is short for
"printer connection") is a Windows XP machine named XP191, and the next figure shows the
contents of the Printers and Faxes folder on this machine, which indicates no printers are currently
present:
Figure 2: Client computer XP191 currently has no printers installed

Deploying Printers
Now we're ready to begin. Our company has its Sales Department in Vancouver, and Bob Smith is
our Head of Sales there:
Figure 3: Bob Smith is in Vancouver and needs a printer
The Vancouver OU has a Group Policy Object named SalesGPO linked to it (see next figure) and we'll
use this GPO to deploy the printer connection to Bob:

Figure 4: The SalesGPO is linked to the Vancouver OU and will be used to deploy a printer
Open up the Print Management console and select the printer you wish to deploy:
Figure 5: Getting ready to deploy Sales Printer 1 to the target user
Right-click on Sales Printer 1 and select Deploy With Group Policy from the shortcut menu. This
opens the Deploy With Group Policy dialog box:
Figure 6: The Deploy With Group Policy dialog box
Click the Browse button and select the GPO you plan on using to deploy the printer:
Figure 7: The printer will be deployed using the SalesGPO
Click OK to return to the Deploy With Group Policy dialog box. Now since we only want Bob to be
able to use the printer (and not anyone who might log on to his computer) we'll deploy the printer on
a per-user basis, so select the first checkbox in the dialog box:
Figure 8: Deploying a per-user printer connection
Now click the Add button to add the connection settings for Sales Printer 1 to the SalesGPO:
Figure 9: The printer connection is added to the SalesGPO
Click OK a few times and you'll now see the printer under the list of deployed printers:

Figure 10: Sales Printer 1 shows up as deployed to the SalesGPO
Note that this may seem confusing as the printer hasn't actually been deployed to the client yet,
only deployed to the SalesGPO. We still have to do one more thing: deploy a utility called
PushPrinterConnections.exe to the client computer so the client can process the printer connection
settings that have been added to the SalesGPO. But before we do that, let's make sure that the
connection settings for Sales Printer 1 have been successfully added to the SalesGPO. To do this,
open the SalesGPO in Group Policy Object Editor and look under User Configuration and you'll see a
new Deployed Printers node with Sales Printer 1 visible under it:
Figure 11: Connection settings for Sales Printer 1 have been added to the SalesGPO
The way we'll get the PushPrinterConnections.exe utility onto the client is to add it as a logon script
(if you were deploying a per-machine printer connection you'd use a startup script instead). The
easiest way to do this is using Group Policy as follows. Start by opening the SalesGPO in the Group
Policy Object Editor and navigate to User Configuration, Windows Settings, Scripts (Logon/Logoff) as
shown:
Figure 12: Getting ready to add a logon script to the SalesGPO
Right-click on the Logon policy in the right-hand pane and select Properties:
Figure 13: Adding a logon script
Click the Show Files button and copy the file PushPrinterConnections.exe from the
%Windir%\PMCSnap folder into the open policy folder:
Figure 14: Add PushPrinterConnections.exe as a logon script
Close the policy folder and click the Add button on Logon Properties, and type
PushPrinterConnections.exe into the Script Name field:

Figure 15: Add PushPrinterConnections.exe as a logon script (continued)
Click OK a couple of times. The logon script will be displayed in the policy when it has been
successfully added:
Figure 16: Logon script is ready to go
Now all Bob needs to do is log off and then log on again to refresh his per-user Group Policy settings,
and Sales Printer 1 will appear in his Printers and Faxes folder as expected:
Figure 17: Bob has a printer
Final Tips
If you unlink the SalesGPO or move Bob out of the Vancouver OU, the connection to Sales Printer 1
will disappear from his machine the next time he logs on. And if you want to remove the connection
settings for Sales Printer 1 from the SalesGPO, you can open this GPO using the Group Policy Object
Editor, right-click on Sales Printer 1, and select Remove. It's also useful to know that in Figure 15
above, if you add the parameter –log to the Script Parameters field, you can enable logging
of printer connection deployment to help you troubleshoot when things go wrong. The log files
that are created are %temp%\PpcUser.log for per-user connections and
%Windir%\temp\PpcMachine.log for per-machine connections and are stored on the computer where
the printer connection is being deployed.
About Mitch Tulloch
Mitch Tulloch is a writer, trainer and consultant specializing in Windows server operating systems,
IIS administration, network troubleshooting, and security. He is the author of 15 books including the
Microsoft Encyclopedia of Networking (Microsoft Press), the Microsoft Encyclopedia of Security
(Microsoft Press), Windows Server Hacks (O'Reilly), Windows Server 2003 in a Nutshell (O'Reilly),
Windows 2000 Administration in a Nutshell (O'Reilly), and IIS 6 Administration (Osborne/McGraw-
Hill). Mitch is based in Winnipeg, Canada, and you can find more information about his books at his
website www.mtit.com
Click here for Mitch Tulloch's section.
Latest articles by Mitch Tulloch
Windows Vista Resource Kit Chapter 23: Supporting Users Using Remote Assistance (Part 1)

Managing Windows Networks Using Scripts - Part 14: Learning More about WMI Scripting
Introducing Windows Server 2008 - Chapter 7: Active Directory Enhancements
Managing Windows Networks Using Scripts - Part 13: A Handy Return-All-Values Script
Managing Windows Networks Using Scripts - Part 12: Properties of a WMI Class
Related links
Managing Printers with Windows Server 2003 R2

Managing Printers Using Group Policy (Part 1)
Managing Printers Using Group Policy (Part 2)
Using Group Policy to Deploy Applications
Best Practices for Designing Group Policy
take stuff your right click that eats memory
This article was found at: http://www.jfitz.com/tips/rclick_custom.html
Customizing Right-Click
Menu Options in Windows
By John Fitzgibbon
Last updated: Tuesday, April 18, 2006, 11:33 AM PST

Introduction
This document gives step by step instructions for customizing the options that appear on the right-
click menu for various file types. I have found this particularly useful for designing and testing web
pages.
Typically, before uploading a HTML page, you will want to view it in both Netscape and Internet
Explorer, and you may wish to make quick edits using, say, WordPad. To make this easier for myself
I have added a "Netscape" and an "Edit" option to the right-click menu for all HTML files, (IE is my
default browser). This means I can open HTML files in Internet Explorer, Netscape or WordPad with
two clicks, instead of dragging files all over the desktop, or opening applications and doing a "File
Open".
For GIFs and JPEGS, I have also added the Netscape option, and I've linked the "Edit" option to my
favorite graphics editing program.

Warning
This document discusses editing the Windows Registry. This gives you complete control over the
configuration of your menus, but you should be extremely careful not to change Registry values that
are used by other applications. The author accepts no responsibility for any problems that may arise
as a result of any changes to the Registry, even for those changes outlined in this example.
If you want to avoid modifying the registry directly, many of the changes described here can also be
made in Windows Explorer's "Folder Options" menu. To use this approach, double click "My
Computer", select the "Tools" menu, then "Folder Options", then the "File Types" tab. From here, you
can highlight the file type you wish to change, then click the "Advanced" button to change the menu
options that appear for the file type. This won't give you complete control of every option, but it is
probably sufficient for most needs, and it is much less likely to cause problems as a result of
accidental changes to the wrong registry keys.
Some Common Questions

Before tackling how to add menu options, here are a few interesting or common questions I've
received.
Note: I stopped using Windows a few years ago, (I switched to Linux), so I'm afraid I no longer offer
help with Windows Registry problems. Please accept this apology if I don't reply to Windows-related
questions.
Question:
"How do I remove unwanted options that appear on right-click menus after installing software?"

Answer:
Usually, all that is required is to remove the appropriate key under the
shellex\ContextMenuHandlers key in HKEY_CLASSES_ROOT for file type "*". For example:
In the sample shown, deleting "gvim" will remove the right-click options for the GUI Vim program I
installed. I'd recommend making a back up of the key data in case you want to put it back in later. If
you don't find the correct ContextMenuHandlers item under "*" you could try looking under specific
file extensions. You could also try searching the registry for the text that appears on the menu.
When searching, don't forget to preface any character that is underlined in the menu with an "&".
The ampersand is typically used to identify the character to underline when a menu entry's text is
saved in the registry.
Question:
"Can I add a 'Search' option to Internet Explorer's right-click menu?"
Answer:
I've written a script to do just that: http://www.jfitz.com/tips/search.htm
Question:
"Can I disable [insert menu option here] in Internet Explorer's right-click menu?"
Answer:
Non-standard items can be removed from the MenuExt registry key. This can usually be found here:
HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\MenuExt
After removing the offending key, restart IE and the menu item should be gone.
With regard to the default behavior of Internet Explorer, (i.e. the menu items that don't appear in
MenuExt) there are a number of restrictions you can place on newer versions of the browser.
One of the best online sources for information about the various options is at:
http://registry.winguides.com/display.php/442/
You can't specifically disable a single menu item, (at least as far as I'm aware -- there may be some
undocumented way around it), but you can make the menu go away completely. This might be
useful for shared machines in a "public" environment, where changes made through the menu,
(such as setting the computer's background from a web image), could be confusing to other users.
Navigate to:
HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Internet Explorer\Restrictions
Set a DWORD value:
NoBrowserContextMenu = 1
You can also do this just for specific users if you wish. In this case, make the change under
HKEY_CURRENT_USER.
If you export the modified key to a .REG file, (using regedit's export menu option), you can very
quickly copy the change to a number of machines. (.REG files open using regedit when double
clicked and apply the registry changes they contain. The files themselves are simply text files -- you
can verify their contents in notepad or any other editor.)

Modifying the Right-Click Menu
Now on with the show...
First we need to find the location of the program we want to use

(Note: You can also get this information from the "Properties" box if you have a
shortcut to the program on your desktop. Otherwise...)
Click on "Find Files or Folders" in the Start Menu
Search for the program you want to add to the right-click menu
Make a note of the folder where the program is found
Some common programs you might like to use are:
Netscape.exe - Netscape Communicator
IExplore.exe - Internet Explorer
WordPad.exe - WordPad

From the Start Menu select "Run"
Enter "regedit"
This runs the Registry Editor
Open the HKEY_CLASSES_ROOT "folder"

This opens a long list of file extensions, (.exe, .html, .ini, etc)
Following the extension list, extension groups are listed, ( for example "htmlfile"
refers to all files with ".htm" and ".html" extensions, "jpegfile" refers to .jpg and .jpeg files, "giffile"
refers to .png files)
Note: To find the extension group associated with a particular extension, click on
the extension and note the value in the "Data" field, (on the right side), for the value named
"(Default)"
Select the extension, or extension group you wish to modify - typically, you will
want to modify an extension group, rather than an individual extension
In this example we want to add a "Netscape" option to all .html and .htm files, so
we open the "htmlfile" extension group
Note: we could modify each extension separately if we wished

Right click on the "shell" option
Select "New"
Select "Key"
This creates a new key with a default name
Change the key name to whatever you wish to appear on the right click menu
Now right click on the new key

Select "New"
Select "Key"

This creates a "subkey" of the key we just created
Rename this subkey "command"
Note that in the right hand window the name "Default" and "value not set" appear
Double click on the "Default", (or the small "ab" icon to the left)
This brings up an Edit window which is used to set the default value
The "value" to enter is the name of the program to run

The format of the value field is:
FOLDERNAME\PROGRAMNAME "%1"
In this example its:
E:\Program Files\Netscape\Communicator\Program\Netscape.exe "%1"
Note: When we use the new menu option, "%1" is replaced with the name of the
file we clicked on. This tells Netscape which file to open
Click "OK" to set the default value

This completes the process - Right clicking on any "htmlfile" will now have a

"Netscape" option that opens the selected file in Netscape
You can add as many right click options as you wish

In this example, an "Edit" command has also been added which will open the file
using WordPad
Note that the menu options are listed in the order in which they were created
The simplest way to reorder the options is to rename the option that you want to
appear at the end of the list
To rename a menu option, right click on the key in the Registry Editor and select
"Rename"

Rename the key to a temporary name, then rename it back to its original
In the above case, we renamed the "Netscape" option and it now appears below
the "Edit" option
Note that you can remove the menu item by deleting the key in the Registry Editor
The "Delete" option is directly above the "Rename" option
Note that to delete the "Netscape" key, you must first delete its "command" subkey
VLAN on Linux and Switches
This article was found at: http://www.linuxjournal.com/article/7268

Since 1994: The Original Monthly Magazine of the Linux Community
Subscribe Now!
Subscribe Now
Subscribe
New Archive CD
Renew
Customer Service

Magazine
Magazine Archives
Write for Us
Masthead
FAQ
Press Releases
Advertise
Request Media Kit

Editorial Calendar
Online Advertising
General Ad Info
Resources
What Is Linux?
Industry Events
Other Resources
Free eNewsletters
LJ Weekly Update
Off the Shelf
Popular content
Today's:
The Ultimate Linux/Windows System

The Real Meaning of GNU GPLv3
Options in OpenOffice.org Calc

$1.88 an issue!*
Start your risk-free

subscription today!
*based on a 2 yr U.S. sub
Navigation
by subject
recent posts
news aggregator
Home
VLANs on Linux
By Paul Frieden on Thu, 2004-03-11 02:00. Software

An introduction to VLANs and VLAN trunking, how Linux interacts with VLANs and how you
might use them in networks.
To begin, we must have a more formal definition of what a LAN is. LAN stands for local area network.
Hubs and switches usually are thought of as participating in a single LAN. Normally, if you connect
two computers to the same hub or switch, they are on the same LAN. Likewise, if you connect two
switches together, they are both on the same LAN.
A LAN includes all systems in the broadcast domain. That is, all of the systems on a single LAN
receive a broadcast sent by any member of that LAN. By this definition, a LAN is bordered by routers
or other devices that operate at OSI Layer 3.

Now that we've defined a LAN, what is a VLAN? VLAN stands for virtual LAN. A single VLAN-capable
switch is able to participate in multiple LANs at once.
This functionality alone has a variety of uses, but VLANs become far more interesting when
combined with trunking. A trunk is a single physical connection that can carry multiple VLANs. Each
frame that crosses the trunk has a VLAN identifier attached to it, so it can be identified and kept
within the correct VLAN.
Trunks can be used between two switches, between a switch and a router or between a switch and a
computer that supports trunking. When connecting to a router or computer, each VLAN appears as a
separate virtual interface.
When using trunks, it is important to consider that all the VLANs carried over the trunk share the
same bandwidth. If the trunk is running over a 100Mbps interface, for example, the combined
bandwidth of all the VLANs crossing that trunk is limited to 100Mbps.
Advantages of VLANs
VLANs provide a number of benefits to a network designer. The first advantage is the number of
devices required to implement a given network topology can be reduced. Without VLANs, if your
network design requires ten machines divided into five different LANs, you would need five different
switches or hubs, and most of the ports would be wasted. With VLANs, this work could be done with
one device.
Most routers and standard computers can support a limited number of physical network interfaces.
Although dual and quad-port Ethernet adapters are available, these are expensive. For example, a
quad-port Ethernet card may cost $400. VLAN capable switches start at around $500, but they
support many more interfaces.
Depending on the scenario, VLANs and trunks can provide an effective way of segmenting a network
without the expense and complexity of managing many physical interfaces.
Types of Trunks
Several trunk encapsulations are available. Trunks can be carried across a variety of interface types,
but this article deals only with Ethernet. The two main protocols for carrying VLANs over Ethernet
are ISL and 802.1q. ISL was created by Cisco prior to the standardization of 802.1q and is
proprietary. 802.1q, on the other hand, is an open standard and is widely supported. Hereafter,
references to trunking mean 802.1q-over-Ethernet. As a side note, 802.1q is defined on only
100Mbps or higher Ethernet; it does not support 10Mbps.
How VLANs Work
Trunks using the 802.1q protocol work by adding a 4-byte VLAN identifier to each frame. This is used
on both ends to identify to which VLAN each individual frame belongs. When a switch receives a
tagged unicast frame, it looks up the outgoing port using both the destination MAC address and the
VLAN identifier. When a broadcast frame is received, it is flooded out to all active ports participating
in that VLAN.
When a VLAN-aware router or computer receives a tagged frame, it examines the tag to determine
to which virtual interface the frame belongs. This virtual interface can have an IP address and
behaves basically the same as a normal physical interface.
Some switches have the concept of a native VLAN on a trunk connection. Packets sent out from the
trunk port on this VLAN are untagged. Likewise, untagged packets received on this port are
associated with this VLAN. Native VLANs on both ends of a trunk must match. A native-VLAN
mismatch on the two ends of the trunk causes problems using the native VLAN configured on each
end.

Security Considerations for VLANs and Trunks
For all the benefits of VLANs and trunking, some risks must be weighed. As opposed to physical
separation between network segments, VLANs rely on the switch to do the right thing. It is possible
that a misconfiguration or a bug could cause the VLAN barriers to be broken.
Two risks are associated with VLANs. In the first, a packet leaks from one VLAN to another, possibly
revealing sensitive information. In the second, a specially crafted packet is injected into another
VLAN. Any attack that could cause the VLAN barriers to break requires a machine directly attached
to the physical network. This means that only a local machine can execute an attack against the
switch.
When the switch is configured properly, the chances of these problems happening are slim, but the
possibility still exists. It is up to you to examine your needs and your security policy to determine if
VLANs are right for you.
It is beyond the scope of this article to describe exactly how to configure your switch securely, but
most vendors provide documentation outlining best practices. Briefly, you should configure at least
the following:
Disable trunking and trunk negotiation on all ports except those absolutely necessary.
Enable MAC flood protection on all ports.
Isolate the management VLAN from workstations and servers.
Linux and VLANs
Linux has long been able to connect to VLAN trunks with a kernel patch, and the functionality was
integrated into the mainstream kernel in 2.4.14. Kernel 2.6 also supports VLAN trunking.
In order to use 802.1q trunking, simply set the CONFIG_VLAN_8021Q option when configuring your
kernel. Depending on what Ethernet card you have, you may need to patch the driver to make
VLANs work correctly. This process is discussed in greater detail later in the article.
MTU Issues
As mentioned earlier, 802.1q works by tagging each frame with a 4-byte VLAN identifier. However,
some Ethernet drivers assume the maximum frame size is 1,500 bytes. The addition of the 4-byte
tag does not leave as much room for data. Thus, although small packets are sent and received
correctly, large packets fail. The solution is either to drop the MTU of the VLAN device or to correct
the assumptions of the driver.
Patches are available on the Linux VLAN Web site for a variety of cards (see Resources). Several
drivers work correctly out of the box (or tar.gz, as the case may be), including the e100 driver for
Intel-based cards.

Linux Configuration
Configuring VLANs under Linux is a process similar to configuring regular Ethernet interfaces. The
main difference is you first must attach each VLAN to a physical device. This is accomplished with
the vconfig utility. If the trunk device itself is configured, it is treated as native. For example, these
commands define VLANs 2-4 on device eth0:
vconfig add eth0 2
vconfig add eth0 3
vconfig add eth0 4
The vconfig program can set a variety of other options, including device-naming conventions.
Hereafter, these are assumed to be at their defaults.
Once the virtual interfaces are defined, they can be used in the same way as other interfaces. The
standard utilities, such as ifconfig and route, all accept VLAN interfaces and behave as expected. For
example, all VLAN interfaces can be listed with ifconfig -a.
Depending on your distribution, support may be available for automatically configuring VLANs on
startup. Debian 3.0 or greater supports this support, but Red Hat and Fedora currently do not. For
other distributions, you simply need to write a script that executes vconfig prior to the main network
startup scripts.
Switch Configuration
Because the configuration interfaces for different brands of switches all are different, the focus of
this section is the common Cisco 2924. All switch configurations are from this model but should work
with little change on other IOS-based switches. A variety of configuration commands are related to
trunking, but only the most basic are covered here. The samples also assume the ports all have a
default configuration. Specifically, this means all ports are configured as access ports in VLAN 1.
This article focuses on the Linux side of the configuration, so only a basic explanation of the switch
commands are given. Listing 1 is a configuration fragment that could be entered into a Cisco
Catalyst 2924 switch. See Resources for URLs to complete documentation of these commands.
Listing 1. Configuring a Cisco Catalyst 2924 Switch

interface FastEthernet 0/1
switchport mode trunk
switchport trunk encapsulation dot1q
switchport trunk native vlan 1
switchport access vlan 2
The commands here are fairly self explanatory if you are familiar with the VLAN terminology
presented earlier. Briefly, the first section converts the first port into a trunk running 802.1q
encapsulation with native VLAN 1. The second section simply moves port 2 into VLAN 2.
It is important to see how VLANs are configured and operating on the switch. The first task is to see
the status of a particular port. This can be done with show interfaces switchport command.
Listing 2. show interfaces switchport

#show interfaces FastEthernet 0/1 switchport
Name: Fa0/1
Switchport: Enabled
Administrative mode: trunk
Operational Mode: trunk
Administrative Trunking Encapsulation: dot1q
Operational Trunking Encapsulation: dot1q
Negotiation of Trunking: Disabled
Access Mode VLAN: 0 ((Inactive))
Trunking Native Mode VLAN: 1 (VLAN0001)
Trunking VLANs Enabled: ALL

Trunking VLANs Active: 1-5
Pruning VLANs Enabled: 6-1001
...
Probably the most useful command is the show vlan command. It shows you a table indicating which
ports are in which VLANs.
Example
The best way to see how VLANs work is by example. Imagine you work for Widgets, Inc. There are
about 20 people from several departments working at your location. Ten people work in engineering,
two people are in accounting, five people in sales and three people in marketing. Widgets, Inc.
currently has a flat network, one in which all the machines are on the same LAN. All of these
machines are connected to a Cisco 2924 switch and reside in the 10.0.0.0/24 private network.
Figure 1. Widgets, Inc.'s Private Network
To improve security, you have convinced management to let you segment the network. You already
have a Linux firewall running Debian 3.0 facing the Internet, but now you need to extend it to
segment the network. The first snag is you have been given only a minimal budget for the project.
After some consideration, you have decided to separate the inside network into four segments:
Management, Sales & Marketing, Accounting and Engineering and a DMZ for your assorted servers.
The management VLAN has no workstations associated with it and is used only for the switch's
configuration interface.
Figure 2. The Segmented Network
Your existing firewall cannot accommodate three more physical interfaces. You recently read an
interesting article about how to use VLANs with Linux, which gives you an idea. With VLANs, the new
topology can be implemented with the existing interfaces. In fact, the physical layout of your
network doesn't change at all. Using VLANs adds a management network to the mix, bringing the
total to five.
Figure 3. The Segmented Network with VLANs
You also have decided to subnet your existing IP addresses for the new segments. Using a subnet
mask of 255.255.255.224 gives you plenty of IPs for each segment and leaves you several spare
subnets to use later. You already are using DHCP to assign IP addresses, so client reconfiguration is
not an issue.
Listing 3. Assigning IP Addresses

Description VLAN IP Subnet
Management 1 10.0.0.0/27
DMZ 2 10.0.0.32/27
Accounting 3 10.0.0.64/27
Engineering 4 10.0.0.96/27
Sales & Marketing 5 10.0.0.128/27
Preparation
Because the network changes here can cause a loss of connectivity, it is important to have
everything prepared beforehand. Ensure that your firewall meets the prerequisites above. It also is
recommended that you have a serial console connection available before you begin. Obviously,
these kinds of changes should be done after business hours.
Preparation is the most important part of a network project. In this case, it is important to have
everything planned out well in advance. You should have planned out your firewall policy, server
configuration, DNS update and so on. Think about all the functions required for the daily operation of
your network, and consider how the changes described here might effect them. For example,

reducing the DHCP lease time several days in advance allows the workstations to retrieve their new
leases more quickly.
Firewall Configuration
The first step towards the new network configuration is to establish the trunk between the firewall
and the switch. On Debian, the vlan package contains the required utilities. Most other distributions
also offer a package containing these utilities. Compile and install your kernel as you normally
would, and enable 802.1q support (CONFIG_VLAN_8021Q).
The Debian interfaces file, located in /etc/network/interfaces, provides support for creating VLAN
interfaces. Each interface is defined as normal, with the addition of a vlan_native_interface line. If
your distribution does not support defining VLAN interfaces, you need to have a script define them
before network startup. Listing 4 shows a Debian interfaces file, using DHCP to retrieve the IP for the
outside interface.
Listing 4. A Debian Interfaces File

auto lo
iface lo inet loopback
auto eth0 eth1 vlan2 vlan3 vlan4 vlan5
iface eth0 inet dhcp
# VLAN 1 - native management VLAN
iface eth1 inet static
address 10.0.0.1
netmask 255.255.255.224
vlan_raw_device eth1
# VLAN 2 - DMZ
iface vlan2 inet static
address 10.0.0.33
netmask 255.255.255.224
# VLAN 3 - Accounting
address 10.0.0.65
netmask 255.255.255.224
# VLAN 2 - DMZ
address 10.0.0.33
netmask 255.255.255.224
# VLAN 3 - Accounting
address 10.0.0.65
netmask 255.255.255.224
# VLAN 4 - Engineering
address 10.0.0.97
netmask 255.255.255.224
# VLAN 5 - Sales & Marketing
address 10.0.0.129
netmask 255.255.255.224
If you were using a distribution other than Debian, you could put lines similar to the ones in Listing 5
in a startup script that runs before network configuration.
Listing 5. Startup Script for Non-Debian Distributions

vconfig add eth1 2
vconfig add eth1 3
vconfig add eth1 4

vconfig add eth1 5
Once the new interfaces are defined, you can bring them up using ifup . You also need to ifdown and
ifup eth1 to set the correct IP and netmask.
Switch Configuration
Before you begin configuration, make sure the IP address of the switch falls within the new
management subnet. The IP configuration is associated with a virtual interface. This is normally
VLAN1.
Listing 6. IP Address for VLAN1

interface VLAN1
ip address 10.0.0.2 255.255.255.224
The firewall is connected to port 1 on the switch, which is referred to as FastEthernet 0/1 in IOS
notation. The first task is to set the encapsulation and native VLAN, then you can enable the trunk.
Listing 7. Enabling the Trunk

switchport trunk encapsulation dot1q
switchport trunk native vlan 1
switchport mode trunk
Once the trunk is active, you need to move ports from the default VLAN into their new one. This is
done by entering the interface configuration and issuing switchport access vlan . Although not
necessary, it is helpful to physically group VLANs to make them easier to manage.
Listing 8. Moving the Ports

interface FastEthernet0/2
Once your changes are complete, you can see which ports are in which VLAN by using the show vlan
command.
Finishing Up
The first order of business is to test whether you can move packets of all sizes successfully without
MTU issues. Packets above 1,476 bytes should trigger any MTU issue you have. This can be tested
by pinging from the firewall to a machine on a non-native VLAN. If small packets work but large
packets do not, you most likely have an MTU issue.
Because you are using DHCP, you now need to update your dhcpd.conf file to reflect the new
subnets. Once it is restarted, client machines start to receive their new IP addresses.
Without a policy, a firewall is useless. Unfortunately, defining that policy is beyond the scope of this
article. However, a variety of effective tools are freely available for this purpose.
Now that everything is working, we need to make sure the switch's new configuration is written to
memory. This is done from enable mode using the write memory command.

Conclusion
As you can see, VLAN trunking can be a valuable tool. I hope you have learned where it can be
useful, the risks and benefits of using it and the basics of its configuration. Even though this
document focuses on a Cisco 2924 switch, it shouldn't be difficult to translate the configuration here
to any switch that supports 802.1q trunks.
I would like to give special thanks to Cheryl Lehman for helping to make my first article readable and
to Randall Shutt for reviewing the content.
Resources
802.1Q VLAN implementation for Linux
Using the Command-line Interface for Catalyst 2900XL Switches
Cisco Catalyst 2900XL IOS Command References
Bookmark/Search this post with:
digg |
reddit
» add new comment | email this page | printer friendly version |
digg |
reddit | 79615 reads
Comment viewing options
Flat list - collapsed

Flat list - expanded
Threaded list - collapsed
Threaded list - expanded
Date - newest first

Date - oldest first
10 comments per page


Select your preferred way to display the comments and click "Save settings" to activate
your changes.
great article
Submitted by Anonymous (not verified) on Sat, 2006-10-21 12:31.
Thanks for this :)
» reply | email this page
figures in this article

Submitted by Anonymous (not verified) on Thu, 2006-02-02 09:15.
I cannot view the figures in this article,it would be useful to view them.Has anyone got them
This article exactly hit the

Submitted by Anonymous (not verified) on Tue, 2005-06-28 19:19.
This article exactly hit the nail on the head! I was to able create a "layer 3 switch" with an unused PC
running Linux and an old 3Com superstack 3300 switch for our test lab. Suprisingly fast, it's clearly
faster than what I suspected (although certainly not as fast a real L3 switch)
Thanks a million! It really got me going!
vlan switch connect to linux gateway

Submitted by Anonymous (not verified) on Thu, 2005-03-24 07:37.
dear
I did configure the switch to use vlan's and I did connect that switch to linux gateway machine.
must I configure vlan under the linux machine also OR just on the switch ?
pleas replay i need help
greeting
Re: VLANs on Linux - basic switch vlan aware

Submitted by Anonymous on Thu, 2004-07-29 01:00.

this is an item I just ordered for a client:
http://store.elementsource.com/elementsources/bgfoncol16po.html
* 16 x 10/100Mbps Auto-negotiation, Auto-MDI/MDIX TP ports

* Supports QoS function based on IEEE 802.1p/802.1q port priority, VLAN tag priority and TCP/IP
header�s TOS/DS
* Supports VLAN, up to 16 group VLANS
* Provides console port and software for easy configuration
* Full/Half duplex transfer mode for each port
* Store-and-Forward switching method
* Extensive front-panel diagnostic LEDs
* IEEE 802.3x flow control for full-duplex
* Back pressure flow control for half-duplex
I ordered it for general networking purposes but I will (in the future) try some VLAN stuff since I want
to separate wireless access to different subnets.
Re: VLANs on Linux

Submitted by Anonymous on Wed, 2004-06-30 01:00.
How to organize domain server by help of Linux Vlan router.

For instance I have VLAN: 2,3,4,5 and I want the traffic from them to be routed in vlan 10 (server's
VLAN) but 2,3,4,5 must don't touch. Help!
Re: VLANs on Linux and Trunk

Submitted by drp666c (not verified) on Tue, 2004-06-15 01:00.
Hi,
Since a switch can have trunk ports that sees traffic from all VLANs is it possible to configure the
interface in Linux to see traffic from all VLANs .. kinda like a trunk interface?
Thanks
Re: VLANs on Linux and Trunk

Submitted by BK (not verified) on Fri, 2005-01-07 04:17.
Yes It is possible. you will need to enable in the 802.1Q option in the kernel, recompile, and install
the vlan package to get the vconfig utility which enables you to add vlan interfaces.
VLANs on linux
Submitted by anwar (not verified) on Mon, 2005-09-19 02:22.
Yes,I enabled in the 802.1Q option in the kernel, recompiled, and installed the vlan package to get
the vconfig utility which enables to add vlan interfaces.
I have one question ,

can I get vlan id through snmp commands ?
If yes,what are neccessary to be installed .
And what is the command.
Pls mail me the solution
With Rgds
Anwar
VLANs on Linux
Having no previous knowledge about vlans or switch configuration and being suddenly tasked with
setting up multiple vlans on a switch configured from a single ethernet connection on a debian
system, I found this article invaluable. Thanks.
Re: VLANs on Linux

If we create VLAN interface

vconfig add eth1 2
and not give it IP address, is it possible to create script which would manage network traffic for
VLAN2.
For example, would this command work:
iptables -A FORWARD -i vlan2 -j DROP
Thanks
Outstanding issues with VLANs on Linux

Linux does not support VLANs over anything but physical ethernet cards. No aggregate links or the
bridge device, either of which would be a huge win for building fault tolerant routers.
Hardware VLAN tagging / untagging was not supported last time I checked (huge difference on GbE
or 10GbE)
iptables hasn't figured out quite how to deal with VLANs (although last I heard there was a module in
the works)
Outstanding issues with VLANs on Linux

Submitted by Anonymous (not verified) on Sat, 2005-05-14 20:12.
What about GVRP? Does the linux vlan implementation include support for GVRP?

Re: Outstanding issues with VLANs on Linux
Submitted by Anonymous on Tue, 2004-08-31 01:00.
use cisco
Re: VLANs on Linux - Still Cloudy

Still a little cloudy if this is necessary all the time when using all Linux workstations on a network.
For instance, you have two switches linked together to share various VLANS (i.e. VLAN 1 and VLAN 2
have ports on both switches) and you have 2 physical LANs with different network addresses.
Physical LAN 1 is part of VLAN 1 and physical LAN 2 is part of VLAN 2. Both physical lans are
connected to a router (Linux box with 2 Ethernet cards) via the switches. With this setup isn't all this
transparent to the the Linux workstations? If you want to talk to the other VLAN or physical network
it would go to the router. In this scenario you would not need to do all the configuration mentioned
in the article? The reason I ask is that we need to mix and match fiber and copper. The above
scenario would enable us share the switches between the physical LANs. We would not be required
to use two switches for each LAN (one copper one fiber). Also, it would still maintain separate
broadcast domains for the physical LANs. Am I way off base?
Re: VLANs on Linux

Submitted by Anonymous on Sat, 2004-03-13 02:00.
I had 3c905C card on my RH9 Linux box. I made 2 VLAN and http traffic stopped. Before this
everything worked fine. I tried to change cards and so on. I fixed it only when removed the 3c905
card and installed DFE-538TX card. It seemed 3c905 driver has some bugs. I guess it is a bug of
assigning or management MTU.
Red Hat/Fedora VLAN support

The article states that Red Hat/Fedora does not support VLAN setup on
boot. This is incorrect.
VLAN support has been in Red Hat Linux since version 9 and is included
in Fedora.
Documentation on configuring is available in the file sysconfig.txt which

is included in the initscripts RPM (ie less `rpm -ql initscripts|grep sysconfig.txt` )
Re: Red Hat/Fedora VLAN support


Thank you for noticing this. I had looked for RedHat support but hadn't found it until you pointed it
out.
For those of you using RedHat or Fedora, I'm including the configuration for the VLAN2 interface in
the example. This would be place in the /etc/sysconfig/network-scripts/ifcfg-eth1.2 file.
DEVICE=eth1.2 # eth1 is the interface and .2 is the VLAN id

IPADDR=10.0.0.33
NETMASK=255.255.255.224
VLAN=yes
ONBOOT=yes
BOOTPROTO=none
The RedHat scripts always configure VLAN interfaces using the device and the VLAN ID without
padding, which differs from the article. The interface created above would be eth1.2 rather than
vlan2.
Paul Frieden

Submitted by Anonymous on Mon, 2004-03-15 02:00.
actually, on fedora/RHEL3/RH9 , add to /etc/sysconfig/network

VLAN=yes
having the ETH driver patched to support 1504 mtu's the normal eth's had to have their mtu capped
to 1500... to do that, add to the /etc/sysconfig/network-scripts/ifcfg-ethX MTU=1500 and to the ifcfg-
ethX.X MTU=1504
my to cents

does this also work in fedora core 2?
jason
Article lacks important details

Submitted by Anonymous on Fri, 2004-03-12 02:00.
Namely, details of using iptables with the defined vlan interfaces. Can you treat them as physical
interfaces with iptables? Does each vlan have an INPUT chain? Etc..
- cameron

Re: Article lacks important details
VLAN interfaces behave exactly as normal physical interfaces do in iptables. You can specify them
for rules as incoming (-i) and outgoing (-o) interfaces.
I haven't had any issues with VLAN interfaces behaving differently than normal interfaces do any
any of my deployments. I do know that in the past there were some issues with DHCP, but I have
never had any problems with it myself.
Paul Frieden
Several things to note.

The linux kernel, at least, can handle VLANs on 10bt interfaces,

though it is likely you would have MTU issues on really ancient NICs.
Very cheap un-managed switches can also pass VLANs, though

you will not necessarily get the benefits of broadcast domain
restriction. For just playing with the technology, however, it is fine.
Some known good drivers include tg3, e100, e1000

At one time, the rtl8139 also worked out of the box but I haven't
tested it lately.
There are patches to various drivers found on this page:

http://www.candelatech.com/~greear/vlan/howto.html
Enjoy,
Ben Greear
Re: VLANs on Linux

Excellent article!
I appreciate the info on how to configure the switch to properly trunk to the Linux box as well as the
clear introduction and examples.
I may pull that old 2900 out of the closet and actually play with this.
Re: VLANs on Linux

I'm terribly sorry but this was a crappy article. Understanding how to configure interfaces is done in
two seconds. The MTU issues are a big problem that you wrestle with for much longer. Until recently
(or does it still apply?) you had to patch your ethernet interface drivers manually in the kernel to
adjust the maximum MTU size.
Also you have to adjust your ruleset to accompany the larger packets. Then some drivers are buggy

and will crash when you increase MTU above the standard 1500 (not to speak of crappy taiwanese d-
link switches that lock up from time to time).
All this is skimmed through with one sentence that it "could be issues". You might say that, yes.
Re: VLANs on Linux

I disagree with your criticism of the article. He did adequately address tne issue of limited/buggy
Linux ethernet drivers (though a link to a more indepth resource, perhaps a Wiki page where various
kernel hackers list links to their patches, would be nice).
Noting that some cheap ethernet equipment might also choke when connected to a trunk line would
be nice, but is also above and beyind the call of this article.
As for how trivial the interfaces are to set up, configure and use --- that's the core of the article. I
teach professional sysadmin courses, and compile kernels for breakfast (well, usually I start them
before I go to bed, actually).
I've been seeing the VLAN 802.1q patch available for years and was vaguely familiar with VLANs
from working alongside Cisco networks on numerous occasions. However, I'd never used the VLAN
features, didn't know about the 'vconfig' command, wouldn't have known that the vlan* interfaces
needed to be bound to their physical interfaces with it, and generally would have had to hunt around
a bit to find that info.
This article introduced the concept well, and gave me enough info that I could fire up an old Cisco
2900 switch I have laying around and play with the functionality with no fuss. (Well, no fussing on
the Linux side; I have no idea what state that 2900 is in and how I would fix it up; it's on permanent
loan from a friend).
It's one of the best articles I've seen recently. I like the fact that he covers the basics of using Cisco
IOS or is it CatOS for the other side of this effort; stressing how the switch must talk to the Linux box
in trunk mode, and giving examples of setting up the other ports as well.
Re: VLANs on Linux

I abolutely agree with the reply to the original post. This was not intended to be an in depth article
on vlans but introductory one to help a user new to vlans quickly set up to use them. I found it
helpful in answering some questions I had since this just came up at work eg. can I trunk a linux box
to a Cisco 3550 or do I need to buy another switch.
All in all a great starter article for anyone interested in getting started using vlans. BTW he does
throw in some caveats regarding NIC drivers and MTU.
Thanks for the article!
Re: VLANs on Linux

I understand the benefits of VLANS, but I'm not quite sure what the purpose of configuring VLANS at

the OS level is. Could you explain the purpose or benefit of configuring VLANS on Linux? Why would
you need to do it you already configured VLANS in your switch.
Thanks.
Re: VLANs on Linux

Need some more detail information, etc router, iptable.
Re: VLANs on Linux

We use it for management. The public addresses of our servers only do serving, there is no
management (ssh fx) on these addresses. Instead we use a separate LAN for management access.
We could put a separate nic in each server, but it is much easier to just add a VLAN on eth0.
Our management VLAN is tagged throughout the network, so for me to get access to it, my
workstation needs to support VLAN's too. My eth0 is configured like any other user's, but then I also
have an eth0.2 configured, which happens to be our management VLAN.
The switch is configured to allow VLAN 2 only on the switch port where I sit, not on everybody else's.
So normal users simply can't have access to VLAN 2. So there is no way they can even connect to an
open port 22.
BTW we use Extreme Summit200 switches, and I like their syntax:

create vlan users
config users tag 10
config users ipaddress 192.168.1.1/24
config users add ports 1-24
create vlan management

config management tag 2
config management ipaddress 192.168.0.1/24
config management add ports 18 tagged
Simon
Re: VLANs on Linux

If you want to have a big NFS server directly on two or more subnet (without routing traffic trough
the FW)
Re: VLANs on Linux


You'd do it when you want your Linux box on the trunk line to be a router from one VLAN to another,
and perhaps even to run a Snort or Prelude IDS or other NIDS (network intrusion detection system)
on on one or more of the VLANs.
I personally prefer separated switches or hub when I can --- especially for the DMZ and server room
segments. However, VLANs become important at a certain scale (as do manageable, SNMP switches).
Re: VLANs on Linux

To route packets between vlans (applying firewall rules in the process). Using virtual interfaces
instead of physcial is (obviously) a lot cheaper, provided that your switch is intelligent enough.
Re: Vlan configuration

Submitted by Anonymous (not verified) on Wed, 2007-07-04 05:11.
I have a Linux box and am planning to configure a VLAN .. Please tell me how to configure a VLAN in
that linux box
Skyscraper Ad

Button 1 zone 6
Text Ad Two - zone 10
Text ad twelve - zone 22
Find Bugs, Memory Leaks

TotalView is THE debugger
for threaded or parallel code.
Get an evaluation copy.

Text ad 11/z21
Linux Journal for $1.88

Subscribe to LJ today for
as low as $1.88 an issue.
linuxjournal.com/subscribe
Strong Health Magazine
div#block-block-38 div.title { display: none }

div#block-block-38 { padding: 0px 0px 0px 4px; margin: 0px; }LJ is a proud supporter of
Strong Health Magazine
Advertise Community Contact Us Privacy Statement Report Problems
Copyright © 1994 - 2007 Linux Journal. All rights reserved.
how to refresh group policy settings on a windows 2000 machine. gotta

do it from start->run

Link found at: http://kb.iu.edu/data/ajjt.html
Indiana University
University Information Technology Services
Skip to content
Indiana University Knowledge Base
* Home
* Menus
* Glossary
* Help
Text size: Text size: smallText size: mediumText size: large

Enter search terms:
Include archived documents What are archived documents?
Search results per page
Using Microsoft Windows 2000, how do I force a group policy to be applied?
When you make a change to a Group Policy Object (GPO), the change takes place on a Windows
2000 domain controller. The change then replicates to all other domain controllers in the Active
Directory. All Windows 2000 computers in Active Directory check for modifications to GPOs at
regular intervals. If there are changes, then they are applied during the next interval.
If you need to apply the change immediately, you can use one of the following commands to trigger
the process:
* To refresh the group policy for the local computer, enter: secedit /refreshpolicy machine_policy
* To refresh the group policy for the user currently logged in, enter: secedit /refreshpolicy
user_policy
These commands compare the currently applied GPO to the GPO located on the domain controllers.
If nothing has changed since the last time the GPO was applied, then the GPO is skipped.
To force a GPO to be reapplied, whether or not changes have been made to the GPO, use the
/enforce switch: secedit /refreshpolicy machine_policy /enforce Once Windows 2000 accepts the
request, it will display the following message:
"Group policy propagation from the domain has been initiated for this computer. It may take a few
minutes for the propagation to complete and the new policy to take effect. Please check Application
Log for errors, if any."
This information was adapted from article 227448 in Microsoft's knowledge base.
You can search Microsoft's knowledge base at:

http://support.microsoft.com/default.aspx
Also see:
* In Microsoft Active Directory, what are group policies?

* Using Windows 2000, how do I change the group policy refresh rate?
* In Windows 2000, XP, 2003, or Vista, why doesn't my group policy take effect immediately?
* In the IU Active Directory, how can I change the default group policy inheritance behavior?
* In Active Directory, is group policy inherited?
* In the IU Active Directory, how are group policy conflicts handled?
* In Windows Active Directory, how can I assign or publish a .MSI file?
* Using Windows XP or Vista, how do I force a group policy to be applied?
This is document ajjt in domain all.

Last modified on March 07, 2007.
Please tell us, did you find the answer to your question?
*
*
*
Indiana University

* UITS Services and Support
* About the Knowledge Base
* KB Comments
* Login
* Copyright 2005-2007, The Trustees of Indiana University

* Copyright Complaints
Eliminate Balloon Tips in XP
1.
Click Start, click Run, type regedit, and then press ENTER.
2.
Navigate to the following subkey:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced
3.
Right-click the right pane, create a new DWORD value, and then name it EnableBalloonTips.
4.
Double-click this new entry, and then give it a hexadecimal value of 0.
5.
Quit Registry Editor. Log off Windows, and then log back on.
These steps disable all Notification Area balloon tips for this user. There is no way to disable balloon
tips for specific programs only

PDF

Încărcat de

Informații document

Descriere originală:

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

PDF

Încărcat de

Drepturi de autor:

Formate disponibile

Network Fun Category

Tips and Tricks to maintain networks for the advanced user .

Generated by KnowledgeBuilder - http://www.activecampaign.com/kb

Generated by KnowledgeBuilder - http://www.activecampaign.com/kb

Windows Error Messages

Windows Error Messages

MS Windows Error Messages

Code Error Message

Generated by KnowledgeBuilder - http://www.activecampaign.com/kb 1 of 90

Generated by KnowledgeBuilder - http://www.activecampaign.com/kb 2 of 90

Generated by KnowledgeBuilder - http://www.activecampaign.com/kb 3 of 90

Generated by KnowledgeBuilder - http://www.activecampaign.com/kb 4 of 90

Generated by KnowledgeBuilder - http://www.activecampaign.com/kb 5 of 90

Generated by KnowledgeBuilder - http://www.activecampaign.com/kb 6 of 90

Generated by KnowledgeBuilder - http://www.activecampaign.com/kb 7 of 90

Generated by KnowledgeBuilder - http://www.activecampaign.com/kb 8 of 90

Generated by KnowledgeBuilder - http://www.activecampaign.com/kb 9 of 90

Generated by KnowledgeBuilder - http://www.activecampaign.com/kb 10 of 90

Generated by KnowledgeBuilder - http://www.activecampaign.com/kb 11 of 90

Generated by KnowledgeBuilder - http://www.activecampaign.com/kb 12 of 90

Generated by KnowledgeBuilder - http://www.activecampaign.com/kb 13 of 90

Generated by KnowledgeBuilder - http://www.activecampaign.com/kb 14 of 90

Generated by KnowledgeBuilder - http://www.activecampaign.com/kb 15 of 90

Generated by KnowledgeBuilder - http://www.activecampaign.com/kb 16 of 90

Generated by KnowledgeBuilder - http://www.activecampaign.com/kb 17 of 90

Generated by KnowledgeBuilder - http://www.activecampaign.com/kb 18 of 90

Generated by KnowledgeBuilder - http://www.activecampaign.com/kb 19 of 90

Generated by KnowledgeBuilder - http://www.activecampaign.com/kb 20 of 90

Generated by KnowledgeBuilder - http://www.activecampaign.com/kb 21 of 90

Generated by KnowledgeBuilder - http://www.activecampaign.com/kb 22 of 90

Generated by KnowledgeBuilder - http://www.activecampaign.com/kb 23 of 90

Generated by KnowledgeBuilder - http://www.activecampaign.com/kb 24 of 90

Generated by KnowledgeBuilder - http://www.activecampaign.com/kb 25 of 90

Generated by KnowledgeBuilder - http://www.activecampaign.com/kb 26 of 90

Generated by KnowledgeBuilder - http://www.activecampaign.com/kb 27 of 90

Generated by KnowledgeBuilder - http://www.activecampaign.com/kb 28 of 90

Generated by KnowledgeBuilder - http://www.activecampaign.com/kb 29 of 90

Generated by KnowledgeBuilder - http://www.activecampaign.com/kb 30 of 90

Generated by KnowledgeBuilder - http://www.activecampaign.com/kb 31 of 90

Generated by KnowledgeBuilder - http://www.activecampaign.com/kb 32 of 90

Generated by KnowledgeBuilder - http://www.activecampaign.com/kb 33 of 90

Generated by KnowledgeBuilder - http://www.activecampaign.com/kb 34 of 90

Generated by KnowledgeBuilder - http://www.activecampaign.com/kb 35 of 90

Generated by KnowledgeBuilder - http://www.activecampaign.com/kb 36 of 90

Generated by KnowledgeBuilder - http://www.activecampaign.com/kb 37 of 90

Generated by KnowledgeBuilder - http://www.activecampaign.com/kb 38 of 90

Generated by KnowledgeBuilder - http://www.activecampaign.com/kb 39 of 90

Generated by KnowledgeBuilder - http://www.activecampaign.com/kb 40 of 90

Generated by KnowledgeBuilder - http://www.activecampaign.com/kb 41 of 90

Home Page www.gregorybraun.com

View Public Profile

Send a private message to cheyenne1212

Visit cheyenne1212's homepage!

Find More Posts by cheyenne1212

Generated by KnowledgeBuilder - http://www.activecampaign.com/kb 42 of 90

geepod vbmenu_register("postmenu_638350", true);

Join Date: Jun 2002

the real meanings of the error codes

thought i would include the real meanings of the error codes!

WindowError:001 Windows loaded. System in danger!

Generated by KnowledgeBuilder - http://www.activecampaign.com/kb 43 of 90

Net Use Command

Connects a computer to or disconnects a computer from a shared resource, or displays information

net use [{DeviceName | }] [\\ComputerName\ShareName[\volume]] [{Password | }]]