Introduction to Kerberos Authentication

It’s one of the most widely used methods of authentication and this post will briefly introduce you to the subject. As well as being implemented into many operating systems you will find Kerberos is available in many industrial products too. Kerberos hasn’t been tested or verified. Kerberos has many crucial benefits. Kerberos has a few main flaws that system administrators want to take into consideration. Kerberos is the most frequently used example of this sort of authentication technology.

Encryption couldn’t be enabled. The encryption key is subsequently created. Transport layer encryption isn’t necessary if SPNEGO is used, but the customer’s browser has to be properly configured. This authentication is automatic in the event the domains are in the exact same forest. This sort of authentication is rather simple to understand, since it only involves two systems. There are lots of things that could fail with Kerberos authentication. If you’re failing to utilize Kerberos authentication utilizing the LocalSystem account, you’re more than likely failing to utilize Kerberos authentication when users are going to go to the remote system. It’s not only used for authenticating users, when your iPad connects through it’s VPN to watch British Channels online using your AD network it’s Kerberos that authenticates the machine.

In the event the password is incorrect, then you won’t have the ability to decrypt the message. It is extremely important that you don’t forget this password. You might be surprised how many users utilize a password that is just like their user name.

Your password isn’t a fantastic option for a password. When employing those services or those clients, you might have to put in your password, which is subsequently sent to the server. It’s very probable that this user has set the exact same password for the two principals for reasons of convenience. Ideally, you should simply have to type your password into your private computer, once, at the start of the day.

You won’t be able to administrate your server in case you do not keep in mind the master password. In case the server cannot automatically register the SPN, the SPN has to be registered manually. Its normal in order for it to take some opportunity to begin the admin server so be patient. The specified server cannot carry out the requested operation. A digital server simply suggests that it’s not a component of dedicated host. The RPC Server isn’t actively listening.

Server refused to negotiate authentication, which is needed for encryption. Before deploying Kerberos, a server has to be selected to accept the use of KDC. The network location server is a site that is utilised to detect whether DirectAccess clients are situated in the corporate network.

The client may be using an old Kerberos V5 protocol that doesn’t support initial connection support. If he is unable to get the ticket then you should see an error similar to one below. In Kerberos protocol, he authenticates against the server and also the server authenticates itself against the client. The RPC Client will send the very first packet, called the SYN packet.

If each client should happen to require a special key for each and every service, and if each service should happen to require an exceptional key for each client, key distribution could quickly come to be a challenging problem to fix. My client is not going to send the job unless it receives the right response. The client can’t decrypt the service ticket because only servers can do so, but nevertheless, it can send it on. Later he can use this ticket to get additional tickets for SS using the same shared secret. Both client and server may also be called security principals.

John Simmons

Filtering Authentication Credentials

When you use a proxy or VPN server there is a very important security consideration that you should be aware of that is sometimes overlooked.  Any connection should be very careful about how it handles any authentication credentials that are sent using that connection.  For example if you are using a proxy for all your web browsing, you will need to trust that server handling any user names and passwords that you supply to those websites.  Remember the proxy will forward all traffic to the origin server including those user credentials.

The other consideration is specific proxy server authentication credentials which also may be transmitted or passed on especially if the servers are chained.  It is common for proxy credentials to be forwarded as it’s reduces the need to authenticate multiple times against different servers.   In these situations the last proxy server in the chain should filter out the Proxy-Authorization: header if it is present.

One of the dangers is that a malicious server could intercept or capture these authentication credentials especially if they’re being passed in an insecure manner.    Any proxy involved in the route has the potential for intercepting usernames and passwords.  Many people forget this when using random free proxies they find online, they are implicitly trusting these servers and the unknown administrators with any personal details leaked whilst using these connections.  When you consider that often these free servers are merely misconfigured or ‘hacked’ servers it makes using them even more risky.

It is actually a difficult situation particularly with regards to proxies about how to deal with authentication details.  The situation with VPNs are slightly more straightforward, the details are protected during the majority of the transmission because most VPNs are encrypted.  However that last step to the target server will rely on any in built in security to the connection, although this can be effected as in this article – BBC block VPN connection.

Any server can filter out and protect authentication credentials but obviously those intended for the target can’t be removed.  It is a real risk and does highlight one of the important security considerations of using any intermediate server such as a proxy.    It is important that these servers are in themselves secure and do not introduce additional security risks into the connection.  Sending credentials particularly over a normal HTTP session are already potentially insecure without a badly configured or administered proxy server as well.

Most websites which accept usernames now at least use something like SSL to protect credentials.  However although VPN sessions will transport these connections effectively many proxies are unable to support the tunneling of SSL connections properly.  Man in the middle attacks are also common against these sort of protections and using a poorly configured proxy makes this much easier than a direct connection.  Ultimately there are several points where web security and protecting the data is a concern, it’s best to ensure that a VPN or proxy doesn’t introduce additional security risks into the connection though.

Additional Reading on UK VPN Trial



Content Filtering and Proxies

Proxy servers are as explained on this site, one of the most important components of a modern network infrastructure.  No corporate network should allow ordinary desktop PCs or laptops to directly access the internet without some sort of protection.  Proxy servers provide that protection to a certain extent as long as their use is enforced.

Most users, especially technically minded ones will often resent using proxies because they will be aware of the control that this entails.   The simplest way is to ensure that configuration files are delivered automatically to the desktop by network servers.  For example in a Windows environment this can be achieved using the active directory which can ensure desktops and users receive specific internet configuration files.  For example, you can configure Internet Explorer using a specific configuration which is delivered to every desktop on login.  In addition you can also use Active Directory to block access to install other browsers and configure them.

However although this allows you to control what browser and the internet route that each user will take – it doesn’t restrict what that user can do online.  Another layer is required and most companies will employ some sort of content filtering in order to protect their environment.    However as far as your proxy server is concerned content filtering will almost obviously have a major impact on performance.

One of the most common forms is that of URL filtering and this has one of the biggest performance impacts.  This is largely due to the fact that this sort of filtering inevitably has many types of patterns to match against.   Content filtering will severely impact the performance of a proxy server because of the sheer volume of data that is involved.  Even running a nominal content filter against a UK VPN trial had a similar effect.

There are a variety of different types of filtering such as HTML tag filtering, virus screening or URL screening.   It can be difficult though and the technology is developing all the time, for instance the ability to screen things like Java or ActiveX objects.

One of the biggest problems with content filtering and maintaining performance on the proxies is the fact that entire objects need to be processed.  A proxy server will need to buffer the entire file, and therefore can only proceed with the transmission after the whole file has been checked.   From the user perspective this can be frustrating as there will be long pauses and delays in their browsing especially on busy networks.   Obviously this delay can be justified in the extent of screening for viruses, however this can be controversial for other screening issues.

Further Reference: Using a Paid VPN Service

TCP Configuration: Timestamp Option

The function of the timestamp option is fairly self explanatory, it simply lets the sender place a timestamp value in each and every segment.   In turn the receiver will also reflect this value in it’s acknowledgement which allows the sender to calculate a round trip time for every received ACK.    Remember this is indeed per ACK and not segment as this can include multiple segments.

Initially most implementations of TCP would only allow one RTT per window however this has changed and nowadays larger windows sizes need more accurate RTT calculations.   You can read about the definitions of these calculations in RFC 1323 which covers the TCP enhanced extensions that allow these improved RTT calculations. The time is estimated by sampling a data signal at a lower frequency one time per window which works well with smaller windows (and less segments).

Accurate measurement of data transmission is often very difficult in congested and busy networks also when troubleshooting across networks like the internet.  It’s difficult to  isolate issues and solve problems in these sort of environments because you have no control or access to the majority of the transport hardware.  For example if you are tryign to fix a Netflix VPN problem remotely being able to check the RTT is essential to analyse where the problems potentially lie.

The sender will place a 32 bit value in the initial field which will be echoed back by the receiver in the reply field. This will increase the size of the TCP header from 20 bytes to 32 bytes when this option is used. The timestamp value will increase value on each transaction. There is no clock synchronization between the sender and the receiver merely an increase in the value of the timestamp unit. Most implementations of the timestamp option recommend that the value increment in units of one ideally between 1 millisecond and 1 second.

This option is configured during the connection establishment and is handled the same way as the windows scale option in the previous section. As you may know the receiving connection does not have to acknowledge every data segment it receives. This however is simplified because only a single timestamp value is maintained per active connection which is updated according to simple algorithm.

First of all TCP monitors the timestamp value ensuring it has the correct value to send in the next ACK. The sequence number is updated after each ACK value is sent and not as it’s acknowledged. After a new segment arrives then the byte numbered in a variable called lastack is incremented. After a new segment arrives then this value is increased but the old value stored in a variable called tsrecent, When a timestamp option is sent the tsrecent value is sent, and the sequence number field is stored in the variable called lastack.

This means that in addition to the timestamp option allowing for better RTT calculation it also performs another function. The receiver can use the function to avoid receiving old duplicate segments using an addition feature called PAWS – Protection against Wrapped Sequence Numbers.

Further Reading on Commercial Proxy Options –

TCP Configuration: Windows Scale Options

There are many ways to configure the way TCP/IP operates on specific networks.  Some of these parameters are rarely used but when you’re running fast Gigabit networks with a wide variety of network hardware and infrastructure some options are extremely useful.  One of those is the Windows Scale option which can be used to modify the definition of the TCP Window from it’s default of 16 bits.

For example in some environments it may be appropriate to increase the size of the TCP windows to 32 bits.   What actually happens is that instead of changing the size of the header to allow the larger windows, the header still holds a 16-bit value.   However an option allows a scaling parameter to be applied to the value which allows TCP to maintain the actual value of 32 bits internally.

The option for scaling can only appear in the SYN segment of the transaction which means that the scaling value by definition will be fixed in both directions when the connection is initially established.   In order for window scaling to be enable both ends of the connection must include the option in their SYN segments.   It should be noted thought that the scale option can be different in each direction.

There are methods for allowing suitable communication between different levels of hardware.   For example the scaling factor can be reduced by sending a non zero scale factor which cancels the scaling if a windows scaling option is not received in the return SYN.   This behaviour is specified in the relevant RFC which specifies that TCP must accept these options in any segment.   This includes all sorts of of connection remember these can be across wide areas, imagine a US IP address connecting to a Netflix server on super fast hardware.   However it should also be noted that TCP/IP will always ignore any option that it doesn’t understand.

For illustration, if the windows scale option is being used with a shift count of X for sending and Y for receiving.  This would mean that every 16 bit window which is advertised would be left shifted by Y bits to obtain the real advertised window.  So every time a windows advertisement is sent then we’d also take the 32 bit windows size and right shift by X bit to discover the real 16 bit value which is in the TCP header.

Any shift count is automatically controlled by TCP, which is because the size of the receiving buffer is important and cannot be controlled by the other size of the connection.

Further Reading

TCP Tricks, receiving BBC iPlayer in France –


Networking Terms: LAN

LAN in networking terms stands for Local Area Network and it refers to a shared communication system that many computers and other devices are attached.   The distinction between this and other networks is that a LAN is a network limited to a local area.

The first recorded use of LANs where in the 1970s, where they grew from the very first basic networking setups.  These consisted of two devices connected by a single network wire much like a child’s string and paper cup model designed to mimic the telephone.   Computer scientists started to think why limit to two devices when the same cable could theoretically connect multiple devices.   There were complications though, and possibly the most basic was finding a mechanism that ensured that multiple devices didn’t use the cable at the same time.

The methods used to ensure that use of the cables are shared properly are called ‘medium access controls’ for self explanatory reasons.  There are a variety of these ranging from allowing workstations to announce their communications to a central device which controls access and allocates bandwidth as required.  In some senses in the same way an individual may buy uk proxy access in order to route their connection privately whilst hiding their own IP address.

Although LANs are normally restricted to a smaller geographical location there are actually different topologies.   The simplest and originally was the most common is the liner bus and the star configuration.   The linear bus involves a cable laid throughout a building from one workstation to another.  Whereas the star configuration has each workstation attached to a central location or hub connected by it’s own specific cable.  There are pros and cons to each configuration and in fact if you use the most popular networking medium ethernet you can use either topology.

A local Area Network is actually a connectionless networking configuration. That definition is important and actually means that once a device is ready to use the network to transmit data it simply releases the data onto the cable and ‘hopes’ that it reaches it’s destination.    In this basic setup, no initial process involves ensuring that the data reaches it’s recipient nor is there any check to see whether it has been received.

When data is transmitted across the LAN it is packaged into ‘frames’ before being dispatched.  At the basic hardware level, each frame is transmitted as a bit stream across the wire.  Every single device connected to this network will listed to the transmission although only the intended recipient will actually receive the data.    Normally this is the case but it is possible to transmit on a multicast address which specifies that all devices on the LAN should receive the data. Other higher level protocols will actually package the data further into datagrams examples of these are IP or IPX.

Further Reading:

Network Troubleshooting – Which Smart DNS Still Works with Netflix

RSVP (Resource Reservation Protocol)

There is no doubt that TCP/IP has transformed our computer networks and played a pivotal role in the expansion of the world wide web, however it is far from perfect.   RSVP is an Internet protocol designed to alleviate some of the issues with TCP/IP particularly regarding delivering data on time and in the right order.  This has been always one of TCP/IP’s biggest shortcomings – it’s ‘best effort’ IP delivery service has no guarantees.  Whereas TCP which is connection orientated does guarantee delivery but gives no assurances on the time it takes.

Guaranteed on time delivery is essential in many of the modern day applications particularly over the internet – especially those including voice and video delivery.  Indeed most web sites involve large amounts of video and voice data which require fast, reliable and timely delivery whenever possible.  If anyone has tried streaming or downloading from applications like the BBC iPlayer like this for example they will know how frustrating slow speeds and missing data packets can be.

The issues are well known and RSVP is an attempt to provide a suitable quality of service for video and voice delivery particularly across the internet and other large TCP/IP based networks.  The way RSVP works is to reserve bandwidth across router connected networks.   It does this by asking each router to keep some of it’s bandwidth allocated to particular traffic flow.  In some senses it is an attempt to add some of the quality features of ATM to TCP/IP in order to facilitate the changing requirements of modern day networks.

RSVP is one of the first attempts to introduce a quality service to TCP/IP but many vendors are looking at introducing many other options too.  Most of them focus like RSVP on reserving bandwidth however this isn’t always an ideal situation.  The obvious issue is that if you reserve network capacity for specific traffic or connection then the amount is reduced for all other users and applications. Some of this issue has been mitigated by  the increase in capacity of both corporate networks and the connections for individual users to the internet.

RSVP works by establishing and maintain bandwidth reservations on a specific network so it’s not a WAN or wide area solution normally. The protocol works from router to router setting up a reservation from each end of the system. It is primarily a signalling protocol not specifically a routing protocol.  If a specific router along the connection cannot provide the requested bandwidth then RSVP will look for an alternative route.  Obviously this only works if the routers have RSVP enabled which many currently do to support this process.   Applications can also use this feature by making similar requests.

Further Reading:

Watching UK TV in USA – a study in optimizing video streams using QoS enabled routers.

Quick Introduction to Computer Ports

Any computer that has network connectivity usually offers services to users both remotely and locally.  Typically the computer will offer these services by running a number of locally hosted services.  In a TCP/IP network, the services are usually available via ports on the local computer.  When a computer connects to access a particular service and end-to-end connection is normally established and a socket set up at each end of the connection.  In simple terms you can think of the socket as a telephone at each end of a line and the port is a specific telephone number.

Most of the common services are usually found at a predetermined port number, in fact they can act as an identifier of the service.     It’s important to remember that although these port number assignments are normally followed there is no strict enforcement of these standards.    Although it is likely that an FTP server is listening on Port 21 there is no actual guarantee that this is true.   These predetermined port assignments are commonly followed though and it is usually considered best practice.   In some senses it can make network management functions much simpler than if non-standard ports are used which makes identifying roles and services harder.

For instance most people would expect a service running on port 80 would be a HTTP server although there is nothing to stop some other service using it.

Republished from archive of Thomas Riemer’s Port Numbers page

The Registered Ports are not controlled by the IANA and on most systems can be used by ordinary user processes or programs executed by ordinary users.

Ports are used in the TCP [RFC793] to name the ends of logical connections which carry long term conversations. For the purpose of providing services to unknown callers, a service contact port is defined. This list specifies the port used by the server process as its contact port. While the IANA can not control uses of these ports it does register or list uses of these ports as a convienence to the community.

To the extent possible, these same port assignments are used with the UDP [RFC768].

The Registered Ports are in the range 1024-65535.

Port Assignments:


  • 1024/tcp Reserved
  • 1024/udp Reserved
  • blackjack 1025/tcp network blackjack
  • blackjack 1025/udp network blackjack
  • iad1 1030/tcp BBN IAD
  • iad1 1030/udp BBN IAD
  • iad2 1031/tcp BBN IAD
  • iad2 1031/udp BBN IAD
  • iad3 1032/tcp BBN IAD
  • iad3 1032/udp BBN IAD
  • nim 1058/tcp nim
  • nim 1058/udp nim
  • nimreg 1059/tcp nimreg
  • nimreg 1059/udp nimreg
  • instl_boots 1067/tcp Installation Bootstrap Proto. Serv.
  • instl_boots 1067/udp Installation Bootstrap Proto. Serv.
  • instl_bootc 1068/tcp Installation Bootstrap Proto. Cli.
  • instl_bootc 1068/udp Installation Bootstrap Proto. Cli.
  • socks 1080/tcp Socks
  • socks 1080/udp Socks
  • ansoft-lm-1 1083/tcp Anasoft License Manager
  • ansoft-lm-1 1083/udp Anasoft License Manager
  • ansoft-lm-2 1084/tcp Anasoft License Manager
  • Ip address American Netflix
  • ansoft-lm-2 1084/udp Anasoft License Manager
  • nfsd-status 1110/tcp Cluster status info
  • nfsd-keepalive 1110/udp Client status info
  • nfa 1155/tcp Network File Access
  • nfa 1155/udp Network File Access
  • lupa 1212/tcp lupa
  • lupa 1212/udp lupa
  • nerv 1222/tcp SNI R&D; network
  • nerv 1222/udp SNI R&D; network
  • hermes 1248/tcp
  • hermes 1248/udp
  • alta-ana-lm 1346/tcp Alta Analytics License Manager
  • alta-ana-lm 1346/udp Alta Analytics License Manager
  • bbn-mmc 1347/tcp multi media conferencing
  • bbn-mmc 1347/udp multi media conferencing
  • bbn-mmx 1348/tcp multi media conferencing
  • bbn-mmx 1348/udp multi media conferencing
  • sbook 1349/tcp Registration Network Protocol
  • sbook 1349/udp Registration Network Protocol
  • channel 4 online abroad
  • editbench 1350/tcp Registration Network Protocol
  • editbench 1350/udp Registration Network Protocol
  • equationbuilder 1351/tcp Digital Tool Works (MIT)
  • equationbuilder 1351/udp Digital Tool Works (MIT)
  • lotusnote 1352/tcp Lotus Note
  • relief 1353/tcp Relief Consulting
  • relief 1353/udp Relief Consulting
  • rightbrain 1354/tcp RightBrain Software
  • rightbrain 1354/udp RightBrain Software
  • intuitive edge 1355/tcp Intuitive Edge
  • intuitive edge 1355/udp Intuitive Edge
  • cuillamartin 1356/tcp CuillaMartin Company
  • cuillamartin 1356/udp CuillaMartin Company
  • pegboard 1357/tcp Electronic PegBoard
  • pegboard 1357/udp Electronic PegBoard
  • connlcli 1358/tcp CONNLCLI
  • connlcli 1358/udp CONNLCLI
  • US Ip Address
  • ftsrv 1359/tcp FTSRV
  • ftsrv 1359/udp FTSRV
  • mimer 1360/tcp MIMER
  • mimer 1360/udp MIMER
  • linx 1361/tcp LinX
  • linx 1361/udp LinX
  • timeflies 1362/tcp TimeFlies
  • timeflies 1362/udp TimeFlies
  • ndm-requester 1363/tcp Network DataMover Requester
  • ndm-requester 1363/udp Network DataMover Requester
  • ndm-server 1364/tcp Network DataMover Server
  • ndm-server 1364/udp Network DataMover Server
  • adapt-sna 1365/tcp Network Software Associates
  • adapt-sna 1365/udp Network Software Associates
  • netware-csp 1366/tcp Novell NetWare Comm Service Platform
  • netware-csp 1366/udp Novell NetWare Comm Service Platform
  • dcs 1367/tcp DCS
  • dcs 1367/udp DCS
  • screencast 1368/tcp ScreenCast
  • screencast 1368/udp ScreenCast
  • gv-us 1369/tcp GlobalView to Unix Shell
  • gv-us 1369/udp GlobalView to Unix Shell
  • us-gv 1370/tcp Unix Shell to GlobalView
  • us-gv 1370/udp Unix Shell to GlobalView
  • fc-cli 1371/tcp Fujitsu Config Protocol
  • fc-cli 1371/udp Fujitsu Config Protocol
  • fc-ser 1372/tcp Fujitsu Config Protocol
  • fc-ser 1372/udp Fujitsu Config Protocol
  • chromagrafx 1373/tcp Chromagrafx
  • chromagrafx 1373/udp Chromagrafx
  • molly 1374/tcp EPI Software Systems
  • molly 1374/udp EPI Software Systems
  • bytex 1375/tcp Bytex
  • bytex 1375/udp Bytex
  • ibm-pps 1376/tcp IBM Person to Person Software
  • ibm-pps 1376/udp IBM Person to Person Software
  • cichlid 1377/tcp Cichlid License Manager
  • cichlid 1377/udp Cichlid License Manager
  • elan 1378/tcp Elan License Manager
  • dbreporter 1379/tcp Integrity Solutions
  • dbreporter 1379/udp Integrity Solutions
  • telesis-licman 1380/tcp Telesis Network License Manager
  • telesis-licman 1380/udp Telesis Network License Manager
  • apple-licman 1381/tcp Apple Network License Manager
  • apple-licman 1381/udp Apple Network License Manager
  • udt_os 1382/tcp
  • udt_os 1382/udp
  • gwha 1383/tcp GW Hannaway Network License Manager
  • gwha 1383/udp GW Hannaway Network License Manager
  • os-licman 1384/tcp Objective Solutions License Manager
  • os-licman 1384/udp Objective Solutions License Manager
  • atex_elmd 1385/tcp Atex Publishing License Manager
  • atex_elmd 1385/udp Atex Publishing License Manager
  • checksum 1386/tcp CheckSum License Manager
  • checksum 1386/udp CheckSum License Manager
  • cadsi-lm 1387/tcp Computer Aided Design Software Inc LM
  • cadsi-lm 1387/udp Computer Aided Design Software Inc LM
  • objective-dbc 1388/tcp Objective Solutions DataBase Cache
  • objective-dbc 1388/udp Objective Solutions DataBase Cache
  • iclpv-dm 1389/tcp Document Manager
  • iclpv-dm 1389/udp Document Manager
  • iclpv-sc 1390/tcp Storage Controller
  • iclpv-sc 1390/udp Storage Controller
  • iclpv-sas 1391/tcp Storage Access Server
  • iclpv-sas 1391/udp Storage Access Server
  • iclpv-pm 1392/tcp Print Manager
  • iclpv-pm 1392/udp Print Manager
  • iclpv-nls 1393/tcp Network Log Server
  • iclpv-nls 1393/udp Network Log Server
  • iclpv-nlc 1394/tcp Network Log Client
  • iclpv-nlc 1394/udp Network Log Client
  • iclpv-wsm 1395/tcp PC Workstation Manager software
  • iclpv-wsm 1395/udp PC Workstation Manager software
  • dvl-activemail 1396/tcp DVL Active Mail
  • dvl-activemail 1396/udp DVL Active Mail
  • audio-activmail 1397/tcp Audio Active Mail
  • audio-activmail 1397/udp Audio Active Mail
  • video-activmail 1398/tcp Video Active Mail
  • video-activmail 1398/udp Video Active Mail
  • cadkey-licman 1399/tcp Cadkey License Manager
  • cadkey-licman 1399/udp Cadkey License Manager
  • cadkey-tablet 1400/tcp Cadkey Tablet Daemon
  • cadkey-tablet 1400/udp Cadkey Tablet Daemon
  • goldleaf-licman 1401/tcp Goldleaf License Manager
  • goldleaf-licman 1401/udp Goldleaf License Manager
  • prm-sm-np 1402/tcp Prospero Resource Manager
  • prm-nm-np 1403/tcp Prospero Resource Manager
  • igi-lm 1404/tcp Infinite Graphics License Manager
  • igi-lm 1404/udp Infinite Graphics License Manager
  • ibm-res 1405/tcp IBM Remote Execution Starter
  • ibm-res 1405/udp IBM Remote Execution Starter
  • netlabs-lm 1406/tcp NetLabs License Manager
  • netlabs-lm 1406/udp NetLabs License Manager
  • dbsa-lm 1407/tcp DBSA License Manager
  • dbsa-lm 1407/udp DBSA License Manager
  • sophia-lm 1408/tcp Sophia License Manager
  • sophia-lm 1408/udp Sophia License Manager
  • here-lm 1409/tcp Here License Manager
  • here-lm 1409/udp Here License Manager
  • hiq 1410/tcp HiQ License Manager
  • hiq 1410/udp HiQ License Manager
  • af 1411/tcp AudioFile
  • af 1411/udp AudioFile
  • innosys 1412/tcp InnoSys
  • innosys 1412/udp InnoSys
  • innosys-acl 1413/tcp Innosys-ACL
  • innosys-acl 1413/udp Innosys-ACL
  • ibm-mqseries 1414/tcp IBM MQSeries
  • ibm-mqseries 1414/udp IBM MQSeries
  • dbstar 1415/tcp DBStar
  • dbstar 1415/udp DBStar
  • novell-lu6.2 1416/tcp Novell LU6.2
  • novell-lu6.2 1416/udp Novell LU6.2
  • timbuktu-srv1 1417/tcp Timbuktu Service 1 Port
  • timbuktu-srv2 1418/tcp Timbuktu Service 2 Port
  • timbuktu-srv3 1419/tcp Timbuktu Service 3 Port
  • timbuktu-srv4 1420/tcp Timbuktu Service 4 Port
  • gandalf-lm 1421/tcp Gandalf License Manager
  • gandalf-lm 1421/udp Gandalf License Manager
  • autodesk-lm 1422/tcp Autodesk License Manager
  • autodesk-lm 1422/udp Autodesk License Manager
  • essbase 1423/tcp Essbase Arbor Software
  • essbase 1423/udp Essbase Arbor Software
  • hybrid 1424/tcp Hybrid Encryption Protocol
  • hybrid 1424/udp Hybrid Encryption Protocol
  • zion-lm 1425/tcp Zion Software License Manager
  • zion-lm 1425/udp Zion Software License Manager
  • sas-1 1426/tcp Satellite-data Acquisition System 1
  • sas-1 1426/udp Satellite-data Acquisition System 1
  • mloadd 1427/tcp mloadd monitoring tool
  • mloadd 1427/udp mloadd monitoring tool
  • informatik-lm 1428/tcp Informatik License Manager
  • informatik-lm 1428/udp Informatik License Manager
  • nms 1429/tcp Hypercom NMS
  • nms 1429/udp Hypercom NMS
  • tpdu 1430/tcp Hypercom TPDU
  • tpdu 1430/udp Hypercom TPDU
  • rgtp 1431/tcp Reverse Gossip Transport
  • rgtp 1431/udp Reverse Gossip Transport
  • blueberry-lm 1432/tcp Blueberry Software License Manager
  • blueberry-lm 1432/udp Blueberry Software License Manager
  • ms-sql-s 1433/tcp Microsoft-SQL-Server
  • ms-sql-m 1434/tcp Microsoft-SQL-Monitor
  • ms-sql-m 1434/udp Microsoft-SQL-Monitor
  • ibm-cics 1435/tcp IBM CISC
  • ibm-cics 1435/udp IBM CISC
  • sas-2 1436/tcp Satellite-data Acquisition System 2
  • sas-2 1436/udp Satellite-data Acquisition System 2
  • tabula 1437/tcp Tabula
  • tabula 1437/udp Tabula
  • eicon-server 1438/tcp Eicon Security Agent/Server
  • eicon-server 1438/udp Eicon Security Agent/Server
  • eicon-x25 1439/tcp Eicon X25/SNA Gateway
  • eicon-x25 1439/udp Eicon X25/SNA Gateway
  • eicon-slp 1440/tcp Eicon Service Location Protocol
  • eicon-slp 1440/udp Eicon Service Location Protocol
  • cadis-1 1441/tcp Cadis License Management
  • cadis-1 1441/udp Cadis License Management
  • cadis-2 1442/tcp Cadis License Management
  • cadis-2 1442/udp Cadis License Management
  • ies-lm 1443/tcp Integrated Engineering Software
  • ies-lm 1443/udp Integrated Engineering Software
  • marcam-lm 1444/tcp Marcam License Management
  • marcam-lm 1444/udp Marcam License Management
  • proxima-lm 1445/tcp Proxima License Manager
  • proxima-lm 1445/udp Proxima License Manager
  • ora-lm 1446/tcp Optical Research Associates License Manager
  • ora-lm 1446/udp Optical Research Associates License Manager
  • apri-lm 1447/tcp Applied Parallel Research LM
  • apri-lm 1447/udp Applied Parallel Research LM
  • oc-lm 1448/tcp OpenConnect License Manager
  • oc-lm 1448/udp OpenConnect License Manager
  • peport 1449/tcp PEport
  • peport 1449/udp PEport
  • dwf 1450/tcp Tandem Distributed Workbench Facility
  • dwf 1450/udp Tandem Distributed Workbench Facility
  • infoman 1451/tcp IBM Information Management
  • infoman 1451/udp IBM Information Management
  • gtegsc-lm 1452/tcp GTE Government Systems License Man
  • gtegsc-lm 1452/udp GTE Government Systems License Man
  • genie-lm 1453/tcp Genie License Manager
  • genie-lm 1453/udp Genie License Manager
  • interhdl_elmd 1454/tcp interHDL License Manager
  • interhdl_elmd 1454/tcp interHDL License Manager
  • esl-lm 1455/tcp ESL License Manager
  • esl-lm 1455/udp ESL License Manager
  • dca 1456/tcp DCA
  • dca 1456/udp DCA
  • valisys-lm 1457/tcp Valisys License Manager
  • valisys-lm 1457/udp Valisys License Manager
  • nrcabq-lm 1458/tcp Nichols Research Corp.
  • nrcabq-lm 1458/udp Nichols Research Corp.
  • proshare1 1459/tcp Proshare Notebook Application
  • proshare1 1459/udp Proshare Notebook Application
  • proshare2 1460/tcp Proshare Notebook Application
  • proshare2 1460/udp Proshare Notebook Application
  • ibm_wrless_lan 1461/tcp IBM Wireless LAN
  • ibm_wrless_lan 1461/udp IBM Wireless LAN
  • world-lm 1462/tcp World License Manager
  • world-lm 1462/udp World License Manager
  • nucleus 1463/tcp Nucleus
  • nucleus 1463/udp Nucleus
  • msl_lmd 1464/tcp MSL License Manager
  • msl_lmd 1464/udp MSL License Manager
  • pipes 1465/tcp Pipes Platform
  • pipes 1465/udp Pipes Platform
  • oceansoft-lm 1466/tcp Ocean Software License Manager
  • oceansoft-lm 1466/udp Ocean Software License Manager
  • csdmbase 1467/tcp CSDMBASE
  • csdmbase 1467/udp CSDMBASE
  • csdm 1468/tcp CSDM
  • csdm 1468/udp CSDM
  • aal-lm 1469/tcp Active Analysis Limited License Manager
  • aal-lm 1469/udp Active Analysis Limited License Manager
  • uaiact 1470/tcp Universal Analytics
  • uaiact 1470/udp Universal Analytics
  • csdmbase 1471/tcp csdmbase
  • csdmbase 1471/udp csdmbase
  • csdm 1472/tcp csdm
  • csdm 1472/udp csdm
  • openmath 1473/tcp OpenMath
  • openmath 1473/udp OpenMath
  • telefinder 1474/tcp Telefinder
  • telefinder 1474/udp Telefinder
  • taligent-lm 1475/tcp Taligent License Manager
  • taligent-lm 1475/udp Taligent License Manager
  • clvm-cfg 1476/tcp clvm-cfg
  • clvm-cfg 1476/udp clvm-cfg
  • ms-sna-server 1477/tcp ms-sna-server
  • ms-sna-base 1478/tcp ms-sna-base
  • ms-sna-base 1478/udp ms-sna-base
  • dberegister 1479/tcp dberegister
  • dberegister 1479/udp dberegister
  • pacerforum 1480/tcp PacerForum
  • pacerforum 1480/udp PacerForum
  • airs 1481/tcp AIRS
  • airs 1481/udp AIRS
  • miteksys-lm 1482/tcp Miteksys License Manager
  • miteksys-lm 1482/udp Miteksys License Manager
  • afs 1483/tcp AFS License Manager
  • afs 1483/udp AFS License Manager
  • confluent 1484/tcp Confluent License Manager
  • confluent 1484/udp Confluent License Manager
  • lansource 1485/tcp LANSource
  • lansource 1485/udp LANSource
  • nms_topo_serv 1486/tcp nms_topo_serv
  • nms_topo_serv 1486/udp nms_topo_serv
  • localinfosrvr 1487/tcp LocalInfoSrvr
  • localinfosrvr 1487/udp LocalInfoSrvr
  • docstor 1488/tcp DocStor
  • docstor 1488/udp DocStor
  • dmdocbroker 1489/tcp dmdocbroker
  • dmdocbroker 1489/udp dmdocbroker
  • insitu-conf 1490/tcp insitu-conf
  • insitu-conf 1490/udp insitu-conf
  • anynetgateway 1491/tcp anynetgateway
  • anynetgateway 1491/udp anynetgateway
  • stone-design-1 1492/tcp stone-design-1
  • stone-design-1 1492/udp stone-design-1
  • netmap_lm 1493/tcp netmap_lm
  • netmap_lm 1493/udp netmap_lm
  • ica 1494/tcp ica
  • ica 1494/udp ica
  • cvc 1495/tcp cvc
  • cvc 1495/udp cvc
  • liberty-lm 1496/tcp liberty-lm
  • liberty-lm 1496/udp liberty-lm
  • rfx-lm 1497/tcp rfx-lm
  • rfx-lm 1497/udp rfx-lm
  • watcom-sql 1498/tcp Watcom-SQL
  • watcom-sql 1498/udp Watcom-SQL
  • fhc 1499/tcp Federico Heinz Consultora
  • fhc 1499/udp Federico Heinz Consultora
  • vlsi-lm 1500/tcp VLSI License Manager
  • vlsi-lm 1500/udp VLSI License Manager
  • sas-3 1501/tcp Satellite-data Acquisition System 3
  • sas-3 1501/udp Satellite-data Acquisition System 3
  • shivadiscovery 1502/tcp Shiva
  • shivadiscovery 1502/udp Shiva
  • imtc-mcs 1503/tcp Databeam
  • imtc-mcs 1503/udp Databeam
  • evb-elm 1504/tcp EVB Software Engineering License Manager
  • evb-elm 1504/udp EVB Software Engineering License Manager
  • funkproxy 1505/tcp Funk Software, Inc.
  • funkproxy 1505/udp Funk Software, Inc.
  • utcd 1506/tcp Universal Time daemon (utcd)
  • utcd 1506/udp Universal Time daemon (utcd)
  • symplex 1507/tcp symplex
  • symplex 1507/udp symplex
  • diagmond 1508/tcp diagmond
  • diagmond 1508/udp diagmond
  • robcad-lm 1509/tcp Robcad, Ltd. License Manager
  • robcad-lm 1509/udp Robcad, Ltd. License Manager
  • mvx-lm 1510/tcp Midland Valley Exploration Ltd. Lic. Man.
  • mvx-lm 1510/udp Midland Valley Exploration Ltd. Lic. Man.
  • 3l-l1 1511/tcp 3l-l1
  • 3l-l1 1511/udp 3l-l1
  • wins 1512/tcp Microsoft’s Windows Internet Name Service
  • wins 1512/udp Microsoft’s Windows Internet Name Service
  • fujitsu-dtc 1513/tcp Fujitsu DTC
  • fujitsu-dtc 1513/udp Fujitsu DTC
  • fujitsu-dtcns 1514/tcp Fujitsu DTCNS
  • fujitsu-dtcns 1514/udp Fujitsu DTCNS
  • ifor-protocol 1515/tcp ifor-protocol
  • ifor-protocol 1515/udp ifor-protocol
  • vpad 1516/tcp Virtual Places Audio data
  • vpad 1516/udp Virtual Places Audio data
  • vpac 1517/tcp Virtual Places Audio control
  • vpac 1517/udp Virtual Places Audio control
  • vpvd 1518/tcp Virtual Places Video data
  • vpvd 1518/udp Virtual Places Video data
  • vpvc 1519/tcp Virtual Places Video control
  • vpvc 1519/udp Virtual Places Video control
  • atm-zip-office 1520/tcp atm zip office
  • atm-zip-office 1520/udp atm zip office
  • ncube-lm 1521/tcp nCube License Manager
  • ncube-lm 1521/udp nCube License Manager
  • rna-lm 1522/tcp Ricardo North America License Manager
  • rna-lm 1522/udp Ricardo North America License Manager
  • cichild-lm 1523/tcp cichild
  • cichild-lm 1523/udp cichild
  • ingreslock 1524/tcp ingres
  • ingreslock 1524/udp ingres
  • orasrv 1525/tcp oracle
  • orasrv 1525/udp oracle
  • prospero-np 1525/tcp Prospero Directory Service non-priv
  • pdap-np 1526/tcp Prospero Data Access Prot non-priv
  • tlisrv 1527/tcp oracle
  • tlisrv 1527/udp oracle
  • mciautoreg 1528/tcp micautoreg
  • mciautoreg 1528/udp micautoreg
  • coauthor 1529/tcp oracle
  • coauthor 1529/udp oracle
  • rap-service 1530/tcp rap-service
  • rap-service 1530/udp rap-service
  • rap-listen 1531/tcp rap-listen
  • rap-listen 1531/udp rap-listen
  • miroconnect 1532/tcp miroconnect
  • miroconnect 1532/udp miroconnect
  • virtual-places 1533/tcp Virtual Places Software
  • virtual-places 1533/udp Virtual Places Software
  • micromuse-lm 1534/tcp micromuse-lm
  • micromuse-lm 1534/udp micromuse-lm
  • ampr-info 1535/tcp ampr-info
  • ampr-info 1535/udp ampr-info
  • ampr-inter 1536/tcp ampr-inter
  • ampr-inter 1536/udp ampr-inter
  • sdsc-lm 1537/tcp isi-lm
  • sdsc-lm 1537/udp isi-lm
  • 3ds-lm 1538/tcp 3ds-lm
  • 3ds-lm 1538/udp 3ds-lm
  • intellistor-lm 1539/tcp Intellistor License Manager
  • intellistor-lm 1539/udp Intellistor License Manager
  • rds 1540/tcp rds
  • rds 1540/udp rds
  • PortMaster 1541/tcp PortMaster for SSL
  • rds2 1541/tcp rds2
  • rds2 1541/udp rds2
  • gridgen-elmd 1542/tcp gridgen-elmd
  • gridgen-elmd 1542/udp gridgen-elmd
  • simba-cs 1543/tcp simba-cs
  • simba-cs 1543/udp simba-cs
  • aspeclmd 1544/tcp aspeclmd
  • aspeclmd 1544/udp aspeclmd
  • vistium-share 1545/tcp vistium-share
  • vistium-share 1545/udp vistium-share
  • issd 1600/tcp
  • issd 1600/udp
  • nkd 1650/tcp
  • nkd 1650/udp
  • shiva_confsrvr 1651/tcp shiva_confsrvr
  • shiva_confsrvr 1651/udp shiva_confsrvr
  • xnmp 1652/tcp xnmp
  • xnmp 1652/udp xnmp
  • netview-aix-1 1661/tcp netview-aix-1
  • netview-aix-1 1661/udp netview-aix-1
  • netview-aix-2 1662/tcp netview-aix-2
  • netview-aix-2 1662/udp netview-aix-2
  • netview-aix-3 1663/tcp netview-aix-3
  • netview-aix-3 1663/udp netview-aix-3
  • netview-aix-4 1664/tcp netview-aix-4
  • netview-aix-4 1664/udp netview-aix-4
  • netview-aix-5 1665/tcp netview-aix-5
  • netview-aix-5 1665/udp netview-aix-5
  • netview-aix-6 1666/tcp netview-aix-6
  • netview-aix-6 1666/udp netview-aix-6
  • netview-aix-7 1667/tcp netview-aix-7
  • netview-aix-7 1667/udp netview-aix-7
  • netview-aix-8 1668/tcp netview-aix-8
  • netview-aix-8 1668/udp netview-aix-8
  • netview-aix-9 1669/tcp netview-aix-9
  • netview-aix-9 1669/udp netview-aix-9
  • netview-aix-10 1670/tcp netview-aix-10
  • netview-aix-10 1670/udp netview-aix-10
  • netview-aix-11 1671/tcp netview-aix-11
  • netview-aix-11 1671/udp netview-aix-11
  • netview-aix-12 1672/tcp netview-aix-12
  • netview-aix-12 1672/udp netview-aix-12
  • licensedaemon 1986/tcp cisco license management
  • licensedaemon 1986/udp cisco license management
  • tr-rsrb-p1 1987/tcp cisco RSRB Priority 1 port
  • tr-rsrb-p1 1987/udp cisco RSRB Priority 1 port
  • tr-rsrb-p2 1988/tcp cisco RSRB Priority 2 port
  • tr-rsrb-p2 1988/udp cisco RSRB Priority 2 port
  • tr-rsrb-p3 1989/tcp cisco RSRB Priority 3 port
  • tr-rsrb-p3 1989/udp cisco RSRB Priority 3 port
  • mshnet 1989/tcp MHSnet system
  • mshnet 1989/udp MHSnet system
  • stun-p1 1990/tcp cisco STUN Priority 1 port
  • stun-p1 1990/udp cisco STUN Priority 1 port
  • stun-p2 1991/tcp cisco STUN Priority 2 port
  • stun-p2 1991/udp cisco STUN Priority 2 port
  • stun-p3 1992/tcp cisco STUN Priority 3 port
  • stun-p3 1992/udp cisco STUN Priority 3 port
  • ipsendmsg 1992/tcp IPsendmsg
  • ipsendmsg 1992/udp IPsendmsg
  • snmp-tcp-port 1993/tcp cisco SNMP TCP port
  • snmp-tcp-port 1993/udp cisco SNMP TCP port
  • stun-port 1994/tcp cisco serial tunnel port
  • stun-port 1994/udp cisco serial tunnel port
  • perf-port 1995/tcp cisco perf port
  • perf-port 1995/udp cisco perf port
  • tr-rsrb-port 1996/tcp cisco Remote SRB port
  • tr-rsrb-port 1996/udp cisco Remote SRB port
  • gdp-port 1997/tcp cisco Gateway Discovery Protocol
  • gdp-port 1997/udp cisco Gateway Discovery Protocol
  • x25-svc-port 1998/tcp cisco X.25 service (XOT)
  • x25-svc-port 1998/udp cisco X.25 service (XOT)
  • tcp-id-port 1999/tcp cisco identification port
  • tcp-id-port 1999/udp cisco identification port
  • callbook 2000/tcp
  • callbook 2000/udp
  • dc 2001/tcp
  • wizard 2001/udp curry
  • globe 2002/tcp
  • globe 2002/udp
  • mailbox 2004/tcp
  • emce 2004/udp CCWS mm conf
  • berknet 2005/tcp
  • oracle 2005/udp
  • invokator 2006/tcp
  • raid-cc 2006/udp raid
  • dectalk 2007/tcp
  • raid-am 2007/udp
  • conf 2008/tcp
  • terminaldb 2008/udp
  • news 2009/tcp
  • whosockami 2009/udp
  • search 2010/tcp
  • pipe_server 2010/udp
  • raid-cc 2011/tcp raid
  • servserv 2011/udp
  • ttyinfo 2012/tcp
  • raid-ac 2012/udp
  • raid-am 2013/tcp
  • raid-cd 2013/udp
  • troff 2014/tcp
  • raid-sf 2014/udp
  • cypress 2015/tcp
  • raid-cs 2015/udp
  • bootserver 2016/tcp
  • bootserver 2016/udp
  • cypress-stat 2017/tcp
  • bootclient 2017/udp
  • terminaldb 2018/tcp
  • rellpack 2018/udp
  • whosockami 2019/tcp
  • about 2019/udp
  • xinupageserver 2020/tcp
  • xinupageserver 2020/udp
  • servexec 2021/tcp
  • xinuexpansion1 2021/udp
  • down 2022/tcp
  • xinuexpansion2 2022/udp
  • xinuexpansion3 2023/tcp
  • xinuexpansion3 2023/udp
  • xinuexpansion4 2024/tcp
  • xinuexpansion4 2024/udp
  • ellpack 2025/tcp
  • xribs 2025/udp
  • scrabble 2026/tcp
  • scrabble 2026/udp
  • shadowserver 2027/tcp
  • shadowserver 2027/udp
  • submitserver 2028/tcp
  • submitserver 2028/udp
  • device2 2030/tcp
  • device2 2030/udp
  • blackboard 2032/tcp
  • blackboard 2032/udp
  • glogger 2033/tcp
  • glogger 2033/udp
  • scoremgr 2034/tcp
  • scoremgr 2034/udp
  • imsldoc 2035/tcp
  • imsldoc 2035/udp
  • objectmanager 2038/tcp
  • objectmanager 2038/udp
  • lam 2040/tcp
  • lam 2040/udp
  • interbase 2041/tcp
  • interbase 2041/udp
  • isis 2042/tcp
  • isis 2042/udp
  • isis-bcast 2043/tcp
  • isis-bcast 2043/udp
  • rimsl 2044/tcp
  • rimsl 2044/udp
  • cdfunc 2045/tcp
  • cdfunc 2045/udp
  • sdfunc 2046/tcp
  • sdfunc 2046/udp
  • dls 2047/tcp
  • dls 2047/udp
  • dls-monitor 2048/tcp
  • dls-monitor 2048/udp
  • shilp 2049/tcp
  • shilp 2049/udp
  • dlsrpn 2065/tcp Data Link Switch Read Port Number
  • dlswpn 2067/tcp Data Link Switch Write Port Number
  • ats 2201/tcp Advanced Training System Program
  • ats 2201/udp Advanced Training System Program
  • ivs-video 2232/tcp IVS Video default
  • ivs-video 2232/udp IVS Video default
  • ivsd 2241/tcp IVS Daemon
  • ivsd 2241/udp IVS Daemon
  • rtsserv 2500/tcp Resource Tracking system server
  • rtsserv 2500/udp Resource Tracking system server
  • rtsclient 2501/tcp Resource Tracking system client
  • rtsclient 2501/udp Resource Tracking system client
  • hp-3000-telnet 2564/tcp HP 3000 NS/VT block mode telnet
  • www-dev 2784/tcp world wide web – development
  • www-dev 2784/udp world wide web – development
  • NSWS 3049/tcp
  • NSWS 3049/udp
  • vmodem 3141/tcp VMODEM
  • vmodem 3141/udp VMODEM
  • ccmail 3264/tcp cc:mail/lotus
  • ccmail 3264/udp cc:mail/lotus
  • dec-notes 3333/tcp DEC Notes
  • dec-notes 3333/udp DEC Notes
  • mapper-nodemgr 3984/tcp MAPPER network node manager
  • mapper-nodemgr 3984/udp MAPPER network node manager
  • mapper-mapethd 3985/tcp MAPPER TCP/IP server
  • mapper-mapethd 3985/udp MAPPER TCP/IP server
  • mapper-ws_ethd 3986/tcp MAPPER workstation server
  • mapper-ws_ethd 3986/udp MAPPER workstation server
  • bmap 3421/tcp Bull Apprise portmapper
  • bmap 3421/udp Bull Apprise portmapper
  • prsvp 3455/tcp RSVP Port
  • prsvp 3455/udp RSVP Port
  • vat 3456/tcp VAT default data
  • vat 3456/udp VAT default data
  • vat-control 3457/tcp VAT default control
  • vat-control 3457/udp VAT default control
  • udt_os 3900/tcp Unidata UDT OS
  • udt_os 3900/udp Unidata UDT OS
  • netcheque 4008/tcp NetCheque accounting
  • netcheque 4008/udp NetCheque accounting
  • nuts_dem 4132/tcp NUTS Daemon
  • nuts_dem 4132/udp NUTS Daemon
  • nuts_bootp 4133/tcp NUTS Bootp Server
  • nuts_bootp 4133/udp NUTS Bootp Server
  • unicall 4343/tcp UNICALL
  • unicall 4343/udp UNICALL
  • krb524 4444/tcp KRB524
  • krb524 4444/udp KRB524
  • nv-video 4444/tcp NV Video default
  • nv-video 4444/udp NV Video default
  • rfa 4672/tcp remote file access server
  • rfa 4672/udp remote file access server
  • commplex-main 5000/tcp
  • commplex-main 5000/udp
  • commplex-link 5001/tcp
  • commplex-link 5001/udp
  • rfe 5002/tcp radio free ethernet
  • rfe 5002/udp radio free ethernet
  • telelpathstart 5010/tcp TelepathStart
  • telelpathstart 5010/udp TelepathStart
  • telelpathattack 5011/tcp TelepathAttack
  • telelpathattack 5011/udp TelepathAttack
  • mmcc 5050/tcp multimedia conference control tool
  • mmcc 5050/udp multimedia conference control tool
  • rmonitor_secure 5145/tcp
  • rmonitor_secure 5145/udp
  • aol 5190/tcp America-Online
  • aol 5190/udp America-Online
  • aol-1 5191/tcp AmericaOnline1
  • aol-1 5191/udp AmericaOnline1
  • aol-2 5192/tcp AmericaOnline2
  • aol-2 5192/udp AmericaOnline2
  • aol-3 5193/tcp AmericaOnline3
  • aol-3 5193/udp AmericaOnline3
  • padl2sim 5236/tcp
  • padl2sim 5236/udp
  • hacl-local 5304/tcp
  • hacl-local 5304/udp
  • hacl-test 5305/tcp
  • hacl-test 5305/udp
  • proshareaudio 5713/tcp proshare conf audio
  • proshareaudio 5713/udp proshare conf audio
  • prosharevideo 5714/tcp proshare conf video
  • prosharevideo 5714/udp proshare conf video
  • prosharedata 5715/tcp proshare conf data
  • prosharedata 5715/udp proshare conf data
  • prosharerequest 5716/tcp proshare conf request
  • prosharerequest 5716/udp proshare conf request
  • prosharenotify 5717/tcp proshare conf notify
  • prosharenotify 5717/udp proshare conf notify
  • x11 6000-6063/tcp X Window System
  • x11 6000-6063/udp X Window System
  • softcm 6110/tcp HP SoftBench CM
  • softcm 6110/udp HP SoftBench CM
  • spc 6111/tcp HP SoftBench Sub-Process Control
  • spc 6111/udp HP SoftBench Sub-Process Control
  • meta-corp 6141/tcp Meta Corporation License Manager
  • meta-corp 6141/udp Meta Corporation License Manager
  • aspentec-lm 6142/tcp Aspen Technology License Manager
  • aspentec-lm 6142/udp Aspen Technology License Manager
  • watershed-lm 6143/tcp Watershed License Manager
  • watershed-lm 6143/udp Watershed License Manager
  • statsci1-lm 6144/tcp StatSci License Manager – 1
  • statsci1-lm 6144/udp StatSci License Manager – 1
  • statsci2-lm 6145/tcp StatSci License Manager – 2
  • statsci2-lm 6145/udp StatSci License Manager – 2
  • lonewolf-lm 6146/tcp Lone Wolf Systems License Manager
  • lonewolf-lm 6146/udp Lone Wolf Systems License Manager
  • montage-lm 6147/tcp Montage License Manager
  • montage-lm 6147/udp Montage License Manager
  • ricardo-lm 6148/tcp Ricardo North America License Manager
  • ricardo-lm 6148/udp Ricardo North America License Manager
  • xdsxdm 6558/tcp
  • xdsxdm 6558/udp
  • acmsoda 6969/tcp acmsoda
  • acmsoda 6969/udp acmsoda
  • afs3-fileserver 7000/tcp file server itself
  • afs3-fileserver 7000/udp file server itself
  • afs3-callback 7001/tcp callbacks to cache managers
  • afs3-callback 7001/udp callbacks to cache managers
  • afs3-prserver 7002/tcp users & groups database
  • afs3-prserver 7002/udp users & groups database
  • afs3-vlserver 7003/tcp volume location database
  • afs3-vlserver 7003/udp volume location database
  • afs3-kaserver 7004/tcp AFS/Kerberos authentication service
  • afs3-kaserver 7004/udp AFS/Kerberos authentication service
  • afs3-volser 7005/tcp volume managment server
  • afs3-volser 7005/udp volume managment server
  • afs3-errors 7006/tcp error interpretation service
  • afs3-errors 7006/udp error interpretation service
  • afs3-bos 7007/tcp basic overseer process
  • afs3-bos 7007/udp basic overseer process
  • afs3-update 7008/tcp server-to-server updater
  • afs3-update 7008/udp server-to-server updater
  • afs3-rmtsys 7009/tcp remote cache manager service
  • afs3-rmtsys 7009/udp remote cache manager service
  • ups-onlinet 7010/tcp onlinet uninterruptable power supplies
  • ups-onlinet 7010/udp onlinet uninterruptable power supplies
  • font-service 7100/tcp X Font Service
  • font-service 7100/udp X Font Service
  • fodms 7200/tcp FODMS FLIP
  • fodms 7200/udp FODMS FLIP
  • man 9535/tcp
  • man 9535/udp
  • sd 9876/tcp Session Director
  • sd 9876/udp Session Director
  • isode-dua 17007/tcp
  • isode-dua 17007/udp
  • biimenu 18000/tcp Beckman Instruments, Inc.
  • biimenu 18000/udp Beckman Instruments, Inc.
  • dbbrowse 47557/tcp Databeam Corporation
  • dbbrowse 47557/udp Databeam Corporation


    [RFC768] Postel, J., “User Datagram Protocol”, STD 6, RFC 768, USC/Information Sciences Institute, August 1980.[RFC793]Postel, J., ed., “Transmission Control Protocol – DARPA Internet Program Protocol Specification”, STD 7, RFC 793, USC/Information Sciences Institute, September 1981.



Security Specifications and Initiatives

Throughout the internet community, there are many groups working on resolving a variety of security related issues online.    The activities cover all aspects of internet security and networking in general from authentication, firewalls, one time passwords, public key infrastructure, transport layer security and much more.

Many of the most important security protocols, initiatives and specifications being developed can be researched at the following groups.

TCSEC (Trusted Computer System Evaluation Criteria)

These are requirements for secure products as defined by the US National Security Agency.   These are important standards which many US and global companies use in establishing base lines for their computer and network infrastructure.    You will often hear these standards referred to as the ‘Orange book’.

CAPI (Crypto API)

CAPI is an application programming interface developed by Microsoft which makes it much easier for developers to create applications which incorporate both encryption and digital signatures.

CDSA (Common Data Security Architecture) 

CDSA is a security reference standard primarily designed to help develop applications which take advantage of other software security mechanisms.   Although not initially widely used, CDSA has since been accepted by the Open Group for evaluation and technical companies usch as IBM, Netscape and Intel have aided in developing the standard further.  It is important for a disparate communication medium such as the internet to have open and inter-operable standards for applications and software.   The standard also includes an expansion platform for future developments and improvements in security elements and architecture.

GSS-API – (Generic Security Services API)

The GSS-API is a higher level interface that enables applications and software an interface into security technologies.  For example it can act as a gateway into private and public key infrastructure and technologies.

This list is of course, a long way from being complete and because of the fast paced development of security technologies it’s very likely to change greatly.   It should be remembered that although there is an obvious requirement for security at the server level,   securing applications and software on the client is also important.   Client side security is often more of a challenge due to different platforms and a lack of standards – configuration settings on every computer are likely to be different.

Many people now take security and privacy extremely seriously, especially now that so much of our lives involve online activities.  Using encryption and some sort of IP cloaker like this to provide anonymity is extremely common.  Most of these security services are provided by third parties through specialised software.   Again incorporating these into some sort of common security standard is a sensible option yet somewhat difficult to achieve.

Further Reading: Netflix VPN Problem, Haber Press, 2015

Certificate Based Client Authentication

One of the most important features of SSL is it’s ability to authenticate based on SSL certificates.  Often people fail to understand that this certificate based authentication can only be used when SSL is functioning, it is not accessible in other situations.    Take for example the more common example on the web of insecure HTTP exchanges – this means that SSL certificate based authentication is not available.  The only option here is to control access by using basic username password authentication.  This represents possibly the biggest security issue on the internet today because this also takes place in clear text too!

Another common misconception is with regards the SSL sessions themselves.  SSL sessions are established between two endpoints.  The session may go through a SSL tunnel which is effectively a forward proxy server.    However secure reverse proxying is not SSL tunnelling it’s probably better described as HTTPS proxying although this is not a commonly used term.   In this example the proxy acts as an endpoint of one SSL session, accepting the endpoint of one SSL session and forwarding the request to the origin server.

The two sessions are distinct except of course they will both be present in the cache and memory of the proxy server. An important consequence of this is that the client certificate based authentication credential are not relayed to the origin server.   The SSL session between the client and the reverse proxy server authenticates the client to the proxy server.  However the SSL session between the origin server and the proxy authenticates the server itself.   The certificate presented to the origin server is the reverse proxy’s certificate and the origin server has no knowledge of the client and it’s certificate.

Just to summarise this is the ability to authenticate the client to the origin server though the reverse proxy server.

In these situations where client based certificate based authentication and access control are required, the role would have to be performed by the reverse proxy serve.  In other words the access control function has been delegated to the proxy server.  Currently there is no protocol available for for transferring access control data from the origin server to the reverse proxy server.    However there are situations in advanced networks where the access control lists can be stored in an LDAP server for example in Windows Active directory domains.   This enables all unverified connections to be controlled, e’g blocking BBC VPN connections from  including outbound client requests to the media servers.

The reverse proxy could be described in this situation as operating as a web server.  Indeed the authentication required by the reverse proxy is actually web server authentication not proxy server authentication.    Thus crucially the challenge status code is HTTP 401 and not 407.  This is a crucial difference and a simple way to identify the exact authentication methods which are taking place on a network if you’re troubleshooting.