Jump to content
Posted 17 January 2012 - 01:40 AM
Posted 17 January 2012 - 07:12 AM
A big thanks to Dider Stevens
sorry for not being around
Posted 17 January 2012 - 12:54 PM
Your firewall must have SMART FILTERING like mine does which means SOMETHING ON YOUR END IS ASKING FOR THIS CONNECTION.. (Otherwise it should be blocked)
Why is my firewall sending out UPD to ports 137 and 139? When I add a block to the rules it doesn't block them it keeps allowing it to pass.
Edited by 4dude, 17 January 2012 - 12:55 PM.
Posted 17 January 2012 - 07:11 PM
If the client has NetBT enabled, it will always try to connect to the server at both port 139 and 445 simultaneously. If there is a response from port 445, it sends a RST to port 139, and continues it's SMB session to port 445 only. If there is no response from port 445, it will continue it's SMB session to port 139 only, if it gets a response from there. If there is no response from either of the ports, the session will fail completely.
If the client has NetBT disabled, it will always try to connect to the server at port 445 only. If the server answers on port 445, the session will be established and continue on that port. If it doesn't answer, the session will fail completely. This is the case if the server for example runs Windows NT 4.0.
If the server has NetBT enabled, it listens on UDP ports 137, 138, and on TCP ports 139, 445. If it has NetBT disabled, it listens on TCP port 445 only.
The Internet is so big, so powerful and pointless that for some people it is a complete substitute for life.
Andrew Brown (1938-1994)
A learning experience is one of those things that say, "You know that thing you just did? Don't do that." Douglas Adams (1952-2001)
"Imagination is more important than knowledge. Knowledge is limited. Imagination circles the world." Albert Einstein (1879-1955)
Posted 17 January 2012 - 10:26 PM
0 members, 0 guests, 0 anonymous users