12.5 Error Codes
While you are using the PacketiX VPN 2.0 software you may see an
error message, an error code, or both at the same time. This section
provides you with a list so that you can easily determine error messages
from error codes, and discusses the main causes of these errors.
Error 1: Connection to server failed. Check network connection, and
address and port number of destination sever.
This error occurs when a connection attempt to the hostname/IP
address and port entered by the user fails. When this error occurs you
should check to make sure your computer is connected to the network and
that the hostname/IP address and port number you entered is correct.
Error 2: Protocol error occurred. Error was returned from
destination server.
This error is displayed when a VPN client computer attempts to
establish a connection to a VPN server, but the VPN server returns an
error. When this error occurs you should check to make sure that the VPN
server software is functioning properly and that the hostname/IP address
and port number is correct. Also, you should update the VPN server
software and the VPN client software to the latest versions if they are
out of date.
Error 3: Connection was disconnected.
This error occurs when you are making an administrative connection to
the VPN server software or to the VPN client software via VPN Client
Manager and the network suddenly fails, the remote software abnormally
shuts down, the connection is dropped by the user or the system, or the
service is restarted. If you encounter this error, try reconnecting to
the server.
Error 4: Protocol error occurred.
This error occurs when a VPN client computer attempts to establish a
connection to a VPN server and an error occurs during the SSL
initialization stage. When this error occurs you should check to make
sure that the VPN server software is functioning properly and that the
hostname/IP address and port number is correct. This error often occurs
when port 443 on the VPN server computer is being used by some other
software and you are attempting to connect to PacketiX VPN Server on
that port. This error can also be caused by a proxy server or
transparent firewall.
Error 5: A client that is not PacketiX VPN software has connected to
the port.
This error occurs when software other than the VPN client software
connects to an open listener port on the VPN server computer. If this
error is being reported constantly in your log files then the listener
port provided by the VPN server could be getting port scanned.
Error 6: A user issued the cancel command.
This error occurs when a user (including the system administrator)
cancels a process while it is still running. This error is usually
always caused by the user and is normally nothing to worry about.
Error 7: The server denied the specified authentication method.
This error occurs when a VPN client computer requests an
authentication method that is not available on the VPN server computer.
Error 8: The specified Virtual HUB does not exist on the server.
This error occurs when a VPN client computer connects to a VPN server
computer and the specified Virtual HUB name does not exist on that VPN
server.
Error 9: User authentication failed.
This error occurs when a VPN client computer attempts to connect to a
VPN server computer's Virtual HUB, but the user could not be
authenticated. This is commonly due to a user error such as specifying
the wrong authentication method, inputting the wrong username or
password, providing the wrong certificate and private key, etc. Check
over all of your authentication information and try the connection
again.
Error 10: The specified Virtual HUB is currently stopped. Wait for a
while and then reconnect.
This error means that the specified Virtual HUB was set to "Offline"
status at the time when the connection was made. If the Virtual HUB is
not online then it can not receive incoming connection requests from VPN
client computers.
Error 11: The VPN session was deleted. It is possible that either
the administrator disconnected the session or the connection from the
client to the VPN Server was disconnected.
This can occur if an administrator forcibly closes the VPN session
while a VPN connection is established between a VPN client and VPN
server, or the VPN server computer and/or Virtual HUB were restarted and
the session times out. In most cases this problem can be solved by
re-establishing the VPN session.
Error 12: Access was denied.
This error occurs when a VPN client makes some request to a VPN
server, or a command is given to the VPN server from an administration
tool such as VPN Server Manager or vpncmd that is not allowed under the
client's access privileges. This error could also be displayed when a
user attempts to connect to a VPN but their account is disabled.
Error 13: Time-out occurred during VPN session communication. It is
possible the connection from the client to the VPN Server was
disconnected.
This error occurs if network conditions become unstable while a VPN
session is established between a VPN client and VPN server. In most
cases this problem can be solved by re-establishing the VPN session.
Error 14: Protocol number is invalid.
This error is generally never displayed.
Error 15: There are too many TCP/IP connections.
This error is generally never displayed.
Error 16: There are too many sessions connected to either the
destination server or Virtual HUB.
This error occurs when a VPN client attempts to connect to a VPN
server's Virtual HUB, but the maximum number of simultaneous sessions
allowed by that server or Virtual HUB are already connected so a new
session can not be created.
Error 17: Connection to proxy server failed.
This error occurs when a VPN client attempts to connect to a VPN
server via a HTTP or SOCKS proxy server, but a connection to the
specified proxy server could not be established. If you encounter this
error, check your proxy server settings and try again.
Error 18: An error occurred on the proxy server.
This error occurs when a VPN client attempts to connect to a VPN
server via a HTTP or SOCKS proxy server, but some error is encountered
after the connection is established to the designated proxy server. In
most cases this error occurs when attempting to make a VPN connection
through a proxy server that can not be used in such a way. If you
encounter this error, check your proxy server settings and try again.
Also, check with your proxy server's administrator to find out exactly
what type of error is occurring on the proxy server.
Error 19: User authentication failed on the proxy server.
This error occurs when a VPN client attempts to connect to a VPN
server via a HTTP or SOCKS proxy server, but the specified username and
password failed to be authorized by the proxy server.
Error 20: There are too many sessions by the same user.
This error is generally never displayed.
Error 21: A license error occurred on the VPN Server. Contact the
VPN Server's administrator.
This error occurs when the VPN server software running on the remote
VPN server computer is a trial version, an expired version, or a beta
version. Contact your VPN Server administrator.
Error 22: Cannot access the Virtual Network Adapter device driver.
Check the Virtual Network Adapter is installed and make sure it isn't
disabled.
This error can occur if the Virtual Network Adapter's device driver
is disabled by the operating system or the device driver file(s) are
corrupted, regardless of whether or not the Virtual Network Adapter
needs to be used.
Error 23: An internal error occurred.
This error does not occur very often, but when it does it is usually
because an invalid value was entered for some parameter by the user
during the configuration process.
Error 24: Access to either the smart card or USB hardware token
device failed.
This error occurs when an attempt is made to use a smart card, but it
can not be accessed. If you encounter this error make sure that you have
selected the proper smart card type, the card is connected to the card
reader, and that the card's drivers are installed and recognized by the
computer. Also, if the card reader needs to be initialized, ensure that
the initialization process has been completed.
Error 25: The PIN code is incorrect.
This error occurs when the PIN code you entered to use your smart
card is incorrect. Be careful, because if the PIN code is incorrectly
entered too many times you will be unable to use the card anymore for
security reasons.
Error 26: The specified certificate is not stored on either the
smart card or the USB hardware token device.
This error occurs when the certificate object specified by the user
does not exist on the smart card.
Error 27: The specified private key is not stored on either the
smart card or the USB hardware token device.
This error occurs when the private key object specified by the user
does not exist on the smart card.
Error 28: Write operation targeting either the smart card or USB
hardware token device failed.
This error occurs when an object is to be written to a smart card, but
the action fails. Ensure that the smart card has enough available free
space and has write access.
Error 29: Cannot find specified object.
This error occurs in many places. In most cases it is encountered
when an object name specified by the user is not registered on the
system.
Error 30: A Virtual Network Adapter with the specified name already
exists. Specify a different name.
This error occurs when the name of the Virtual Network Adapter
attempting to be registered already exists.
Error 31: Installation of the Virtual Network Adapter device driver
failed.
This error occurs when the device drivers fail to install when
creating a new Virtual Network Adapter. If you encounter this error, try
running the VPN client software process (vpnclient) in service mode or
with Administrator/root privileges.
Error 32: You cannot use the specified name for a Virtual Network
Adapter device name.
This error occurs when characters that can not be used when naming a
Virtual Network Adapter are contained in the name specified by the user.
You may only use alphanumeric characters and a few certain symbols when
naming Virtual Network Adapters.
Error 33: Not supported.
This error occurs when the function specified by the user is not
supported by the system. For example, this error would occur if a
command is made to create a Virtual Layer 3 Switch to PacketiX VPN
Bridge 2.0.
Error 34: A connection setting with the specified name already
exists.
This error occurs when the name specified when creating a new
connection configuration is the same as an already existing one.
Error 35: The specified connection setting is currently connected.
This error occurs when the user attempts to connect a connection
configuration that is already in the process of connecting or has
already successfully made a connection.
Error 36: The specified connection setting does not exist.
This error occurs when the specified connection configuration name
does not match any existing connection configurations.
Error 37: The specified connection setting is not connected.
This error occurs when the user attempts to close a VPN connection,
but the connection configuration is not connecting/connected.
Error 38: Invalid parameter.
This error can occur for many different reasons. In most cases it
occurs because an invalid value was entered for some parameter by the
user during the configuration process.
Error 39: Error occurred on smart card or USB hardware token.
This error occurs when an attempt is made to access the smart card,
but the hardware returns an error.
Error 40: Authentication of smart card or USB hardware token was
selected but the device to be used has not been selected. Select this
from the [Smart Card] menu of Connection Manager.
This error occurs when the smart card device to use for
authentication has not been selected.
Error 41: The specified Virtual Network Adapter is being used by at
least one connection setting. Either delete the connection setting that
is using this Virtual Network Adapter or change Virtual Network Adapter
that this connection setting is using.
This error occurs when an attempt is made to delete a Virtual Network
Adapter, but it is being used by a connection configuration. When
deleting Virtual Network Adapters, delete any connection configurations
that use them first.
Error 42: Cannot find the Virtual Network Adapter that the specified
connection setting is using. Make sure this Virtual Network Adapter
exists. Also make sure the Virtual Network Adapter device has not been
disabled. If you cannot resolve the problem, either change the Virtual
Network Adapter being used by this connection setting or create a new
Virtual Network Adapter with the same name.
This error can occur if the Virtual Network Adapter's device driver
is disabled by the operating system or the device driver file(s) are
corrupted, regardless of whether or not the Virtual Network Adapter
needs to be used.
Error 43: The Virtual Network Adapter used by the specified
connection setting is already being used by a different connection
setting. If there is a different connection setting that is using the
same Virtual Network Adapter, disconnect that connection setting.
This error occurs when a Virtual Network Adapter is configured to be
used by two or more connection configurations and is trying to be used
by another connection configuration while already in use.
Error 44: The Virtual Network Adapter being used by the specified
connection setting has been disabled. Before using this connection
setting, enable the Virtual Network Adapter and change its status so
that use is possible.
This error can occur if the Virtual Network Adapter's device driver
is disabled by the operating system or the device driver file(s) are
corrupted, regardless of whether or not the Virtual Network Adapter
needs to be used.
Error 45: The specified value is invalid.
This error can occur for many different reasons. In most cases it
occurs because an invalid value was entered for some parameter by the
user during the configuration process.
Error 46: The connection destination is not a cluster controller.
This error occurs when a command normally given to a cluster
controller is given to some other type of VPN server software.
Error 47: Making connection attempt.
This error means that the connection to the cluster controller is
currently attempting to make a connection.
Error 48: Connection to cluster controller failed.
This error occurs when a cluster member server can not connect to the
cluster controller.
Error 49: The cluster controller was unable to assign a new session
on a cluster.
This error occurs when a cluster controller fails to assign a VPN
session to a VPN Server on the cluster.
Error 50: Unable to manage the Virtual HUB of the cluster member
server.
This error occurs when trying to configure the options on a cluster
member server's Virtual HUB. In a clustered environment all Virtual HUB
administration and/or configuration must be done via the cluster
controller.
Error 51: The user password used to connect was blank and this
prevented connection from remote. If a blank password is used, it is
only possible to connect from the VPN Server's local computer localhost
(127.0.0.1).
This error occurs when no password is set on the server for the user
attempting to make a remote connection and therefore can not be
authorized for remote access. If you encounter this error first connect
to localhost on the computer running the server software and create a
password.
Error 52: Authorization is insufficient.
This error occurs when a user attempts to execute a command when they
do not have the required privileges to do so.
Error 53: Cannot find specified listener.
This error occurs when the specified listener port does not exist.
Error 54: The listener of the specified port number already exists.
This error occurs when the user attempts to create a listener port
that already exists.
Error 55: This is not a cluster member server.
This error occurs when a user attempts an operation intended for a
cluster member server on a machine other than a cluster member server.
Error 56: The specified encryption algorithm name is not supported.
This error occurs when the user specifies a SSL encryption algorithm
not supported by the VPN server.
Error 57: The Virtual HUB with the specified name already exists on
the server.
This error occurs when the user attempts to register a new Virtual
HUB with the same name as a Virtual HUB already existing on the server.
Error 58: There are too many registered Virtual HUBs. No more can be
registered. Delete the old Virtual HUBs.
This error occurs when the user attempts to register a new Virtual
HUB on a VPN server which already contains the maximum number of Virtual
HUBs that it can handle.
Error 59: The cascade connection with the specified name already
exists.
This error occurs when the user attempts to register a new cascade
connection with the same name as a cascade connection already existing
on the server.
Error 60: A cascade connection cannot be created on a server on a
cluster.
This error occurs when the user attempts to create a cascade
connection on a VPN server in a clustered environment.
Error 61: The specified cascade connection is offline.
This error occurs when the user specifies an offline cascade connection
where an online cascade connection is required.
Error 62: There are too many registered access lists.
This error occurs when there are a large number of access lists
registered to a Virtual HUB and no more can be created.
Error 63: There are too many registered users.
This error occurs when there are a large number of users registered
on a Virtual HUB and no more can be created.
Error 64: There are too many registered groups.
This error occurs when there are a large number of groups registered
on a Virtual HUB and no more can be created.
Error 65: The specified group does not exist.
This error occurs when the specified group name does not exist on the
Virtual HUB.
Error 66: The user with the specified name already exists on the
Virtual HUB.
This error occurs when the user tries to create a user with the same
name as one that already exists on the Virtual HUB.
Error 67: The group with the specified name already exists on the
Virtual HUB.
This error occurs when the user tries to create a group with the same
name as one that already exists on the Virtual HUB.
Error 68: A user with the specified name exists on the server but
the type of authentication is not password authentication. Unable to
change password.
This error occurs when attempting to use the VPN client software to
change the password for a user on the VPN server that is not
authenticated via standard password authentication.
Error 69: The user name or old password you entered is incorrect.
The password is case-sensitive.
This error occurs when attempting to use the VPN client software to
change the password for a user on the VPN server but the specified
username or password is incorrect.
Error 73: Unable to disconnect the cascade connection's session. To
delete the session, stop the cascade connection.
This error occurs when the user tries to mistakenly disconnect a
cascade connection session.
Error 74: The connection setting for connection with the VPN Server
is incomplete. First complete the connection setting for connection with
the VPN Server.
This error occurs when a process is invoked that requires a
connection configuration but there are none registered yet.
Error 75: Connection to the VPN Server has already started.
This error occurs when the connection process to a VPN server
computer has already been started.
Error 76: Not connected to the VPN Server.
This error occurs when the connection process to a VPN server
computer has not been started.
Error 77: The specified X509 certificate file does not hold a RSA
1024 bit or 2048 bit public key. PacketiX VPN software supports RSA 1024
bit or 2048 bit certificates.
This error occurs when the user specifies a X.509 certificate does
not have a bit length of 1024 or 2048.
Error 78: Unable to disconnect the SecureNAT's session. To delete
the session, stop the SecureNAT function.
This error occurs when the user tries to mistakenly disconnect a
SecureNAT session.
Error 79: Cannot enable the SecureNAT function in a clustering
environment.
This error occurs when the user attempts to enable SecureNAT on a VPN
server in a clustered environment.
Error 80: The SecureNAT function is not operating.
This error occurs when a process that requires SecureNAT is invoked
when SecureNAT is not active.
Error 81: This connection session to the VPN Server was disconnected
by the firewall device installed by the network administrator. Contact
the network administrator.
This error occurs when a VPN client attempts to connect to a VPN
server, but the connection is intercepted and blocked by a device
installed on the network. If you encounter this error, please consult
with your network administrator.
Error 82: Unable to disconnect the local bridge session. To delete
the session, stop the local bridge function.
This error occurs when the user tries to mistakenly disconnect a
local bridge session.
Error 83: The local bridge function is not operating.
This error occurs when a process that requires local bridging is
invoked when the local bridging functionality is not active.
Error 84: Local bridge cannot be used on the destination VPN Server.
Refer to online help or other documentation for the setting method when
using local bridge on the VPN Server you are using.
This error occurs when trying to use local bridging with the VPN
server software on an operating system that does not support local
bridging.
Error 85: Unable to trust the certificate provided by the
destination server. The setting to always verify the server certificate
is enabled in the connection settings. Either register a root
certificate that can be trusted or register a individual certificate.
This error occurs when the X.509 certificate from the remote VPN
server computer can not be verified.
Error 86: The product code of the destination server is incorrect.
It is not possible to connect from this client.
This error generally never occurs.
Error 87: The client and server versions do not match. Update the
software.
This error occurs when there is a considerable version difference
between the VPN server software and the VPN client software resulting in
protocol incompatibility. You should update the VPN server software and
the VPN client software to the latest versions if they are out of date.
Error 88: Failed to add capture device. It is possible that the same
capture device is already registered.
This error generally never occurs.
Error 89: Unable to connect to the destination server from this
client. Special client software is required.
This error generally never occurs.
Error 90: The specified capture device is not registered.
This error generally never occurs.
Error 91: Unable to disconnect the virtual Layer 3 switch session.
To delete the session, stop the virtual Layer 3 switch.
This error occurs when the user tries to mistakenly disconnect a
Virtual Layer 3 Switch session.
Error 92: A virtual Layer 3 switch with the specified name already
exists. Specify a different name.
This error occurs when the name of the Virtual Layer 3 Switch
attempting to be registered already exists.
Error 93: Cannot find a virtual Layer 3 switch with the specified
name.
This error occurs when the specified Virtual Layer 3 Switch has not
been registered.
Error 94: The specified name is invalid. Check if the name contains
characters that cannot be used.
This error occurs when the specified name contains characters that
cannot be used.
Error 95: Failed to add the virtual Layer 3 interface.
This error occurs when a Virtual Layer 3 Switch could not be added to
a VPN server computer.
Error 96: Failed to delete the virtual Layer 3 interface.
This error occurs when a Virtual Layer 3 Switch could not be deleted
from a VPN server computer.
Error 97: The virtual Layer 3 interface that is connecting to the
destination Virtual HUB of the specified virtual Layer 3 interface
already exists inside the virtual Layer 3 switch. No more than one
virtual Layer 3 interface that connects to the same Virtual HUB can be
defined in a single virtual Layer 3 switch.
This error occurs when the specified Virtual Layer 3 Interface's
remote Virtual HUB already has a Virtual Layer 3 Interface pointing to
it within the Virtual Layer 3 Switch.
Error 98: Failed to add routing table.
This error occurs when a new routing table fails to be added to a
layer 3 switch.
Error 99: Failed to delete routing table.
This error occurs when the specified routing table fails to be
deleted from a layer 3 switch.
Error 100: The specified routing table already exists.
This error occurs when the user attempts to add a new routing table
to a layer 3 switch which already contains the same exact routing table.
Error 101: The client clock and the server clock are not
synchronized with each other. Check the time settings.
This error occurs when the clocks on the VPN client computer and VPN
server computer are drastically different from each other.
Error 102: Unable to start this virtual Layer 3 switch. To start the
virtual Layer 3 switch, at least 1 virtual interface must be defined in
the virtual Layer 3 switch.
This error occurs when there are no Virtual Interfaces registered to
a Virtual Layer 3 Switch.
Error 103: Not enough client connection licenses for the destination
VPN Server. Contact the server administrator.
This error occurs when the number of VPN sessions equals or exceeds
the number of client connection licenses registered to the VPN server
computer and thus no more VPN sessions (client mode connections) can be
established.
Error 104: Not enough bridge connection licenses for the destination
VPN Server. Contact the server administrator.
This error occurs when the number of VPN sessions equals or exceeds
the number of bridge connection licenses registered to the VPN server
computer and thus no more VPN sessions (bridge or router mode
connections) can be established.
Error 105: Due to current technical difficulties, the destination
VPN Server is not receiving the connection. Either wait a while, or
contact the VPN Server administrator requesting that the server log file
be checked.
This error generally never occurs. If you do happen to encounter this
error, contact your VPN server administrator.
Error 106: The destination VPN Server's certificate has expired.
Contact the VPN Server's administrator.
This error occurs when the X.509 certificate from the VPN server
computer (server certificate) has expired.
Error 107: A connection was requested in monitoring mode. The
security policy for the user who is using the connection does include
permission for monitoring mode.
This error occurs when the user attempts to connect to a VPN server's
Virtual HUB from a VPN client in monitoring mode, but the user's
security policy does not allow them to make monitoring mode connections.
Error 108: A connection was requested in bridge / router mode. The
security policy for the user who is using the connection forbids both
bridge mode and router mode.
This error occurs when the user attempts to connect to a VPN server's
Virtual HUB from a VPN client in bridge/router mode, but the user's
security policy does not allow them to make bridge/router mode
connections.
Error 109: A connection from a client IP address was denied as a
result of the access control list setting of the VPN Server's Virtual
HUB.
This error occurs when the user attempts to connect to a VPN server's
Virtual HUB from a VPN client but their IP address is refused by the
Virtual HUB's access control list.
Error 110: There are too many items.
This error can occur in many different situations. Generally it occurs
when the user tries to add an object to a list that is already full and
cannot hold any more of that object.
Error 111: Memory is insufficient.
This error occurs when the computer does not have enough memory and
the required amount cannot be allocated.
Error 112: The specified object already exists.
This error can occur in many different situations. Generally it occurs
when the user attempts to add a new object to a list that already
contains the same exact object.
Error 113: A fatal error occurred. It is possible that the program
operation is unable to continue.
This error generally never occurs. If you do happen to encounter this
error, contact your VPN server administrator.
Error 114: The destination VPN Server has detected a software
license violation. Connection is refused. Contact the VPN Server's
administrator.
This error occurs when trying to connect to a VPN server that is
using a single VPN server software product license key on multiple
computers, which is a violation of the licensing contract.
Error 116: A software license violation was detected on the client
side. Connection is refused.
This error generally never occurs. If you do happen to encounter this
error, contact your system administrator.
Error 117: The command or file name is incorrect.
This error occurs when the user specifies an invalid command in
vpncmd.
Error 118: The license key is incorrect.
This error occurs when the user attempts to register an invalid
license key to the VPN server software. If you encounter this error,
contact your system administrator.
Error 119: A valid product license is not registered on the VPN
Server. Contact the VPN Server's administrator.
This error occurs when the VPN server computer cannot function as a
VPN server because it does not have a single valid product license
registered. If you encounter this error, contact your system
administrator.
Error 120: The product license required for the VPN Server to
operate as a cluster is not registered. Contact the VPN Server's
administrator.
This error occurs when the VPN server computer cannot function as a
VPN server with clustering capabilities because it does not have a
single valid product license registered that allows clustering. If you
encounter this error, contact your system administrator.
|