Re: [Port 1198]

From: H Carvey (keydet89@yahoo.com)
Date: 04/05/03

  • Next message: Dave: "SQL tracing" 
    Date: 5 Apr 2003 13:36:18 -0000
From: H Carvey <keydet89@yahoo.com>
To: security-basics@securityfocus.com
    ('binary' encoding is not supported, stored as-is) In-Reply-To: <004901c2fa8a$b04bbe60$3c00680a@AM2EU.DE>

    Wolfgang,

    >I have a log at my Firewall, which I can not resolve.
    >Does anyone have information about software using Port
    1198 ?
    >
    >2003/04/03 12:47:48 ** TCP SYN Flooding ** <IP/TCP>
     10.104.0.80:1198 ->>
    >212.65.0.186:80
    >
    >I couldn't find anything on the net so far.

    What exactly are you looking for? 1198 is the source
    port, and it's above 1024 (ie, within the range used by
    clients). Knowing this...what are you trying to find.
     Any client application (web browser, port scanner,
    etc) can use this port...

    -------------------------------------------------------------------
    SurfControl E-mail Filter puts the brakes on spam,
    viruses and malicious code. Safeguard your business
    critical communications. Download a free 30-day trial:
    http://www.securityfocus.com/SurfControl-security-basics

  • Next message: Dave: "SQL tracing"

    Relevant Pages

    • Re: adding machine to domain with NATed IPs
      ... sounds that the DCs are not reaching the clients ... weight 100, port 389, target srv5.mydomain.local ...
      (microsoft.public.windows.server.active_directory)
    • Re: adding machine to domain with NATed IPs
      ... sounds that the DCs are not reaching the clients ... Type: SRV (Service location) ... weight 100, port 389, target srv5.mydomain.local ...
      (microsoft.public.windows.server.active_directory)
    • Re: DDoS to microsoft sites
      ... The primary difference between the two clients is that the first port scan I ... > - netbios (brute force attack on Administrator account) ... I'm guessing that the SQL server is the infection vector in both these ...
      (Incidents)
    • Re: Help need desperately!
      ... Changing from port 80 is not required. ... Inventory information began flowing properly. ... All of the clients seemed to install with the new ... >> found our problem to be in our TCP port configuration on the Server. ...
      (microsoft.public.sms.inventory)
    • Re: adding machine to domain with NATed IPs
      ... sounds that the DCs are not reaching the clients or vice versa? ... weight 100, port 389, target srv5.mydomain.local ...
      (microsoft.public.windows.server.active_directory)
    • Quantcast