Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsWindows Server 2003Windows 2000Windows NTSmall Business ServerVirtual ServerExchange ServerIISHost Integration ServerISA ServerSMSWSUSMOMWindows Media ServerSecurityCertification
Related Topics
SQL ServerMS WindowsMS OfficePC HardwareMore Topics ...

Windows Server Forum / Windows Server 2003 / Security / June 2005

Tip: Looking for answers? Try searching our database.

Closing / stealthing ports on 2003

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
TC - 28 Jun 2005 04:09 GMT
Hello,

   I just starting testing GFI LANguard and did a scan on some computers
and I am noticeing open ports and ones that are not mentioned in NetStat.

   What I am wondering is how can I stealth ports or at least close them?
Also, I know of some sites that tell port numbers but they are ganeric. Are
there any that are specific to windows.

   I want to make sure I don't turn the wrong things off. Since some of
these systems are DC's and other servers.
Signature

Thank you,

TC

Please reply to the newsgroup so we can all learn from others.
Thanks.

Steven L Umbach - 28 Jun 2005 05:35 GMT
First off a firewall should be used at the perimiter to protect your network
from unwanted access. Beyond that you can either close ports by disabling
the service or application that uses them or block them with a host based
firewall. You can use free utilties like TCPView and Process Explorer from
SysInternals to find what application or service is using a particilar port.
The commands netstat -ano, netstat -anb, and tasklist /svc will also be
helpful in seeing what executeables and process ID's are associated with a
port. Tasklist /svc will show what services are associated with an instance
of svchost. Ipsec policy can also be used to restrict access to ports on a
computer with either an ipsec filtering policy or with an ipsec negotation
policy that requires computer authnetication before access is allowed to a
computer on the ports restricted by ipsec.

http://www.microsoft.com/windowsserver2003/technologies/networking/ipsec/default.mspx  
--- Windows 2003 ipsec

Use the free tool Microsoft Baseline Security Analyzer to check for
vulnerabilites on your computer including services that may not be needed.
The Windows 2003 Server Security Guide also has excellent information on
what services should be enabled on servers by role and also recommendations
for ipsec filtering policy. If you are using SP1 you can take advantage of
the Security Configuration Wizard as shown in the first link below to help
configure your servers with only the needed services and to implement an
ipsec filtering policy.   --- Steve

http://www.microsoft.com/windowsserver2003/technologies/security/configwiz/defau
lt.mspx

http://www.microsoft.com/technet/security/tools/mbsahome.mspx  --- MBSA
http://support.microsoft.com/default.aspx?scid=kb;en-us;832017   --- Windows
Server ports
http://www.microsoft.com/technet/security/prodtech/windowsserver2003.mspx    
--- TechNet Security for windows 2003

> Hello,
>
[quoted text clipped - 7 lines]
>    I want to make sure I don't turn the wrong things off. Since some of
> these systems are DC's and other servers.
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2010 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.