3129 port- danger?

From: James Raaymakers MCSe (jamesraa@pacbell.net)
Date: 02/06/03 

From: "James Raaymakers MCSe" <jamesraa@pacbell.net>
Date: Thu, 6 Feb 2003 14:45:01 -0800

OOpps....wrong App. Here it is as an attachment.
>-----Original Message-----
>Hello, recently I checked my server using netstat, found
that someone was
>listening on TCP 3129 port and 1026 port, is it dangerous
or some kind of
>trojan?
>
>Thanks!
>
>
>.
>

Relevant Pages

  • Re: 2 Default instances on Active/Active
    ... on a different TCP port and/or pipe name. ... on a separate node, and each is listening on TCP 1433, whenever a failover ... for both cluster and stand-alone systems with ...
    (microsoft.public.sqlserver.clustering)
  • Re: Netstat results - problem?
    ... listening corresponding to a port. ... Luca Vix Visconti wrote: ... >> Have I a trojan or does this look like normal netstat logs? ...
    (comp.security.misc)
  • Re: ISA2004 with SBS2003 Web Proxy Bind Error
    ... already using the same port or by a network adapter that is not functional. ... The failure is due to error: ... TCP sbs2003:nameserver sbs2003.sbs.local:0 LISTENING 2312 ...
    (microsoft.public.windows.server.sbs)
  • Re: Cant connect to Terminal Services following upgrade of Win 2003 to service pack 1
    ... Is the server listening on port 3389? ... - an" at a command prompt. ... I've done a netstat -an and it says that port 3389 is ...
    (microsoft.public.windows.terminal_services)
  • Re: Why does DNS.EXE listen on a ephemeral TCP port?
    ... Right, but when my name server makes a query to another name server, ... via UDP to my server and then my server originates a TCP connection. ... server) I understand why my server listens on a UDP port, ... don't think this explains why my server is LISTENING on a TCP port. ...
    (microsoft.public.windows.server.dns)