Results 1 to 8 of 8

Thread: Microsoft-ds event in Firestarter

  1. #1
    Join Date
    Aug 2006
    Location
    The Zoo
    Beans
    150
    Distro
    Ubuntu 10.04 Lucid Lynx

    Microsoft-ds event in Firestarter

    Hello,

    We've seen some events in Firestarter lately on one of the networks I work on.

    They say they are attempts to connect from a Windows computer that shares the same router, using Microsoft-ds on Port 445 and TCP Port 80.

    That originating Windows computer does not have file and printer sharing activated however. No networking or filesharing is set up, just a shared router.

    Is that cause for concern or is there a legitimate reason why that might happen?

    Thanks in advance,

    lemuriax

  2. #2
    Join Date
    Aug 2006
    Location
    The Zoo
    Beans
    150
    Distro
    Ubuntu 10.04 Lucid Lynx

    Re: Microsoft-ds event in Firestarter

    Maybe this is the wrong forum for this, sorry if so...

  3. #3
    Join Date
    Aug 2006
    Location
    The Zoo
    Beans
    150
    Distro
    Ubuntu 10.04 Lucid Lynx

    Red face Re: Microsoft-ds event in Firestarter

    *bump*

    can we move this to the right forum too ?

  4. #4
    Join Date
    Sep 2007
    Beans
    68
    Distro
    Ubuntu 7.10 Gutsy Gibbon

    Re: Microsoft-ds event in Firestarter

    Do you have samba installed on machine that is the destination of the traffic? If so, then the traffic is probably Windows doing it's SMB stuff.

    Windows is very chatty-- even if you don't have file and printer sharing enabled, it may still try to connect over 445, so I wouldn't worry about that Other services- Fax Service, License Logging Service, Server service, Net Logon Service, Remote Procedure call locator, all go over 445 on later versions of Windows.

    The port 80 traffic is a puzzler. There is an "RPC over HTTP" service, so it may be that or it may be Windows Media player or other piece going out and looking for a home. Or it may be some other software like AOL IM or something like that on the Windows box.

    On the Windows box, you can try a netstat -anb to see if anything odd pops up there (the -b flag only works with newer versions of windows and shows the process behind a network connection or listener)

    I hope this helps
    Sean T Murray

  5. #5
    Join Date
    Aug 2006
    Location
    The Zoo
    Beans
    150
    Distro
    Ubuntu 10.04 Lucid Lynx

    Re: Microsoft-ds event in Firestarter

    Thanks for the reply.

    I do have the smbclient, libsmbclient library, and samba-common files installed though have never done anything with them yet. That's good to know that it's probably just Windows checking on SMB stuff - the Windows computer never triggered these events before the other day but perhaps an update to XP changed it's behaviour in this regard. The Port 80 events happen at the same time as the SMB events, usually when booting up and going online for the day, also new behaviour...

    I ran the netstat -anb command and don't see anything out of the ordinary as far as I can tell.

  6. #6
    Join Date
    Nov 2005
    Location
    Nashville, TN
    Beans
    437
    Distro
    Ubuntu 14.04 Trusty Tahr

    Re: Microsoft-ds event in Firestarter

    Nothing that strange. Windows is very chatty. It will continuously try to locate other machines and advertise it's presence on a network. It would be easier if you had something like a wireshark capture to determine what the packets were.
    -Chayak

  7. #7
    Join Date
    Nov 2006
    Location
    40.31996,-80.607213
    Beans
    Hidden!
    Distro
    Ubuntu

    Re: Microsoft-ds event in Firestarter

    It is most likely just Windows sending out requests to find other shares.
    There should be nothing harmful with it, in itself.
    "Security lies within the user of who runs the system. Think smart, live safe." - Dr Small
    Linux User #441960 | Wiki: DrSmall

  8. #8
    Join Date
    Aug 2006
    Location
    The Zoo
    Beans
    150
    Distro
    Ubuntu 10.04 Lucid Lynx

    Re: Microsoft-ds event in Firestarter

    Okay thanks for the input everyone, I appreciate it.

    And sorry if I was impatient at first, was just a wee bit concerned as this behavior is new on that particular network. I will look into installing wireshark capture or something like that to further study up on packet analysis.

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •