User Monitoring System Using LAN

User Monitoring System Using LAN

Khandagale Tejas1, Mojad Ajit2, Khan Hafiz3, Betal Shubrato4 , Mr. Pankaj Chandre

1,2,3,4 Department of Computer Engineering, SPCOE-412409, Pune University,

Abstract The project aims to develop various network utilities which are required to effectively monitor a user activities using LAN network. It aims to develop an integrated software solution that allows a network administrator to remotely monitor his users and their daily activities through LAN.

This function allows obtaining detailed information about the activities your employees are engaged into during their working hours, and also create statistical reports with important data. For a more detailed observation of the activities occurring on user computers, Software takes snapshots at pre-set intervals inconspicuously for the user and saves them into a database chronologically. A quick gallery view of these snapshots gives full information about all users activities.

Index Terms J2EE, LAN, FTP, RMI, REMOTE CONTROL.

1. INTRODUCTION

   The primary goal of the project is to remotely handle the monitoring system of client pc connected in the LAN . With the ever growing computer networks it has become challenging job for an IT professional to manage the network resources and the monitoring. In such environments, it becomes an administrative task to carefully manage the task for every client with using the snapshot. Remote monitoring system and LAN Controlled user in client pc with the help of user client some of the existing services that may already be deployed and in use within an organization, as well as adds some additional services that one may or may not be familiar with. Monitoring of the system can be used to deploy Operating system and requested softwares by the clients on their PC from the server without even interrupting the client after processing their request. An administrator can roll out a new version of the operating system to hundreds, even thousands of users at one time, and do so from its remote location. LAN Controlled can be used to handle Remote processes and remote operation of clients.

   With the ever growing computer networks it has become challenging job for an IT professional to manage the network resources and monitoring all system is very difficult task. In such environments, it becomes a administrative task of monitoring system of need. The Remote Host Monitoring System is an Application Software, which help us to monitoring the users remotely on LAN. The main benefit of this software is that an administrator can sit on server computer and can view the details about the users computer connected to his system. In propose system the server is provided with the privileges to monitor any of its client systems with the help of snapshot.

   The Design of proposed system is to be used on the remotely handle monitoring and is used to monitor and record user activity.

   Fig: LAN Architecture

2. FEATURES CONTROLLED BY SYSTEM

   1. SNAPSHOT:

      Capture the snapshot of user desktop and transfer it to server.

      Server takes the snapshots and stores the snapshots in separate directory automatically.

   2. PROCESS VIEW:

      Get the lists of all processes running in the remote machine Also admin has an authority to control all the processes and he can add new process if needed or kill the unauthorized process.

   3. PC CONTROL:

      Admin can control the user pc remotely

      Server has authority to restart, hibernate, shutdown the user computer.

   4. MESSAGE PASSING:

      Admin can send message to the user computer The message is appear like the popup

      The message is either broadcast or sends to particular user only.

   5. REMOTE DESKTOP ACCESS:

   The server can access the user desktop remotely

   It has only select the user IP address and access the user desktop. Admin can watch the user activity directly to server side.

3. ARCHITECTURE OF PROPOSED SYSTEM

   Fig: Architecture of proposed system

   In the above system architecture number of client in same LAN network connected to the centralize server that is main server of our system. And also storage server connected to the main server. The UMS access the user data remotely with the help of remote control logic. The Admin which have a controls of all functionality of UMS is present at the server side only.

   The following are list of conventions and acronym used in this document and the project.

   User: user who will connect in the LAN

   Interface: LAN is used to communicate across different sides.

   UMS: User Monitoring System

   LAN-UMI: User Monitoring Interface

   SRS: Software Requirements Specification

   User: User of the system such as customer, client, employee, visitor. Anyone who can interact with the system using the user interface layer (LAN).

4. BLOCK DIAGRAM OF PROPOSED SYSTEM

   From the block diagram of proposed system we see that from user side SNAPSHOT is send to server through LAN network. At server there is a individual directory in which the each snapshot is save after the seleted time. All the active user list is available to the server always. Server can manages the monitoring time and user by concidering their IP address. At the user side every individual user must have to login and

   accept the server connection request at beginning. After the selected time period the snapshot are saved at server and he is able to access them any time during monitoring. The above mentioned features are provided for every server side installation at server only. This block diagram of UMS is gives basic idea regarding the system flow.

   There is no any database maintained there is only one temporary database or we can say file. Through database we get the data we needed.

   Fig: Blockdiagram of propose system

5. TECHNOLOGY USED IN PROPOSED SYSTEM

   In User Monitoring System we use technology like

   1. FTP/LAN:

      By using FTP protocol in these system we communicate with client and server.

   2. NET BEANS: For better and efficient programming we use net beans for designing this system.

   3. PROCESS BUILDER: This class is used in this system which is very important to create operating system processes.

   4. ABSTRACT WINDOW TOOLKIT: This is javas toolkit used for windowing sets, graphics and graphical user interface creation for this system.

   5. J2EE: It is collection of java programming APIs used for java platform based programs which is used to program this system.

6. INTERFACES

   1. User Interface

      • Every user must connect to LAN and having own IP address.

      • Must keep the Allow remote access settings ON.

      • Provide the access from firewall to trust the network.

   2. Software Interface

      • Its an client server architecture software

      • Two different installations are required at both client and server site.

      • Authentication is must require for server machine.

      • None of activity is performed by user for start monitoring.

      • Its a combination of different java programs which require the operating system support for running the application.

   3. Hardware Interface

   • Standalone system

   • Processor : Dual Core

   • RAM : Minimum 1 GB

   • HDD : Minimum 80 GB

   • LAN connection Switches and Hubs

FUTURE WORKS

The future enhancements in the system include

LAN monitoring and control whenever the administrator is not present at station. This application decrese the time as well as efforts of administrator.

7. APPLICATIONS OF PROPOSED SYSTEM

   • Totally unaware from the user.

   • Its always connected so that information is available every time.

   • High integrity and security.

   • Ability to incorporate fresh and newly available data.

   • It is user friendly

   • Speed and accuracy is increased

   • Fully automated.

   • Security is provided with user authentication

   • Duplication of information is curbed.

   • No need of Internet for monitoring.

   • Required very less storage according to previous monitoring systems.

   • Provides various controls of user system.

   • Additional functionality of Message send/broadcast.

8. CONCLUSIONS