Nessus tells me to close ports on my XPHE and W3K3 boxes, including specificying registry settings to do so. I am a newbie to the registry. Can anyone point me to a quality document/book for learning how the registry works and how to use it, AND how to close/open TCP/UDP ports, and disable/enable associated services on XPHE and W2K3 machines? Thanks!

Re: how to close ports by g-w

g-w
Mon Jun 07 16:46:07 CDT 2004

jbiddlew wrote:
> Nessus tells me to close ports on my XPHE and W3K3 boxes, including specificying registry settings to do so. I am a newbie to the registry. Can anyone point me to a quality document/book for learning how the registry works and how to use it, AND how to close/open TCP/UDP ports, and disable/enable associated services on XPHE and W2K3 machines? Thanks!

Are you using a firewall? If not, why not? Firewalls will stop any
incoming or outgoing packts unless you tell the firewall to allow the
application to send and receive packets. Unsolicited Internet packets
will be rejected. Ports will be open when the applications need them and
closed when they are closed.

g-w

Re: how to close ports by FE-FR

FE-FR
Mon Jun 07 16:53:22 CDT 2004

Ports are opened as soon as an application (or service) asked the Winsock
stack to open it.

You can download FPORT from
http://www.foundstone.com/index.htm?subnav=resources/navigation.htm&subcontent=/resources/intrusion_detection.htm
so you will be able to know what service is behind whatever port opened...
and so how to close it.

Anyway you can install a firewall on the machine itself if you have security
issues...

Hope this helps

FE
"jbiddlew" <anonymous@discussions.microsoft.com> wrote in message
news:B22F0627-1FBD-4CC2-BB31-B84AA0C46898@microsoft.com...
> Nessus tells me to close ports on my XPHE and W3K3 boxes, including
specificying registry settings to do so. I am a newbie to the registry.
Can anyone point me to a quality document/book for learning how the registry
works and how to use it, AND how to close/open TCP/UDP ports, and
disable/enable associated services on XPHE and W2K3 machines? Thanks!



Re: how to close ports by anonymous

anonymous
Mon Jun 07 17:36:04 CDT 2004

I run fport 2.0 on my W2K3 box, it give me a header line only
"PID Process Port Proto Path" but no info on ports that Nessus says are open
Any thought on why this output and other tools? My understanding is that Fport only reports but does not open or close ports. Does anyone know of any tools for closing and opening ports on W2K3 and XPHE? Thanks!

Re: how to close ports by Eric

Eric
Mon Jun 07 19:56:37 CDT 2004


"jbiddlew" <anonymous@discussions.microsoft.com> wrote in message
news:43D71AE7-9BEE-4DAF-819B-514FA7B6A855@microsoft.com...
> I run fport 2.0 on my W2K3 box, it give me a header line only:
> "PID Process Port Proto Path" but no info on ports that Nessus says
are open.
> Any thought on why this output and other tools? My understanding is that
Fport only reports but does not open or close ports. Does anyone know of any
tools for closing and opening ports on W2K3 and XPHE? Thanks!

Ports are opened because running services request the ports from the OS. To
close ports, find what service is using the port and disable the service.
What ports are you worried about, maybe someone can tell you what service to
disable?


--
Eric Chamberlain, CISSP




Re: how to close ports by Sadie

Sadie
Mon Jun 07 21:52:24 CDT 2004

Try reading this guide as a gentle introduction.It will
assist you in closing down extraneous services (assuming
you are reasonably certain that you are not using them.)
You are quite sensible not to mess about in the registry
until you are confident of what you are doing.

http://www.blackviper.com/WinXP/servicecfg.htm

Sadie
>-----Original Message-----
>
>
>jbiddlew wrote:
> > Nessus tells me to close ports on my XPHE and
W3K3 boxes, including specificying registry settings to
do so. I am a newbie to the registry. Can anyone point
me to a quality document/book for learning how the
registry works and how to use it, AND how to close/open
TCP/UDP ports, and disable/enable associated services on
XPHE and W2K3 machines? Thanks!
>
> ----- g-w wrote: -----
> Are you using a firewall? If not, why not? Firewalls
will stop any
> incoming or outgoing packts unless you tell the
firewall to allow the
> application to send and receive packets.
Unsolicited Internet packets
> will be rejected. Ports will be open when the
applications need them and
> closed when they are closed.
>
> g-w
>
>jbiddlew wrote:
>yes, am using a perimiter firewall and hostbased
firewalls that are "application aware". But firewalls
can be hacked and malware can enter by other means, so
I'd like to shut down unnecessary ports. There must be a
tool out there to close Windows TCP/UDP ports. Should I
have to be mucking around with the registry to close
ports? Thanks in advance for your advice.
>
>
>.
>