Re: Windows 2003 Domain Controller (Open Port 593)



Any ideas?

netmon wrote:
I have just set up a new Windows 2003 domain controller and after
setting up the DC I ran a quick nmap scan of the box and have two open
ports which concern me. They are ports 593 and 1026. I did a quick
Google and port 593 (opened by svchost.exe) is related to
http-rpc-epmap and port 1026 (opened by lsass.exe) is related to
lsa-or-nterm. I do not have RPC over http proxy enabled and just to
make sure I have doubled checked this by going to add/remove windows
components/networking services and RPC over HTTP Proxy is not enabled.
My question is how can I remove these or are they necessary services
needed by the OS. I do not have an Exchange environment.

.



Relevant Pages

  • Re: Win32 The RPC server is unavailable
    ... WMI errors the seem to be RPC related. ... Usually RPC errors are due to name resolution or blocked ports. ... Microsoft MVP - Directory Services ... Instead of the website you're using, I suggest to use OEx (Outlook Express ...
    (microsoft.public.windows.server.networking)
  • Re: RPC ports over a firewall
    ... > 1) Does the RPC need to be restricted to a static port on ServerB as well ... you restrict RPC to a small number of ports. ... UDP 88 Kerberos Authentication ...
    (microsoft.public.windows.server.active_directory)
  • Re: dcpromo failed
    ... way to lock rpc down to specific ports and keep high ports turned off. ... MVP - Directory Services ... I disjoined the server from the domain. ...
    (microsoft.public.windows.server.active_directory)
  • Re: RCP/HTTPS on SBS 2003 Server
    ... Certianly not needed for RPC over HTTP. ... Did you open the correct ports on your server's router as well? ... So we know all the server components are installed> correctly. ...
    (microsoft.public.windows.server.sbs)
  • Re: Windows Ports when used on DMZ
    ... When I was doing testing, the absolute minimum was - RPC with 1 static port, ... DNS (UDP only is sufficient if no long response is expected), ... > than likely your problem is with dynamic RPC in that you are finding ports ... > 1025-1030 being dropped by your firewall. ...
    (microsoft.public.security)