FAX Free

• Port Monitor 1 3 3 – Monitor System Tcp Ip Network Connections Extender
• Portsmonitor 1 3 3 – Monitor System Tcpip Network Connections Configuration

Port Monitor 1 3 3 – Monitor System Tcp Ip Network Connections Extender

RS232 Port Monitor comes with a slew of powerful features, including advanced filtering and search options, built-in terminal, convenient data visualizers, the ability to record serial communication data to a file, and more. The software has a streamlined and user-friendly interface and doesn’t require any programming skills. After the data transmission process is over, TCP automatically terminates the connection between two separate endpoints. Summary TCP 3-way handshake or three-way handshake or TCP 3-way handshake is a process which is used in a TCP/IP network to make a connection between server and client. Syn use to initiate and establish a connection. Capsa Free is a network analyzer that allows you to monitor network traffic, troubleshoot network issues and analyze packets. Features include support for over 300 network protocols (including the ability to create and customize protocols), MSN and Yahoo Messenger filters, email monitor and auto-save, and customizable reports and dashboards. SmartSniff - Capture TCP/IP packets on your network adapter SocketSniff - Windows Sockets (WinSock) Sniffer See Also. NK2Edit - Edit, merge and fix the AutoComplete files (.NK2) of Microsoft Outlook. Description CurrPorts is network monitoring software that displays the list of all currently opened TCP/IP and UDP ports on your local computer. Axence nVision 12.0.1.30105. Our Rating: User Rating: Popularity: 6 Axence nVision is a network management suite that combines network monitoring and visualization, hardware and software inventory, intelligent user monitoring (and website blocking), data leak protection and remote desktop.

Port monitors consist of user-mode DLLs. They are responsible for providing a communications path between the user-mode print spooler and the kernel-mode port drivers that access I/O port hardware. A port monitor typically uses the CreateFile, WriteFile, ReadFile, and DeviceIOControl functions, described in the Microsoft Windows SDK documentation, to communicate with kernel-mode port drivers. Port monitors are also responsible for management and configuration of a server's printer ports, as described in Managing a Port.

An NT-based-operating system user's view of a 'printer' is really a print queue, to which one or more physical printer devices can be connected. A port is the physical connection between the print queue and a single printer device. Each port monitor supports one or more instances of one or more types of ports. For example Localmon.dll, the sample port monitor, can support all of a server's local COM and LPT ports. (The print folder assigns ports to port monitors by calling the Windows SDK documentation's AddPrinter function.)

For print queues representing multiple printer devices (through multiple ports), the spooler sends each print job to the first available port. If the port monitor indicates that a specified port is busy or has encountered an error, the spooler resubmits the job to the queue, specifying another port supported by the port monitor.

Besides Localmon.dll, Windows 2000 and later operating system versions provide several additional port monitors. The Windows 2000 Server Resource Kit describes each of these port monitors. (This resource may not be available in some languages and countries.)

Customized port monitors can be written to support additional types of I/O port hardware.

For Windows 2000 and later, each port monitor is divided into two DLLs:

Port Monitor UI DLL
A port monitor's user interface DLL contains user interface functionality and executes on print client systems.

This DLL must reside in the client system's System32 subdirectory.

Port Monitor Server DLL
A port monitor's server DLL contains port communications functionality and executes on print servers. It must not display a user interface.

The UI DLL communicates with the server DLL by calling the spooler's XcvData function.

A sample port monitor is included in the Windows Driver Kit (WDK).

1. Technical Field

The present invention relates to security in a network computer environment. More specifically, the present invention relates to security in computer networks which use several TCP/IP ports.

2. Description of Related Art

As applications become increasingly net-centric, myriad TCP/IP ports are tapped to provide various functions undreamed of only a few years ago. Numerous applications now communicate via obscure, but dedicated, TCP/IP ports and accordingly, provisions must be made within each system to allow connections upon these ports as warranted. If this increase in port nomenclature and usage were not enough to confound security, the boundaries between “secured” and “unsecured” are becoming more difficult to fathom as well, as the old model of a bastion firewall marking the border between a hostile outside and a benign corporate environment is increasingly outmoded.

This blurring of the lines can be demonstrated firstly by the incorporation of multiple web-servers, and even multiple domains, within the “secure” side of organizational firewalls. As outsiders are permitted electronic entry into an organization through designated TCP/IP ports, the old “outside-is-dangerous, inside-is-safe” model breaks down. Furthermore, organizations are increasingly subject to multiple levels of security even within their firewalls; examples of this are school districts, which need deterrents not only from the outside world, but also between the student-accessible computers and the administrative computers housing grades and student records.

It is clear that old security paradigms based upon a singular, well-controlled entry point into an organization now solve only part of the problem. It is also apparent that new security methods must be developed to safeguard systems as individual entities, given this new level of complexity inherent in system's models.

Because of the ambiguities between which subnetwork, machines and directory structures are safe and which are not, the solution should exist on the individual systems themselves. Secondly, because each unique system is going to be tasked with primary job responsibilities, it is of great importance that the systems not be loaded with any CPU-intensive processes in monitoring port usage upon its own system. Minimizing the impact of such a monitoring tool upon any jobs running on the targeted system is paramount. Security must not be accompanied by significant reduction in the performance of the host systems.

Currently, solutions exist only at the firewall, with the limitations described above, or at the host level, with heavy demands upon the resources of the target system. Therefore, a port monitoring method that can be implemented on the individual client computers in a network, but does not add an undue processing burden, would be desirable.

The present invention provides a method for monitoring incoming data from an external computer network. The invention comprises polling all active port connections in a data processing system at regular intervals and comparing these connections to a table of authorized ports and IP addresses. Any unauthorized connections are logged and a network administrator is notified. The present invention can be implemented on clients within a computer network.

The novel features believed characteristic of the invention are set forth in the appended claims. The invention itself, however, as well as a preferred mode of use, further objectives and advantages thereof, will best be understood by reference to the following detailed description of an illustrative embodiment when read in conjunction with the accompanying drawings, wherein:

FIG. 1 depicts a pictorial representation of a distributed data processing system in which the present invention may be implemented;

FIG. 2 depicts a block diagram of a data processing system which may be implemented as a server, in accordance with the present invention;

FIG. 3 depicts a block diagram of a data processing system in which the present invention may be implemented; and

FIG. 4 depicts a flowchart illustrating a method for synchronous port monitoring, in accordance with the present invention.

With reference now to the figures, and in particular with reference to FIG. 1, a pictorial representation of a distributed data processing system is depicted in which the present invention may be implemented.

Distributed data processing system 100 is a network of computers in which the present invention may be implemented. Distributed data processing system 100 contains network 102, which is the medium used to provide communications links between various devices and computers connected within distributed data processing system 100. Network 102 may include permanent connections, such as wire or fiber optic cables, or temporary connections made through telephone connections. Connections are made via pathways, known as ports into and out of computers. In the depicted example, server 104 is connected to network 102, along with storage unit 106. In addition, clients 108, 110 and 112 are also connected to network 102. These clients, 108, 110 and 112, may be, for example, personal computers or network computers.

For purposes of this application, a network computer is any computer coupled to a network that receives a program or other application from another computer coupled to the network. In the depicted example, server 104 provides data, such as boot files, operating system images and applications, to clients 108-112. Clients 108, 110 and 112 are clients to server 104. Distributed data processing system 100 may include additional servers, clients, and other devices not shown. Distributed data processing system 100 also includes printers 114, 116 and 118. A client, such as client 110, may print directly to printer 114. Clients such as client 108 and client 112 do not have directly attached printers. These clients may print to printer 116, which is attached to server 104, or to printer 118, which is a network printer that does not require connection to a computer for printing documents. Client 110, alternatively, may print to printer 116 or printer 118, depending on the printer type and the document requirements.

In the depicted example, distributed data processing system 100 is the Internet, with network 102 representing a worldwide collection of networks and gateways that use the TCP/IP suite of protocols to communicate with one another. At the heart of the Internet is a backbone of high-speed data communication lines between major nodes or host computers consisting of thousands of commercial, government, education, and other computer systems that route data and messages. Of course, distributed data processing system 100 also may be implemented as a number of different types of networks such as, for example, an intranet or a local area network.

FIG. 1 is intended as an example and not as an architectural limitation for the processes of the present invention.

Referring to FIG. 2, a block diagram of a data processing system which may be implemented as a server, such as server 104 in FIG. 1, is depicted in accordance with the present invention. Data processing system.200 may be a symmetric multiprocessor (SMP) system including a plurality of processors 202 and 204 connected to system bus 206. Alternatively, a single processor system may be employed. Also connected to system bus 206 is memory controller/cache 208, which provides an interface to local memory 209. I/O bus bridge 210 is connected to system bus 206 and provides an interface to I/O bus 212. Memory controller/cache 208 and I/O bus bridge 210 may be integrated as depicted.

Peripheral component interconnect (PCI) bus bridge 214 connected to I/O bus 212 provides an interface to PCI local bus 216. A number of modems 218-220 may be connected to PCI bus 216. Typical PCI bus implementations will support four PCI expansion slots or add-in connectors. Communications links to network computers 108-112 in FIG. 1 may be provided through modem 218 and network adapter 220 connected to PCI local bus 216 through add-in boards.

Additional PCI bus bridges 222 and 224 provide interfaces for additional PCI buses 226 and 228, from which additional modems or network adapters may be supported. In this manner, server 200 allows connections to multiple network computers. A memory mapped graphics adapter 230 and hard disk 232 may also be connected to I/O bus 212 as depicted, either directly or indirectly.

Those of ordinary skill in the art will appreciate that the hardware depicted in FIG. 2 may vary. For example, other peripheral devices, such as optical disk drives and the like, also may be used in addition to or in place of the hardware depicted. The depicted example is not meant to imply architectural limitations with respect to the present invention.

The data processing system depicted in FIG. 2 may be, for example, an IBM RS/6000, a product of International Business Machines Corporation in Armonk, New York, running the Advanced Interactive Executive (AIX) operating system.

With reference now to FIG. 3, a block diagram of a data processing system in which the present invention may be implemented is illustrated. Data processing system 300 is an example of a client computer. Data processing system 300 employs a peripheral component interconnect (PCI) local bus architecture. Although the depicted example employs a PCI bus, other bus architectures, such as Micro Channel and ISA, may be used. Processor 302 and main memory 304 are connected to PCI local bus 306 through PCI bridge 308. PCI bridge 308 may also include an integrated memory controller and cache memory for processor 302. Additional connections to PCI local bus 306 may be made through direct component interconnection or through add-in boards. In the depicted example, local area network (LAN) adapter 310, SCSI host bus adapter 312, and expansion bus interface 314 are connected to PCI local bus 306 by direct component connection. In contrast, audio adapter 316, graphics adapter 318, and audio/video adapter (A/V) 319 are connected to PCI local bus 306 by add-in boards inserted into expansion slots. Expansion bus interface 314 provides a connection for a keyboard and mouse adapter 320, modem 322, and additional memory 324. In the depicted example, SCSI host bus adapter 312 provides a connection for hard disk drive 326, tape drive 328, CD-ROM drive 330, and digital video disc read only memory drive (DVD-ROM) 332. Typical PCI local bus implementations will support three or four PCI expansion slots or add-in connectors.

An operating system runs on processor 302 and is used to coordinate and provide control of various components within data processing system 300 in FIG. 3. The operating system may be a commercially available operating system, such as AIX, which is available from International Business Machines Corporation. “AIX” is a trademark of International Business Machines Corporation. An object oriented programming system, such as Java, may run in conjunction with the operating system, providing calls to the operating system from Java programs or applications executing on data processing system 300. Instructions for the operating system, the object-oriented operating system, and applications or programs are located on a storage device, such as hard disk drive 326, and may be loaded into main memory 304 for execution by processor 302.

Those of ordinary skill in the art will appreciate that the hardware in FIG. 3 may vary depending on the implementation. For example, other peripheral devices, such as optical disk drives and the like, may be used in addition to or in place of the hardware depicted in FIG. 3. The depicted example is not meant to imply architectural limitations with respect to the present invention. For example, the processes of the present invention may be applied to multiprocessor data processing systems.

Referring now to FIG. 4, a flowchart illustrating a method for synchronous port monitoring is depicted in accordance with the present invention. The example presented in FIG. 4 is based on a tool called portmon, which was developed by IBM. However, the present invention can be implemented in other formats and is not restricted to the portmon tool. Also note that, although the invention as described and detailed in this example was implemented upon UNIX systems, the concept behind the invention can be implemented with operating system-dependent syntax modifications to any computational device which accepts TCP/IP connections.

Most hacker methodologies achieve entry on arcane ports. In fact, hacking tools exist which scan the range of TCP ports, from outside the target system, to search for security weaknesses. Thus, portmon runs on the target client to monitor entry into obscure TCP/IP ports.

Portmon is initiated synchronously, that is, at regular intervals which are determined by the network administrator (step 401). For purposes of this example, it will be assumed that portmon is run once a minute via crontab, on its UNIX implementation. A crontab is a file of instructions that executes commands at a set time or time interval.

Once portmon has been initiated, it looks to see that the necessary lookup table is installed on the system (step 402). The lookup table contains information about permitted IP addresses and the ports which they may access. If the lookup table is not properly installed, an email is sent to the network administrator and the script exits (step 410).

If the lookup table is properly installed, portmon proceeds to examine all active ports (step 403). After polling an active port, portmon moves on to the next port connection (step 404). A note is made concerning each active port connection and the foreign address from which the connection has occurred (step 405). To reduce the processing load, all self-referential connections are ignored. Self-referential connections are created when different parts of the same system must communicate with each other. Since they do not represent a threat from the outside world, all lines which have identical local and foreign addresses are dropped from consideration.

For a given port connection, portmon consults the lookup table and finds what range of addresses are allowed to make such connections (step 406). If the connection is from a known-good port and a permitted address, portmon simply continues to the next connection entry (step 409).

If a given connection is from an illicit port, or from a known-good port, but from an illicit address, this fact is noted in an output log (step 408). After making this note, portmon then continues to the next connection entry (step 409).

Portsmonitor 1 3 3 – Monitor System Tcpip Network Connections Configuration

Steps 404 through 409 are repeated until all active port connections have been polled. At the completion of the port survey, portman compiles all problems entered into the output log (if any)(step 410) and then sends an email to the administrator (step 411). The administrator email address can be contained within the body of the script itself. This location can also be changed to either a command line argument or a file-invoked address, which could initiate an automatic response.

Prior art approaches to providing security at the client level require constant monitoring of the contents of incoming traffic, which requires substantial processing. The present invention simply relies upon a synchronous “snapshot” of the connection ports and foreign IP addresses which are compared with a predefined lookup table, requiring far less processing resources. The present invention also relieves the network administrator from having to rely solely upon a firewall to screen the network from the outside world. By monitoring security at the client level, without imposing heavy processing loads on the target system, the present invention increases data security with a minimum of operator intervention and a minimum in performance degradation.

It is important to note that while the present invention has been described in the context of a fully functioning data processing system, those of ordinary skill in the art will appreciate that the processes of the present invention are capable of being distributed in the form of a computer readable medium of instructions and a variety of forms and that the present invention applies equally regardless of the particular type of signal bearing media actually used to carry out the distribution. Examples of computer readable media include recordable-type media, such as a floppy disk, a hard disk drive, a RAM, CD-ROMs, DVD-ROMs, and transmission-type media, such as digital and analog communications links, wired or wireless communications links using transmission forms, such as, for example, radio frequency and light wave transmissions. The computer readable media may take the form of coded formats that are decoded for actual use in a particular data processing system.

The description of the present invention has been presented for purposes of illustration and description, and is not intended to be exhaustive or limited to the invention in the form disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art. The embodiment was chosen and described in order to best explain the principles of the invention, the practical application, and to enable others of ordinary skill in the art to understand the invention for various embodiments with various modifications as are suited to the particular use contemplated.