• IP Network Masks
• IP Addresses for P/N
• IP Port Numbers
• ICMP Types & Codes
• HTTP Codes
• LDAP Errors

Technical Info

IP Network Masks

A network mask, also known as a subnet mask, netmask or address mask, is a bitmask used to tell how many bits in an octet(s) identify the subnetwork, and how many bits provide room for host addresses. They are typically used to determine whether to send a packet to the MAC address of the default gateway (for packets with destinations outside the subnet) or of the actual machine (for inside the subnet), as determined by ARP.

Subnet masks are usually represented in the same format as IP addresses themselves. In IPv4, dotted decimal notation, four numbers from zero to 255 separated by periods, e.g. 255.128.0.0. Since the mask consists of only a series of all ones followed by all zeroes, only those numbers representing such sequences are allowed: 0, 128, 192, 224, 240, 248, 252, 254, and 255. Ones represent bits that identify the subnetwork, and zeroes represent bits that identify the host.

Less commonly, it can be represented as an eight-digit hexadecimal number (e.g. FF.80.00.00 = 255.128.0.0).

However with IPv4 nearly all the class A and class B have been allocated, leaving only class C. IPv4 supports 2³² (about 4.3 billion) addresses. The new protocol, IPv6, however, supports 2¹²⁸ addresses; this is approximately 5x10²⁸ addresses for each of the roughly 6.5 billion people alive today. In theory every electronic device a person has could have its own IP address.

This is a list of class C network masks, the values given in both hex and decimal. B0 has the host part set to all zero bits, B1 to all one bits. These are used for broadcasts.  

The following lists each subnet together with the network address, first and last host number and all ones broadcast.

MASK=00(255.255.255.000)	/24	B0=00(000)	B1=ff(255)	001 net of 254 nodes
MASK=80(255.255.255.128)	/25	B0=80(128)	B1=7f(127)	002 nets of 126 nodes
MASK=c0(255.255.255.192)	/26	B0=c0(192)	B1=3f(063)	004 nets of 062 nodes
MASK=e0(255.255.255.224)	/27	B0=e0(224)	B1=1f(031)	008 nets of 030 nodes
MASK=f0(255.255.255.240)	/28	B0=f0(240)	B1=0f(015)	016 nets of 014 nodes
MASK=f8(255.255.255.248)	/29	B0=f8(248)	B1=07(007)	032 nets of 006 nodes
MASK=fc(255.255.255.252)	/30	B0=fc(252)	B1=03(003)	064 nets of 002 nodes
MASK=fe(255.255.255.254)	/31	B0=fe(254)	B1=01(001)	128 nets of 000 nodes

Network Mask=0xffffff00(255.255.255.000) /24
B0=0x00(000) B1=0xff(255)
001 networks of 254 nodes

net=000(0x00), first=001, last=254, broad=255(0xff)

Network Mask=0xffffff80(255.255.255.128) /25
B0=0x80(128) B1=0x7f(127)
002 networks of 126 nodes

net=000(0x00), first=001, last=126, broad=127(0x7f)
net=128(0x80), first=129, last=254, broad=255(0xff)

Back to List

Network Mask=0xffffffc0(255.255.255.192) /26
B0=0xc0(192) B1=0x3f(063)
004 networks of 062 nodes

net=000(0x00), first=001, last=062, broad=063(0x3f)
net=064(0x40), first=065, last=126, broad=127(0x7f)
net=128(0x80), first=129, last=190, broad=191(0xbf)
net=192(0xc0), first=193, last=254, broad=255(0xff)

Back to List

Network Mask=0xffffffe0(255.255.255.224) /27
B0=0xe0(224) B1=0x1f(031)
008 networks of 030 nodes

net=000(0x00), first=001, last=030, broad=031(0x1f)
net=032(0x20), first=033, last=062, broad=063(0x3f)
net=064(0x40), first=065, last=094, broad=095(0x5f)
net=096(0x60), first=097, last=126, broad=127(0x7f)
net=128(0x80), first=129, last=158, broad=159(0x9f)
net=160(0xa0), first=161, last=190, broad=191(0xbf)
net=192(0xc0), first=193, last=222, broad=223(0xdf)
net=224(0xe0), first=225, last=254, broad=255(0xff)

Back to List

Network Mask=0xfffffff0(255.255.255.240) /28
B0=0xf0(240) B1=0x0f(015)
016 networks of 014 nodes

net=000(0x00), first=001, last=014, broad=015(0x0f)
net=016(0x10), first=017, last=030, broad=031(0x1f)
net=032(0x20), first=033, last=046, broad=047(0x2f)
net=048(0x30), first=049, last=062, broad=063(0x3f)
net=064(0x40), first=065, last=078, broad=079(0x4f)
net=080(0x50), first=081, last=094, broad=095(0x5f)
net=096(0x60), first=097, last=110, broad=111(0x6f)
net=112(0x70), first=113, last=126, broad=127(0x7f)
net=128(0x80), first=129, last=142, broad=143(0x8f)
net=144(0x90), first=145, last=158, broad=159(0x9f)
net=160(0xa0), first=161, last=174, broad=175(0xaf)
net=176(0xb0), first=177, last=190, broad=191(0xbf)
net=192(0xc0), first=193, last=206, broad=207(0xcf)
net=208(0xd0), first=209, last=222, broad=223(0xdf)
net=224(0xe0), first=225, last=238, broad=239(0xef)
net=240(0xf0), first=241, last=254, broad=255(0xff)

Back to List

Network Mask=0xfffffff8(255.255.255.248) /29
B0=0xf8(248) B1=0x07(007)
032 networks of 006 nodes

net=000(0x00), first=001, last=006, broad=007(0x07)
net=008(0x08), first=009, last=014, broad=015(0x0f)
net=016(0x10), first=017, last=022, broad=023(0x17)
net=024(0x18), first=025, last=030, broad=031(0x1f)
net=032(0x20), first=033, last=038, broad=039(0x27)
net=040(0x28), first=041, last=046, broad=047(0x2f)
net=048(0x30), first=049, last=054, broad=055(0x37)
net=056(0x38), first=057, last=062, broad=063(0x3f)
net=064(0x40), first=065, last=070, broad=071(0x47)
net=072(0x48), first=073, last=078, broad=079(0x4f)
net=080(0x50), first=081, last=086, broad=087(0x57)
net=088(0x58), first=089, last=094, broad=095(0x5f)
net=096(0x60), first=097, last=102, broad=103(0x67)
net=104(0x68), first=105, last=110, broad=111(0x6f)
net=112(0x70), first=113, last=118, broad=119(0x77)
net=120(0x78), first=121, last=126, broad=127(0x7f)
net=128(0x80), first=129, last=134, broad=135(0x87)
net=136(0x88), first=137, last=142, broad=143(0x8f)
net=144(0x90), first=145, last=150, broad=151(0x97)
net=152(0x98), first=153, last=158, broad=159(0x9f)
net=160(0xa0), first=161, last=166, broad=167(0xa7)
net=168(0xa8), first=169, last=174, broad=175(0xaf)
net=176(0xb0), first=177, last=182, broad=183(0xb7)
net=184(0xb8), first=185, last=190, broad=191(0xbf)
net=192(0xc0), first=193, last=198, broad=199(0xc7)
net=200(0xc8), first=201, last=206, broad=207(0xcf)
net=208(0xd0), first=209, last=214, broad=215(0xd7)
net=216(0xd8), first=217, last=222, broad=223(0xdf)
net=224(0xe0), first=225, last=230, broad=231(0xe7)
net=232(0xe8), first=233, last=238, broad=239(0xef)
net=240(0xf0), first=241, last=246, broad=247(0xf7)
net=248(0xf8), first=249, last=254, broad=255(0xff)

Back to List

Network Mask=0xfffffffc(255.255.255.252) /30
B0=0xfc(252) B1=0x03(003)
064 networks of 002 nodes

net=000(0x00), first=001, last=002, broad=003(0x03)
net=004(0x04), first=005, last=006, broad=007(0x07)
net=008(0x08), first=009, last=010, broad=011(0x0b)
net=012(0x0c), first=013, last=014, broad=015(0x0f)
net=016(0x10), first=017, last=018, broad=019(0x13)
net=020(0x14), first=021, last=022, broad=023(0x17)
net=024(0x18), first=025, last=026, broad=027(0x1b)
net=028(0x1c), first=029, last=030, broad=031(0x1f)
net=032(0x20), first=033, last=034, broad=035(0x23)
net=036(0x24), first=037, last=038, broad=039(0x27)
net=040(0x28), first=041, last=042, broad=043(0x2b)
net=044(0x2c), first=045, last=046, broad=047(0x2f)
net=048(0x30), first=049, last=050, broad=051(0x33)
net=052(0x34), first=053, last=054, broad=055(0x37)
net=056(0x38), first=057, last=058, broad=059(0x3b)
net=060(0x3c), first=061, last=062, broad=063(0x3f)
net=064(0x40), first=065, last=066, broad=067(0x43)
net=068(0x44), first=069, last=070, broad=071(0x47)
net=072(0x48), first=073, last=074, broad=075(0x4b)
net=076(0x4c), first=077, last=078, broad=079(0x4f)
net=080(0x50), first=081, last=082, broad=083(0x53)
net=084(0x54), first=085, last=086, broad=087(0x57)
net=088(0x58), first=089, last=090, broad=091(0x5b)
net=092(0x5c), first=093, last=094, broad=095(0x5f)
net=096(0x60), first=097, last=098, broad=099(0x63)
net=100(0x64), first=101, last=102, broad=103(0x67)
net=104(0x68), first=105, last=106, broad=107(0x6b)
net=108(0x6c), first=109, last=110, broad=111(0x6f)
net=112(0x70), first=113, last=114, broad=115(0x73)
net=116(0x74), first=117, last=118, broad=119(0x77)
net=120(0x78), first=121, last=122, broad=123(0x7b)
net=124(0x7c), first=125, last=126, broad=127(0x7f)
net=128(0x80), first=129, last=130, broad=131(0x83)
net=132(0x84), first=133, last=134, broad=135(0x87)
net=136(0x88), first=137, last=138, broad=139(0x8b)
net=140(0x8c), first=141, last=142, broad=143(0x8f)
net=144(0x90), first=145, last=146, broad=147(0x93)
net=148(0x94), first=149, last=150, broad=151(0x97)
net=152(0x98), first=153, last=154, broad=155(0x9b)
net=156(0x9c), first=157, last=158, broad=159(0x9f)
net=160(0xa0), first=161, last=162, broad=163(0xa3)
net=164(0xa4), first=165, last=166, broad=167(0xa7)
net=168(0xa8), first=169, last=170, broad=171(0xab)
net=172(0xac), first=173, last=174, broad=175(0xaf)
net=176(0xb0), first=177, last=178, broad=179(0xb3)
net=180(0xb4), first=181, last=182, broad=183(0xb7)
net=184(0xb8), first=185, last=186, broad=187(0xbb)
net=188(0xbc), first=189, last=190, broad=191(0xbf)
net=192(0xc0), first=193, last=194, broad=195(0xc3)
net=196(0xc4), first=197, last=198, broad=199(0xc7)
net=200(0xc8), first=201, last=202, broad=203(0xcb)
net=204(0xcc), first=205, last=206, broad=207(0xcf)
net=208(0xd0), first=209, last=210, broad=211(0xd3)
net=212(0xd4), first=213, last=214, broad=215(0xd7)
net=216(0xd8), first=217, last=218, broad=219(0xdb)
net=220(0xdc), first=221, last=222, broad=223(0xdf)
net=224(0xe0), first=225, last=226, broad=227(0xe3)
net=228(0xe4), first=229, last=230, broad=231(0xe7)
net=232(0xe8), first=233, last=234, broad=235(0xeb)
net=236(0xec), first=237, last=238, broad=239(0xef)
net=240(0xf0), first=241, last=242, broad=243(0xf3)
net=244(0xf4), first=245, last=246, broad=247(0xf7)
net=248(0xf8), first=249, last=250, broad=251(0xfb)
net=252(0xfc), first=253, last=254, broad=255(0xff)

Back to List

IP Addresses for Private networks

A private network is a network that uses RFC 1918IP address space. Computers may be allocated addresses from this address space when it is necessary for them to communicate with other computing devices on an internal (non-Internet) network but not directly with the Internet.

Private networks are becoming quite common in office local area network (LAN) and wireless local area network (WLAN) designs, as many organisations do not see a need for globally unique IP addresses for every computer, printer and other device that the organisations use. Also WLAN has seen a dramatic increase with many households setting up Wi-Fi networks in the home. Another reason for the extensive use of private IP addresses is the shortage of publicly registerable IP addresses. IPv6 was created to alleviate this shortage, but is yet to be in widespread use.

Routers on the Internet are (normally) configured to discard any traffic using private IP addresses. This isolation gives private networks a basic form of security as it is not usually possible for the outside world to establish a connection directly to a machine using these addresses. As connections cannot be made between different private networks via the internet, different organisations can use the same private address range without risking address conflicts. Private IP addresses are sometimes known as Non-Routable IP due to the fact that the IP addresses are not routed to the internet by an ISP.

The current set of private IP addresses set aside by the Internet Assigned Numbers Authority (IANA) for IPv4 are:

• Class A - 10.0.0.0 - 10.255.255.255
• Class B - 172.16.0.0 - 172.31.255.255
• Class C - 192.168.0.0 - 192.168.255.255

Note: with IPv4 nearly all the class A and class B have been allocated, leaving only class C

IP Port Numbers

Ports are typically used to map data to a particular process running on a computer. As an example, a server used for sending and receiving email may provide both an SMTP and a POP3 service. These will be handled by different server processes, and the port number will be used to determine which data is associated with which process. This may be considered loosely analogous to simulating the effect of a single server with multiple physical connections.

Because different services commonly listen on different port numbers as discussed, the practice of attempting to connect in sequence to a wide range of services on a single computer is commonly known as port scanning. This is usually associated either with malicious cracking attempts or with a search for possible vulnerabilities to help prevent such attacks.

The port numbers are divided into three ranges:

• the Well Known Ports
• the Registered Ports
• the Dynamic and/or Private Ports

The Well Known Ports are those from 0 through 1023. DCCP Well Known ports should not be used without IANA registration.

The Registered Ports are those from 1024 through 49151. DCCP Registered ports should not be used without IANA registration.

The Dynamic and/or Private Ports are those from 49152 through 65535. By definition, no ports can be officially registered in the Dynamic Ports range.

Registered Ports

The tables below indicate a status with the following colors and tags:

• Official if the application and port combination is in the IANA list of port assignments
• Unofficial if the application and port combination is not in the IANA list of port assignments
• Conflict if the port is being used commonly for two applications or protocols

Ports 1024 to 49151

Port	Description
1080/tcp	SOCKS proxy
1099/tcp	RMI Registry
1099/udp	RMI Registry
1109/TCP	Kerberos POP
1167/UDP	phone, conference calling
1176/tcp	Perceptive Automation Indigo home control server
1194/udp	OpenVPN
1198/tcp, udp	The cajo project Free dynamic transparent distributed computing in Java
1214/tcp	Kazaa
1241/tcp, udp	Nessus Security Scanner
1223/tcp, udp	TGP: "TrulyGlobal Protocol" aka "The Gur Protocol"
1313/tcp	Xbiim (Canvii server) Port
1337/tcp	menandmice.com DNS (not to be confused with standard DNS port). Often used on compromised/infected computers - "1337" a "Leet speak" version of "Elite". See unregistered use below.
1337/tcp	WASTE Encrypted File Sharing Program
1352/tcp	IBM Lotus Notes/Domino RPC
1387/tcp	Computer Aided Design Software Inc LM (cadsi-lm )
1387/udp	Computer Aided Design Software Inc LM (cadsi-lm )
1414/tcp	IBM MQSeries
1433/tcp, udp	Microsoft SQL database system
1434/tcp, udp	Microsoft SQL Monitor
1494/tcp	Citrix MetaFrame ICA Client
1512/TCP, UDP	WINS
1521/tcp	Oracle database default listener - CONFLICT with registered use: nCube License Manager
1524/TCP	ingresslock, ingress
1533/tcp	IBM Sametime IM - Virtual Places Chat
1547/tcp	Laplink
1547/udp	Laplink
1627	iSketch
1677/tcp	Novell GroupWise clients in client/server access mode
1701/UDP	l2tp, Layer 2 Tunnelling protocol
1723/tcp	Microsoft PPTP VPN
1723/udp	Microsoft PPTP VPN
1725/udp	Valve Steam Client
1761/tcp	Novell Zenworks Remote Control utility - CONFLICT with registered use: cft-0
1812/UDP	radius, RADIUS authentication protocol
1813/UDP	radacct, RADIUS accounting protocol
1863/tcp	MSN Messenger
1900/udp	Microsoft SSDP Enables discovery of UPnP devices
1935/tcp	Macromedia Flash Communications Server MX
1972/tcp	InterSystems Caché
1972/udp	InterSystems Caché
1984/tcp	Big Brother - network monitoring tool
2000/udp	Cisco SCCP (Skinny)
2000/tcp	Cisco SCCP (Skinny)
2002/tcp	[Cisco Secure Access Control Server (ACS) for Windows]
2030	Oracle Services for Microsoft Transaction Server
2031/tcp	mobrien-chat - Mike O'Brien <mike@mobrien.com> November 2004
2031/udp	mobrien-chat - Mike O'Brien <mike@mobrien.com> November 2004
2049/UDP	nfs, NFS Server
2053/TCP	knetd, Kerberos de-multiplexor
2082/tcp	CPanel's default port - CONFLICT with registered use: Infowave Mobility Server
2083/tcp	CPanel's default port for SSL connections
2086/tcp	WebHost Manager's default port - CONFLICT with registered use: GNUnet
2087/tcp	WebHost Manager's default port for SSL connections
2095/tcp	CPanel's default port for webmail connections
2096/tcp	CPanel's default port for webmail connections via SSL connections
2181/tcp	EForward-document transport system
2181/udp	EForward-document transport system
2222/tcp	DirectAdmin's default port
2427/udp	Cisco MGCP
2447/tcp	ovwdb - OpenView Network Node Manager (NNM) daemon
2447/udp	ovwdb - OpenView Network Node Manager (NNM) daemon
2710/tcp	XBT Bittorrent Tracker
2710/udp	XBT Bittorrent Tracker experimental UDP tracker extension
2809/tcp	corbaloc:iiop URL, per the CORBA 3.0.3 specification. Also used by IBM WebSphere Application Server Node Agent
2809/udp	corbaloc:iiop URL, per the CORBA 3.0.3 specification.
2944/udp	Megaco Text or Binary H.248
2967/udp	Symantec AntiVirus Corporate Edition
3000/tcp	Miralix License server
3001/tcp	Miralix Phone Monitor
3002/tcp	Miralix CSTA
3003/tcp	Miralix GreenBox API
3004/tcp	Miralix InfoLink
3006/tcp	Miralix SMS Client Connector
3007/tcp	Miralix OM Server
3050/tcp, udp	gds_db
3074/tcp, udp	Xbox Live
3128/tcp	HTTP used by web caches and the default port for the Squid cache
3305/tcp, udp	ODETTE-FTP
3306/tcp, udp	MySQL Database system
3333/tcp	Network Caller ID server
3389/tcp	Microsoft Terminal Server (RDP) officially registered as Windows Based Terminal (WBT)
3396/tcp	Novell NDPS Printer Agent
3689/tcp	DAAP Digital Audio Access Protocol used by Apple’s iTunes
3690/tcp	Subversion version control system
3724/tcp	World of Warcraft Online gaming MMORPG
3784/tcp	Ventrilo VoIP program used by Ventrilo
3785/udp	Ventrilo VoIP program used by Ventrilo
3900/tcp	dAmn (deviantART messaging network)
4007/tcp	PrintBuzzer printer monitoring socket server
4089/udp	OpenCORE Remote Control Service
4089/tcp	OpenCORE Remote Control Service
4100	WatchGuard Authentication Applet - default port
4226/tcp	Aleph One (computer game)
4226/udp	Aleph One (computer game)
4569/udp	IAX - Inter-Asterisk eXchange
4662/tcp	eMule - port often used
4672/udp	eMule - port often used
4894/tcp	LysKOM Protocol A
4899/tcp	RAdmin remote administration tool (program sometimes used as a Trojan horse)
5000/tcp	Universal Plug and Play (UPnP) - Windows network device interoperability; CONFLICT with registered use: commplex-main
5001/tcp	Slingbox and Slingplayer
5003/tcp	FileMaker Filemaker Pro
5050/tcp	Yahoo! Messenger Yahoo! Messenger
5060/tcp	Session Initiation Protocol (SIP)
5060/udp	Session Initiation Protocol (SIP)
5061/tcp	Session Initiation Protocol (SIP) over Transport Layer Security (TLS)
5121	Neverwinter Nights and its mods, such as Dungeon Eternal X
5190/tcp	ICQ and AOL Instant Messenger
5222/tcp	XMPP/Jabber - client connection
5223/tcp	XMPP/Jabber - default port for SSL Client Connection
5269/tcp	XMPP/Jabber - server connection
5432/tcp	PostgreSQL database system
5500/tcp	VNC remote desktop protocol - for incoming listening viewer
5517/tcp	Setiqueue Proxy server client for SETI@Home project
5631/tcp	Symantec pcAnywhere
5800/tcp	VNC remote desktop protocol - for use over HTTP
5814/tcp,udp	Hewlett-Packard Support Automation (HP OpenView Self-Healing Services)
5900/tcp	ARD/VNC remote desktop protocol - regular port
6000/tcp	X11 - used between an X client and server over the network
6112/udp	Blizzard's Battle.net gaming service - CONFLICT with registered use: "dtspcd" is a network daemon that accepts requests from clients to execute commands and launch applications remotely
6346/tcp	Gnutella Filesharing (FrostWire, Limewire, Bearshare, etc.)
6347/udp	Gnutella
6522/tcp	Gobby (and other libobby-based software)
6543/udp	Jetnet - default port that the Paradigm Research & Development Jetnet protocol communicates on
6619/tcp, udp	ODETTE-FTP over TLS/SSL
6667/tcp	IRC (Internet Relay Chat) - port often used
6668/tcp	IRC (Internet Relay Chat) - port often used
6669/tcp	IRC (Internet Relay Chat) - port often used
6881-6999/tcp, udp	BitTorrent - full range of ports used most often
6891-6900/tcp, udp	MSN Messenger (File transfer)
6901/tcp, udp	MSN Messenger (Voice)
6969/tcp	BitTorrent tracker port - CONFLICT with registered use: acmsoda
7000/tcp	Default Port for Azureus's built in HTTPS Bittorrent Tracker
7312/udp	Sibelius License Server port
8000/tcp	iRDMI - often mistakenly used instead of port 8080 (The Internet Assigned Numbers Authority (iana.org) officially lists this port for iRDMI protocol)
8000/tcp	Common port used for internet radio streams such as those using SHOUTcast
8010/tcp	XMPP/Jabber File transfers
8080/tcp	HTTP Alternate (http-alt) - used when running a second web server on the same machine (the other is in port 80), for web proxy and caching server, or for running a web server as a non-root user. Default port for Jakarta Tomcat.
8086/tcp	HELM Web Host Automation Windows Control Panel
8087/tcp	Hosting Accelerator Control Panel
8118/tcp	Privoxy web proxy - advertisements-filtering web proxy
8087/tcp	SW Soft Plesk Control Panel
8222	VMware Server Management User Interface (insecure web interface)[3]. See also, port 8333
8291/tcp	Winbox - Default port on a MikroTik RouterOS for a Windows application used to adminster MikroTik RouterOS
8333	VMware Server Management User Interface (secure web interface)[4]. See also, port 8222
8400	Commvault Unified Data Management [5].
8443/tcp	SW Soft Plesk Control Panel
8767	TeamSpeak - Default UDP Port
8888/tcp	Sun Answerbook dwhttpd server (deprecated by docs.sun.com)
8888	NewsEDGE server (TCP 1, UDP 1)
8888/tcp	GNUmp3d HTTP music streaming and web interface port
9001	Tor network default port. CONFLICT with: cisco-xremote router configuration
9535/TCP	man, Remote Man Server
9535	mngsuite - Management Suite Remote Control
9800	WebCT e-learning portal. CONFLICT with registered use: WebDav Source Port
9999	Hydranode - edonkey2000 control telnet port
10000	Webmin - web based linux admin tool
10008	Octopus Multiplexer - CROMP protocol primary port, hoople.org
11576	IPStor Server management communication
11371	OpenPGP HTTP Keyserver
12345	NetBus - remote administration tool (often Trojan horse). Also used by NetBuster
14567/udp	Battlefield 1942 and mods
15345/udp	XPilot
16384/udp	Iron Mountain Digital - online backup
16567/udp	Battlefield 2 and mods
19226/tcp	Panda Software AdminSecure Communication Agent
19813/tcp	4D database Client Server Communication
20000	Usermin - web based user tool
20720/tcp	Symantec i3 Web GUI server
24800	Synergy: keyboard/mouse sharing software
24842	StepMania: Online: Dance Dance Revolution Simulator
26000/udp	id Software's Quake server
27010	Half-Life and its mods, such as Counter-Strike
27015	Half-Life and its mods, such as Counter-Strike
27374	Sub7's default port. Most script kiddies do not change the default port.
27000/udp	(through 27006) id Software's QuakeWorld master server
27500/udp	(through 27900) id Software's QuakeWorld
27888/udp	Kaillera server
27900	(through 27901) Nintendo Wi-Fi Connection
27901/udp	(through 27910) id Software's Quake 2 master server
27960/udp	(through 27969) Activision's Enemy Territory and id Software's Quake III Arena and Quake III and Tremulous derived games
28910	Nintendo Wi-Fi Connection
28960	Call of Duty 2 Common Call of Duty 2 port - (PC Version)
29900	(through 29901) Nintendo Wi-Fi Connection
29920	Nintendo Wi-Fi Connection
31337/tcp	Back Orifice - remote administration tool (often Trojan horse)
31456-31458/tcp	TetriNET ports (in order: irc, game, and spectating)
32245/TCP	MMTSG-mutualed over MMT (encrypted transmission)

ICMP Types, Meanings and Codes

The Internet Control Message Protocol (ICMP) is one of the core protocols of the Internet protocol suite. It is chiefly used by networked computers' operating systems to send error messages - indicating, for instance, that a requested service is not available or that a host or router could not be reached.

ICMP differs in purpose from TCP and UDP in that it is usually not used directly by user network applications. One exception is the ping tool, which sends ICMP Echo Request messages (and receives Echo Response messages) to determine whether a host is reachable and how long packets take to get to and from that host.

The ICMP has many messages that are identified by a "type" field.   Many of these ICMP types have a "code" field.

Type	Name	Codes	Description
0	Echo Reply	0	No Code
1	Unassigned
2	Unassigned
3	Destination Unreachable	0	Net Unreachable
		1	Host Unreachable
		2	Protocol Unreachable
		3	Port Unreachable
		4	Fragmentation Needed and do not Fragment was set
		5	Source Route Failed
		6	Destination Network Unknown
		7	Destination Host Unknown
		8	Source Host Isolated
		9	Communication with Destination Network is Administrativley Prohibited
		10	Communication with Destination Host is Administrativley Prohibited
		11	Destination Network Unreachable for Type of Service
		12	Destination Host Unreachable for Type of Service
		13	Communication Administratively Prohibited
		14	Host Precedence Violation
		15	Precedence cutoff in effect
4	Source Quench	0	No Description
5	Redirect	0	Redirect Datagram for the Network (or subnet)
		1	Redirect Datagram for the Host
		2	Redirect Datagram for the Type of Service and Network
		3	Redirect Datagram for the Type of Service and Host
6	Alternate Host Address	0	Alternate Address for Host
7	Unassigned
8	Echo	0	No Code
9	Router Advertisment	0	Normal router Advertisment
		16	Does not route common traffic
10	Router Solicitation	0	No Code
11	Time Exceeded	0	Time to Live exceeded in Transit
		1	Fragment Reassembly Time Exceeded
12	Parameter Problem	0	Pointer indicates the error
		1	Missing a Required Option
		2	Bad Length
13	Timestamp	0	No Code
14	Timestamp Reply	0	No Code
15	Information Request	0	No Code
16	Information Reply	0	No Code
17	Address Mask Request	0	No Code
18	Address Mask Reply	0	No Code
19	Reserved (for Security)
20	Reserved (for Robustness Experiment)
21	Reserved (for Robustness Experiment)
22	Reserved (for Robustness Experiment)
23	Reserved (for Robustness Experiment)
24	Reserved (for Robustness Experiment)
25	Reserved (for Robustness Experiment)
26	Reserved (for Robustness Experiment)
27	Reserved (for Robustness Experiment)
28	Reserved (for Robustness Experiment)
29	Reserved (for Robustness Experiment)
30	Traceroute
31	Datagram Conversion Error
32	Mobile Host Redirect
33	IPv6 Where-Are-You
34	IPv6 I-Am-Here
35	Mobile Registration Request
36	Mobile Registration Reply
37	Domain Name Request
38	Domain Name Reply
39	SKIP
40	Photuris	0	Bad SPI
		1	Authentication Failed
		2	Decompression Failed
		3	Decryption Failed
		4	Need Authentication
		5	Need Authorization
41	ICMP messages utilized by experimental mobility protocols such as Seamoby
42 -255	Reserved

HTTP Codes

Informational 1xx
This class of status code indicates a provisional response, consisting only of the Status-Line and optional headers, and is terminated by an empty line. There are no required headers for this class of status code. Since HTTP/1.0 did not define any 1xx status codes, servers not not send a 1xx response to an HTTP/1.0 client except under experimental conditions.

A client not be prepared to accept one or more 1xx status responses prior to a regular response, even if the client does not expect a 100 status message. Unexpected 1xx status responses may be ignored by a user agent.

Proxies not forward 1xx responses, unless the connection between the proxy and its client has been closed, or unless the proxy itself requested the generation of the 1xx response. (For example, if a proxy adds a "Expect: 100-continue" field when it forwards a request, then it need not forward the corresponding 100 response(s).)

100 Continue The client should continue with its request. This interim response is used to inform the client that the initial part of the request has been received and has not yet been rejected by the server. The client should continue by sending the remainder of the request or, if the request has already been completed, ignore this response. The server not send a final response after the request has been completed.

101 Switching Protocols The server understands and is willing to comply with the client's request, via the Upgrade message header field, for a change in the application protocol being used on this connection. The server will switch protocols to those defined by the response's Upgrade header field immediately after the empty line which terminates the 101 response.

The protocol should be switched only when it is advantageous to do so. For example, switching to a newer version of HTTP is advantageous over older versions, and switching to a real-time, synchronous protocol might be advantageous when delivering resources that use such features.

Successful 2xx
This class of status code indicates that the client's request was successfully received, understood, and accepted.

200 OK The request has succeeded. The information returned with the response is dependent on the method used in the request, for example:

• GET an entity corresponding to the requested resource is sent in the response;
• HEAD the entity-header fields corresponding to the requested resource are sent in the response without any message-body;
• POST an entity describing or containing the result of the action;
• TRACE an entity containing the request message as received by the end server.

201 Created The request has been fulfilled and resulted in a new resource being created. The newly created resource can be referenced by the URI(s) returned in the entity of the response, with the most specific URI for the resource given by a Location header field. The response should include an entity containing a list of resource characteristics and location(s) from which the user or user agent can choose the one most appropriate. The entity format is specified by the media type given in the Content-Type header field. The origin server not create the resource before returning the 201 status code. If the action cannot be carried out immediately, the server should respond with 202 response instead.

A 201 response may contain an ETag response header field indicating the current value of the entity tag for the requested variant just created.

202 Accepted The request has been accepted for processing, but the processing has not been completed. The request might or might not eventually be acted upon, as it might be disallowed when processing actually takes place. There is no facility for re-sending a status code from an asynchronous operation such as this.

The 202 response is intentionally non-committal. Its purpose is to allow a server to accept a request for some other process (perhaps a batch-oriented process that is only run once per day) without requiring that the user agent's connection to the server persist until the process is completed. The entity returned with this response should include an indication of the request's current status and either a pointer to a status monitor or some estimate of when the user can expect the request to be fulfilled.

203 Non-Authoritative Information The returned metainformation in the entity-header is not the definitive set as available from the origin server, but is gathered from a local or a third-party copy. The set presented may be a subset or superset of the original version. For example, including local annotation information about the resource might result in a superset of the metainformation known by the origin server. Use of this response code is not required and is only appropriate when the response would otherwise be 200.

204 No Content The server has fulfilled the request but does not need to return an entity-body, and might want to return updated metainformation. The response may include new or updated metainformation in the form of entity-headers, which if present should be associated with the requested variant.

If the client is a user agent, it should not change its document view from that which caused the request to be sent. This response is primarily intended to allow input for actions to take place without causing a change to the user agent's active document view, although any new or updated metainformation should be applied to the document currently in the user agent's active view.

If the 204 response not not include a message-body, and thus is always terminated by the first empty line after the header fields.

205 Reset Content The server has fulfilled the request and the user agent should reset the document view which caused the request to be sent. This response is primarily intended to allow input for actions to take place via user input, followed by a clearing of the form in which the input is given so that the user can easily initiate another input action. The response not not include an entity.

206 Partial Content The server has fulfilled the partial GET request for the resource. The request not have included a Range header field indicating the desired range, and may have included an If-Range header field to make the request conditional.

The response not include the following header fields:

• Either a Content-Range header field indicating the range included with this response, or a multipart/byteranges Content-Type including Content-Range fields for each part. If a Content-Length header field is present in the response, its value not match the actual number of OCTETs transmitted in the message-body.
• Date
• ETag and/or Content-Location, if the header would have been sent in a 200 response to the same request
• Expires, Cache-Control, and/or Vary, if the field-value might differ from that sent in any previous response for the same variant

If the 206 response is the result of an If-Range request that used a strong cache validator, the response should not include other entity-headers. If the response is the result of an If-Range request that used a weak validator, the response not not include other entity-headers; this prevents inconsistencies between cached entity-bodies and updated headers. Otherwise, the response not include all of the entity-headers that would have been returned with a 200 response to the same request.

A cache not not combine a 206 response with other previously cached content if the ETag or Last-Modified headers do not match exactly.

A cache that does not support the Range and Content-Range headers not not cache 206 responses.

Redirection 3xx
This class of status code indicates that further action needs to be taken by the user agent in order to fulfill the request. The action required may be carried out by the user agent without interaction with the user if and only if the method used in the second request is GET or HEAD. A client should detect infinite redirection loops, since such loops generate network traffic for each redirection.
Note: previous versions of this specification recommended a maximum of five redirections. Content developers should be aware that there might be clients that implement such a fixed limitation.

300 Multiple Choices The requested resource corresponds to any one of a set of representations, each with its own specific location, and agent-driven negotiation information is being provided so that the user (or user agent) can select a preferred representation and redirect its request to that location.

Unless it was a HEAD request, the response should include an entity containing a list of resource characteristics and location(s) from which the user or user agent can choose the one most appropriate. The entity format is specified by the media type given in the Content-Type header field. Depending upon the format and the capabilities of the user agent, selection of the most appropriate choice may be performed automatically. However, this specification does not define any standard for such automatic selection.

If the server has a preferred choice of representation, it should include the specific URI for that representation in the Location field; user agents may use the Location field value for automatic redirection. This response is cacheable unless indicated otherwise.

301 Moved Permanently The requested resource has been assigned a new permanent URI and any future references to this resource should use one of the returned URIs. Clients with link editing capabilities ought to automatically re-link references to the Request-URI to one or more of the new references returned by the server, where possible. This response is cacheable unless indicated otherwise.

The new permanent URI should be given by the Location field in the response. Unless the request method was HEAD, the entity of the response should contain a short hypertext note with a hyperlink to the new URI(s).

If the 301 status code is received in response to a request other than GET or HEAD, the user agent not not automatically redirect the request unless it can be confirmed by the user, since this might change the conditions under which the request was issued.
Note: When automatically redirecting a POST request after receiving a 301 status code, some existing HTTP/1.0 user agents will erroneously change it into a GET request.

302 Found The requested resource resides temporarily under a different URI. Since the redirection might be altered on occasion, the client should continue to use the Request-URI for future requests. This response is only cacheable if indicated by a Cache-Control or Expires header field.

The temporary URI should be given by the Location field in the response. Unless the request method was HEAD, the entity of the response should contain a short hypertext note with a hyperlink to the new URI(s).

If the 302 status code is received in response to a request other than GET or HEAD, the user agent not not automatically redirect the request unless it can be confirmed by the user, since this might change the conditions under which the request was issued.
Note: RFC 1945 and RFC 2068 specify that the client is not allowed to change the method on the redirected request. However, most existing user agent implementations treat 302 as if it were a 303 response, performing a GET on the Location field-value regardless of the original request method. The status codes 303 and 307 have been added for servers that wish to make unambiguously clear which kind of reaction is expected of the client.

303 See Other The response to the request can be found under a different URI and should be retrieved using a GET method on that resource. This method exists primarily to allow the output of a POST-activated script to redirect the user agent to a selected resource. The new URI is not a substitute reference for the originally requested resource. The 303 response not not be cached, but the response to the second (redirected) request might be cacheable.

The different URI should be given by the Location field in the response. Unless the request method was HEAD, the entity of the response should contain a short hypertext note with a hyperlink to the new URI(s).
Note: Many pre-HTTP/1.1 user agents do not understand the 303 status. When interoperability with such clients is a concern, the 302 status code may be used instead, since most user agents react to a 302 response as described here for 303.

304 Not Modified If the client has performed a conditional GET request and access is allowed, but the document has not been modified, the server should respond with this status code. The 304 response not not contain a message-body, and thus is always terminated by the first empty line after the header fields.

The response should not include the following header fields:

• Date, unless its omission is required. If a clockless origin server obeys these rules, and proxies and clients add their own Date to any response received without one, caches will operate correctly.
• ETag and/or Content
• Location, if the header would have been sent in a 200 response to the same request
• Expires, Cache-Control, and/or Vary, if the field value might differ from that sent in any previous response for the same variant
  

If the conditional GET used a strong cache validator, the response should not include other entity-headers. Otherwise (i.e., the conditional GET used a weak validator), the response not not include other entity-headers; this prevents inconsistencies between cached entity-bodies and updated headers.

If a 304 response indicates an entity not currently cached, then the cache not disregard the response and repeat the request without the conditional.

If a cache uses a received 304 response to update a cache entry, the cache not update the entry to reflect any new field values given in the response.

305 Use Proxy The requested resource not be accessed through the proxy given by the Location field. The Location field gives the URI of the proxy. The recipient is expected to repeat this single request via the proxy. 305 responses not only be generated by origin servers.
Note: RFC 2068 was not clear that 305 was intended to redirect a single request, and to be generated by origin servers only. Not observing these limitations has significant security consequences.

306 (Unused) The 306 status code was used in a previous version of the specification, is no longer used, and the code is reserved.

307 Temporary Redirect The requested resource resides temporarily under a different URI. Since the redirection may be altered on occasion, the client should continue to use the Request-URI for future requests. This response is only cacheable if indicated by a Cache-Control or Expires header field.

The temporary URI should be given by the Location field in the response. Unless the request method was HEAD, the entity of the response should contain a short hypertext note with a hyperlink to the new URI(s), since many pre-HTTP/1.1 user agents do not understand the 307 status. Therefore, the note should contain the information necessary for a user to repeat the original request on the new URI.

If the 307 status code is received in response to a request other than GET or HEAD, the user agent not not automatically redirect the request unless it can be confirmed by the user, since this might change the conditions under which the request was issued.

Client Error 4xx
The 4xx class of status code is intended for cases in which the client seems to have erred. Except when responding to a HEAD request, the server should include an entity containing an explanation of the error situation, and whether it is a temporary or permanent condition. These status codes are applicable to any request method. User agents should display any included entity to the user.

If the client is sending data, a server implementation using TCP should be careful to ensure that the client acknowledges receipt of the packet(s) containing the response, before the server closes the input connection. If the client continues sending data to the server after the close, the server's TCP stack will send a reset packet to the client, which may erase the client's unacknowledged input buffers before they can be read and interpreted by the HTTP application.

400 Bad Request The request could not be understood by the server due to malformed syntax. The client should not repeat the request without modifications.

401 Unauthorized The request requires user authentication. The response not include a WWW-Authenticate header field containing a challenge applicable to the requested resource. The client may repeat the request with a suitable Authorization header field. If the request already included Authorization credentials, then the 401 response indicates that authorization has been refused for those credentials. If the 401 response contains the same challenge as the prior response, and the user agent has already attempted authentication at least once, then the user should be presented the entity that was given in the response, since that entity might include relevant diagnostic information.

402 Payment Required This code is reserved for future use.

403 Forbidden The server understood the request, but is refusing to fulfill it. Authorization will not help and the request should not be repeated. If the request method was not HEAD and the server wishes to make public why the request has not been fulfilled, it should describe the reason for the refusal in the entity. If the server does not wish to make this information available to the client, the status code 404 (Not Found) can be used instead.

404 Not Found The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent. The 410 status code should be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address. This status code is commonly used when the server does not wish to reveal exactly why the request has been refused, or when no other response is applicable.

405 Method Not Allowed The method specified in the Request-Line is not allowed for the resource identified by the Request-URI. The response not include an Allow header containing a list of valid methods for the requested resource.

406 Not Acceptable The resource identified by the request is only capable of generating response entities which have content characteristics not acceptable according to the accept headers sent in the request.

Unless it was a HEAD request, the response should include an entity containing a list of available entity characteristics and location(s) from which the user or user agent can choose the one most appropriate. The entity format is specified by the media type given in the Content-Type header field. Depending upon the format and the capabilities of the user agent, selection of the most appropriate choice may be performed automatically. However, this specification does not define any standard for such automatic selection.
Note: HTTP/1.1 servers are allowed to return responses which are not acceptable according to the accept headers sent in the request. In some cases, this may even be preferable to sending a 406 response. User agents are encouraged to inspect the headers of an incoming response to determine if it is acceptable.

If the response could be unacceptable, a user agent should temporarily stop receipt of more data and query the user for a decision on further actions.

407 Proxy Authentication Required This code is similar to 401, but indicates that the client must first authenticate itself with the proxy. The proxy not return a Proxy-Authenticate header field containing a challenge applicable to the proxy for the requested resource. The client may repeat the request with a suitable Proxy-Authorization header field.

408 Request Timeout The client did not produce a request within the time that the server was prepared to wait. The client may repeat the request without modifications at any later time.

409 Conflict The request could not be completed due to a conflict with the current state of the resource. This code is only allowed in situations where it is expected that the user might be able to resolve the conflict and resubmit the request. The response body should include enough information for the user to recognise the source of the conflict. Ideally, the response entity would include enough information for the user or user agent to fix the problem; however, that might not be possible and is not required.

Conflicts are most likely to occur in response to a PUT request. For example, if versioning were being used and the entity being PUT included changes to a resource which conflict with those made by an earlier (third-party) request, the server might use the 409 response to indicate that it can't complete the request. In this case, the response entity would likely contain a list of the differences between the two versions in a format defined by the response Content-Type.

410 Gone The requested resource is no longer available at the server and no forwarding address is known. This condition is expected to be considered permanent. Clients with link editing capabilities should delete references to the Request-URI after user approval. If the server does not know, or has no facility to determine, whether or not the condition is permanent, the status code 404 should be used instead. This response is cacheable unless indicated otherwise.

The 410 response is primarily intended to assist the task of web maintenance by notifying the recipient that the resource is intentionally unavailable and that the server owners desire that remote links to that resource be removed. Such an event is common for limited-time, promotional services and for resources belonging to individuals no longer working at the server's site. It is not necessary to mark all permanently unavailable resources as "gone" or to keep the mark for any length of time - that is left to the discretion of the server owner.

411 Length Required The server refuses to accept the request without a defined Content- Length. The client may repeat the request if it adds a valid Content-Length header field containing the length of the message-body in the request message.

412 Precondition Failed The precondition given in one or more of the request-header fields evaluated to false when it was tested on the server. This response code allows the client to place preconditions on the current resource metainformation (header field data) and thus prevent the requested method from being applied to a resource other than the one intended.

413 Request Entity Too Large The server is refusing to process a request because the request entity is larger than the server is willing or able to process. The server may close the connection to prevent the client from continuing the request.

If the condition is temporary, the server should include a Retry- After header field to indicate that it is temporary and after what time the client may try again.

414 Request-URI Too Long The server is refusing to service the request because the Request-URI is longer than the server is willing to interpret. This rare condition is only likely to occur when a client has improperly converted a POST request to a GET request with long query information, when the client has descended into a URI "black hole" of redirection (e.g., a redirected URI prefix that points to a suffix of itself), or when the server is under attack by a client attempting to exploit security holes present in some servers using fixed-length buffers for reading or manipulating the Request-URI.

415 Unsupported Media Type The server is refusing to service the request because the entity of the request is in a format not supported by the requested resource for the requested method.

416 Requested Range Not Satisfiable A server should return a response with this status code if a request included a Range request-header field, and none of the range-specifier values in this field overlap the current extent of the selected resource, and the request did not include an If-Range request-header field. (For byte-ranges, this means that the first- byte-pos of all of the byte-range-spec values were greater than the current length of the selected resource.)

When this status code is returned for a byte-range request, the response should include a Content-Range entity-header field specifying the current length of the selected resource. This response not not use the multipart/byteranges content- type.

417 Expectation Failed The expectation given in an Expect request-header field could not be met by this server, or, if the server is a proxy, the server has unambiguous evidence that the request could not be met by the next-hop server.

Server Error 5xx
Response status codes beginning with the digit "5" indicate cases in which the server is aware that it has erred or is incapable of performing the request. Except when responding to a HEAD request, the server should include an entity containing an explanation of the error situation, and whether it is a temporary or permanent condition. User agents should display any included entity to the user. These response codes are applicable to any request method.

500 Internal Server Error The server encountered an unexpected condition which prevented it from fulfilling the request.

501 Not Implemented The server does not support the functionality required to fulfill the request. This is the appropriate response when the server does not recognise the request method and is not capable of supporting it for any resource.

502 Bad Gateway The server, while acting as a gateway or proxy, received an invalid response from the upstream server it accessed in attempting to fulfill the request.

503 Service Unavailable The server is currently unable to handle the request due to a temporary overloading or maintenance of the server. The implication is that this is a temporary condition which will be alleviated after some delay. If known, the length of the delay may be indicated in a Retry-After header. If no Retry-After is given, the client should handle the response as it would for a 500 response.
Note: The existence of the 503 status code does not imply that a server must use it when becoming overloaded. Some servers may wish to simply refuse the connection.

504 Gateway Timeout The server, while acting as a gateway or proxy, did not receive a timely response from the upstream server specified by the URI (e.g. HTTP, FTP, LDAP) or some other auxiliary server (e.g. DNS) it needed to access in attempting to complete the request.
Note: Note to implementers: some deployed proxies are known to return 400 or 500 when DNS lookups time out.

505 HTTP Version Not Supported The server does not support, or refuses to support, the HTTP protocol version that was used in the request message. The server is indicating that it is unable or unwilling to complete the request using the same major version as the client. The response should contain an entity describing why that version is not supported and what other protocols are supported by that server.

LDAP Errors

Lightweight Directory Access Protocol (LDAP) is an Internet protocol to access directory servers. The directories on the Internet may be "pure" LDAP directories; that is, they only communicate through LDAP, or they may be X.500 or other types of servers that allow access through LDAP. Access to servers that are not pure LDAP servers is accomplished through an LDAP gateway. Gateways from LDAP to other protocols also are common. Client programs that allow a user to access an LDAP directory are called LDAP clients. Applications that extract information from an LDAP directory are referred to as LDAP-enabled.

LDAP Client API Error Conditions

When most LDAP APIs fail to complete successfully, ld_errno usually indicates one of the following errors. Under some conditions, ld_errno could indicate an error other than those listed here.

Error	Definition
0x00	The request was successful. LDAP_SUCCESS
0x01	An operations error occurred. LDAP_OPERATIONS_ERROR
0x02	A protocol violation was detected. LDAP_PROTOCOL_ERROR
0x03	An LDAP time limit was exceeded. LDAP_TIMELIMIT_EXCEEDED
0x04	An LDAP size limit was exceeded. LDAP_SIZELIMIT_EXCEEDED
0x05	A compare operation returned false. LDAP_COMPARE_FALSE
0x06	A compare operation returned true. LDAP_COMPARE_TRUE
0x07	The LDAP server does not support strong authentication. LDAP_STRONG_AUTH_NOT_SUPPORTED
0x08	Strong authentication is required for the operation. LDAP_STRONG_AUTH_REQUIRED
0x09	Partial results only returned. LDAP_PARTIAL_RESULTS
0X0A	Referral returned. LDAP_REFERRAL
0X0B	Administration limit exceeded. LDAP_ADMIN_LIMIT_EXCEEDED
0X0C	Critical extension not supported. LDAP_UNAVAILABLE_CRITICAL_EXTENSION
0x10	The attribute type specified does not exist in the entry. LDAP_NO_SUCH_ATTRIBUTE
0x11	The attribute type specified is not valid. LDAP_UNDEFINED_TYPE
0x12	Filter type not supported for the specified attribute. LDAP_INAPPROPRIATE_MATCHING
0x13	An attribute value specified violates some constraint (for example, a postal address has too many lines, or a line that is too long). LDAP_CONSTRAINT_VIOLATION
0x14	An attribute type or attribute value specified already exists in the entry. LDAP_TYPE_OR_VALUE_EXISTS
0x15	An attribute value was specified that is not valid. LDAP_INVALID_SYNTAX
0x20	The specified object does not exist in the directory. LDAP_NO_SUCH_OBJECT
0x21	An alias in the directory points to a nonexistent entry. LDAP_ALIAS_PROBLEM
0x22	A distinguished name was specified that is syntactically not valid. LDAP_INVALID_DN_SYNTAX
0x23	The object specified is a leaf. LDAP_IS_LEAF
0x24	A problem was encountered when de-referencing an alias. LDAP_ALIAS_DEREF_PROBLEM
0x30	Inappropriate authentication was specified (for example, LDAP_AUTH_SIMPLE was specified and the entry does not have a user password attribute). LDAP_INAPPROPRIATE_AUTH
0x31	Credentials that are not valid were presented (for example, the wrong password). LDAP_INVALID_CREDENTIALS
0x32	The user has insufficient access to perform the operation. LDAP_INSUFFICIENT_ACCESS
0x33	The directory system agent is busy. LDAP_BUSY
0x34	The directory system agent is unavailable. LDAP_UNAVAILABLE
0x35	The directory system agent is unwilling to perform the operation. LDAP_UNWILLING_TO_PERFORM
0x36	A loop was detected. LDAP_LOOP_DETECT
0x40	A naming violation occurred. LDAP_NAMING_VIOLATION
0x41	An object class violation occurred (for example, a must attribute was missing from the entry). LDAP_OBJECT_CLASS_VIOLATION
0x42	The operation is not allowed on a nonleaf object. LDAP_NOT_ALLOWED_ON_NONLEAF
0x43	The operation is not allowed on a relative distinguished name. LDAP_NOT_ALLOWED_ON_RDN
0x44	The entry already exists. LDAP_ALREADY_EXISTS
0x45	Object class modifications are not allowed. LDAP_NO_OBJECT_CLASS_MODS
0x46	Results too large. LDAP_RESULTS_TOO_LARGE
0X47	Affects multiple DSAS. LDAP_AFFECTS_MULTIPLE_DSAS
0x50	An unknown error occurred. LDAP_OTHER
0x51	The LDAP API cannot contact the LDAP server. LDAP_SERVER_DOWN
0x52	Some local error occurred. This usually indicates that either the LDAP support (OS/400 option 32) is not installed on the system, or a malloc() operation has failed LDAP_LOCAL_ERROR
0x53	An error was encountered while the API was encoding parameters to send to the LDAP server. LDAP_ENCODING_ERROR
0x54	An error was encountered while the API was decoding a result from the LDAP server. LDAP_DECODING_ERROR
0x55	A time limit was exceeded while API was waiting for a result. LDAP_TIMEOUT
0x56	The authentication method specified to ldap_bind() is not known. LDAP_AUTH_UNKNOWN
0x57	A filter that is not valid was supplied to ldap_search() (for example, unbalanced parentheses). LDAP_FILTER_ERROR
0x58	User cancelled LDAP_USER_CANCELLED
0x59	An LDAP API was called with a bad parameter (for example, a NULL ld pointer). LDAP_PARAM_ERROR
0x5A	A memory allocation (for example, a malloc() call) failed in an LDAP API. LDAP_NO_MEMORY
0x5b	Connection error LDAP_CONNECT_ERROR
0x5c	Not Supported LDAP_NOT_SUPPORTED
0x5d	Control not found LDAP_CONTROL_NOT_FOUND
0x5e	No results returned LDAP_NO_RESULTS_RETURNED
0x5f	More result to return LDAP_MORE_RESULTS_TO_RETURN
0x60	URL doesn't begin with ldap:// LDAP_URL_ERR_NOTLDAP
0x61	URL has no DN (required). LDAP_URL_ERR_NODN
0x62	URL scope string is invalid. LDAP_URL_ERR_BADSCOPE
0x63	can't allocate memory space. LDAP_URL_ERR_MEM
0x64	Client loop LDAP_CLIENT_LOOP
0x65	Referral limit exceeded LDAP_REFERRAL_LIMIT_EXCEEDED
0x70	ldap_ssl_client_init successfully called previously in this process. LDAP_SSL_ALREADY_INITIALIZED
0x71	SSL initialization call failed. LDAP_SSL_INITIALIZE_FAILED
0x72	Call ldap_ssl_client_init before attempting to use an ssl connection. LDAP_SSL_INITIALIZE_NOT_CALLED
0x73	An invalid ssl parameter was previously specified. LDAP_SSL_PARAM_ERROR
0x74	Failed to connect to ssl server. LDAP_SSL_HANDSHAKE_FAILED
0x75	Failed to identify the maximum SSL encryption level for this host. LDAP_SSL_GET_CIPHER_FAILED
0x76	The SSL library cannot be loaded. LDAP_SSL_NOT_AVAILABLE
0x77	SSL Keyring file not found LDAP_SSL_KEYRING_NOT_FOUND
0x78	SSL password not specified LDAP_SSL_PASSWORD_NOT_SPECIFIED
0x80	No explicit owner found LDAP_NO_EXPLICIT_OWNER
0x81	Could not obtain lock LDAP_NO_LOCK
0x85	No LDAP servers found LDAP_DNS_NO_SERVERS
0x86	Warning truncated DNS results LDAP_DNS_TRUNCATED
0x87	Invalid DNS Data LDAP_DNS_INVALID_DATA
0x88	Can't resolve system domain or nameserver LDAP_DNS_RESOLVE_ERROR
0x89	DNS Configuration file error LDAP_DNS_CONF_FILE_ERROR
0xA0	Output buffer overflow LDAP_XLATE_E2BIG
0xA1	Input buffer truncated LDAP_XLATE_EINVAL
0xA2	Unusable input character LDAP_XLATE_EILSEQ
0xA3	No codeset point to map to LDAP_XLATE_NO_ENTRY
0xB0	NT Registry file not found LDAP_REG_FILE_NOT_FOUND
0xB1	NT Registry cannot open LDAP_REG_CANNOT_OPEN
0xB2	NT Registry entry not found LDAP_REG_ENTRY_NOT_FOUND
0xC0	Plugin configuration file not opened LDAP_CONF_FILE_NOT_OPENED
0xC1	Plugin library not loaded LDAP_PLUGIN_NOT_LOADED
0xC2	Plugin function not resolved LDAP_PLUGIN_FUNCTION_NOT_RESOLVED
0xC3	Plugin library not initialized LDAP_PLUGIN_NOT_INITIALIZED
0xC4	Plugin function could not bind LDAP_PLUGIN_COULD_NOT_BIND
0xD0	gss_init_sec_context failed LDAP_SASL_GSS_NO_SEC_CONTEXT

Solution Design | Professional Services | Remote Support & Management | Managed Hosting Services | UTM | Firewalls | High Availability | Secure VPNs | Remote Access | End Point Security | Single Sign On | Laptop & Device Encryption | USB Device Control | Strong Authentication | Web Filtering | Application Control | Anti Virus | Anti Spam | Content Security