netbios
Results 1 to 5 of 5

Thread: netbios

  1. #1
    Junior Member
    Join Date
    Sep 2002
    Posts
    14

    netbios

    I ran a scan against one of my win2k boxes here at work and it comes up with a port 139 which is the netbios on tcp. Now when i try to connect via net use \\xxx.xxx.xxx.xxx\ipc$ it tells me my box isnt found? I have a firewall so i assume my box is safe from netbios attacks. i assume right>?

  2. #2
    Senior Member
    Join Date
    Feb 2002
    Posts
    856

    Re: netbios

    Originally posted here by cerealbowl
    I ran a scan against one of my win2k boxes here at work and it comes up with a port 139 which is the netbios on tcp. Now when i try to connect via net use \\xxx.xxx.xxx.xxx\ipc$ it tells me my box isnt found? I have a firewall so i assume my box is safe from netbios attacks. i assume right>?
    Hrrrm,
    If you have a firewall working, a port scan shouldn't find port 139. Were you scanning the win2k box from another computer-- or from the same computer?
    For the wages of sin is death, but the free gift of God is eternal life in Christ Jesus our Lord.
    (Romans 6:23, WEB)

  3. #3
    A portscan on localhost [127.0.0.1] will always reveal open ports since a firewall doesnt block ports, but close them.... And your computer is almost always set as a trusted zone (usually under 0.0.0.0)

  4. #4
    Junior Member
    Join Date
    Sep 2002
    Posts
    14
    remote scan from my home to work box. fire wall inbetween.

  5. #5
    Junior Member
    Join Date
    Sep 2002
    Posts
    18
    Your Firewall should stealth all your ports when scanned remotely (with the possible exception of 80)



    Disabling Services

    Disabling NetBIOS
    http://support.microsoft.com/default...EN-US;q137368&
    http://support.microsoft.com/default...EN-US;q313314&
    http://www.jsifaq.com/SUBL/tip5500/rh5558.htm

Posting Permissions

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