Network security is the new buzzword in the city.Most people think a network firewall that is configured by default with the protection of network. The simple fact that no. Not until hack you know this fact. Of course, this comes a bit late. All Operating Systems need to open ports to communicate information about Active Directory, DNS, DHCP, boot a computer and more. Some applications need to open ports work. So where do you get to a safe spot where job applications and are safe. The following ports will address the work and what concerned. Later I will discuss how to secure it.

The ports are concerned about those 3,389 port terminal services. If you do not have a firewall in place blocking the public Forwarding IP address to the private IP address using this port, then To call the security professional. Other ports in question are about 139 that provides access to network shares.

Another area of concern is the SMB or
(Server Message Block) protocol. This protocol is used among other things,
file sharing in Windows NT/2000/XP. In Windows NT is implemented on top of NetBT
(NetBIOS over TCP / IP), which uses the famous ports 137, 138 (UDP) and 139 (TCP).
In Windows 2000/XP/2003, Microsoft added the ability to run SMB directly
through TCP / IP, without the extra layer of NetBT. It uses TCP port 445.
Once again all these ports should remain in the private network and firewall
must block access.

Note: The NETSTAT command will show
what ports are open or in use, but is not a port scanning tool! If
wants his team scanned for open ports to see this page instead (link
shortly.)

C: netstat>-an | find / i “listening”

TCP 0.0.0.0:135 0.0.0.0:0 LISTENING

TCP 0.0.0.0:445 0.0.0.0:0 LISTENING

TCP 0.0.0.0:1723 0.0.0.0:0 LISTENING

TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING

TCP 127.0.0.1:1026 0.0.0.0:0 LISTENING

TCP 127.0.0.1:4664 0.0.0.0:0 LISTENING

192.168.50.127:139 0.0.0.0:0 LISTENING TCP

192.168.100.193:139 0.0.0.0:0 LISTENING TCP

The netstat command also displays currently active on the computer. This
show what spyware or Trojan horses that may be installed on your machine.

Active Connections

Proto Local Address Foreign Address State

TCP argon: argon EPMAP: 0 LISTENING

TCP Argon: microsoft-ds Argon: 0 LISTENING

TCP argon: argon pptp: 0 LISTENING

TCP argon: argon 3389: 0 LISTENING

TCP argon: argon 1026: 0 LISTENING

argon TCP: 2617 localhost: 2618 ESTABLISHED

argon TCP: 2618 localhost: 2617 ESTABLISHED

Argon TCP: 2619 localhost: 2620 ESTABLISHED

argon TCP: 2620 localhost: 2619 ESTABLISHED

Argon TCP: 4664 Argon: 0 LISTENING

TCP argon: argon NetBIOS-SSN: 0 LISTENING

argon TCP: 2958-in-one f104.google.com: http ESTABLISHED

Argon TCP: 3011 is on f104.google.com: http TIME_WAIT

argon TCP: 3014 eo-in-f147.google.com: http ESTABLISHED

Argon TCP: 3081 unknown.xeex.net: http TIME_WAIT

argon TCP: 3104 unknown.xeex.net: http ESTABLISHED

Argon TCP: 3903 web1.allaboutsingles.com: http CLOSE_WAIT

argon TCP: 4449 static-71-116-207-166.lsanca.dsl-w.verizon.net: pptp ESTABLISHED

TCP Argon: 4762 runs f104.google.com: http CLOSE_WAIT

TCP argon: argon NetBIOS-SSN: 0 LISTENING

argon TCP: 2939 192.168.100.202:1025 ESTABLISHED

argon TCP: 2957 exchange01.intercore.local: 1419 ESTABLISHED

Once you have blocked all ports, then it must be
concerned about internal security. Nobody in your organization will be allowed
talk to anyone about any information safe. Even granting there email
direction. Then, use devices such as honey pots, Barracuda spam appliance Symantec
hardware and antivirus software. A properly configured network can allow your
workers to work and not allow hackers to work.