Microsoft CIFS (TCP) Closed Connection

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

I'm using SBS 2004. I got the following message in my log.

Destination port: 445 Protocol: Microsoft CIFS(TCP) Action: Initiated
Connection

Destination Port: 445 Protocol: Microsoft CIFS (TCP) Action: Closed
Connection.

I already ensure that the access rule is set up for port 445 and ensure
the destination being "LocalHost". I have 2 rules for this.. One is
the system. The other one is standard access rule.

What could cause this port open and closed immediatley?

Does this "open and close" has anything to do with Certificate?
I didn't set the certificate up yet.

Thanks in advance,

PL

.

Relevant Pages

  • iptables blocking DNS resolution, web browsing, ftp...etc.
    ... Accept If protocol is TCP and input interface is eth2 and destination port ...
    (alt.linux)
  • Microsoft CIFS(TCP) Close Connection
    ... Destination port: 445 Protocol: Microsoft CIFSAction: Initiated ... Connection ... Destination Port: 445 Protocol: Microsoft CIFS Action: Closed ...
    (microsoft.public.windows.server.sbs)
  • Never seen this before?
    ... PROTOCOL: UDP ... DESTINATION HOST: 24.76.248.XXX ... DESTINATION PORT: 500 ...
    (comp.security.firewalls)
  • RE: firewall question
    ... connection complies with a valid protocol, ... and not just depending on the destination port. ... I have a question regarding stateful inspection firewalls ... This list is provided by the SecurityFocus Security Intelligence Alert ...
    (Pen-Test)
  • iptables firewall problems.
    ... I use iptables firewall. ... ESTABLISHED indicates that the packet is associated with a connection ... or source or destination port. ...
    (comp.os.linux.misc)