maybe you should torch to see what ports are being used.
maybe you are blocking some ports.
as far as i’ve read on the internet, the netbios uses broadcast packets, maybe it has something to do with that.
Hmmm.. i used connection filter to check on which ports they communicate and i readed manuel for ports that need to be open.
It seems that work only when i check "Any. Port: " in firewall filter option and adding ports there.
Confusing i must tell, by the way does anyone know what Any. Port: mean, i readed somewhere on the internet but is a litle bit confused for me, my english is not so good.
Continueing to wok under this seting i tested windows rdp as an example. I needed to apply on both rule rule for rdp port in order to work but i just wonned to access from one subnet, dont understand why on both rule i must to add this port and to use Any. Port:?
Any help will,would be appreciated for this “anomaly” and making this correct.
You really need to use Torch to see which ports are involved. Also note that while some NetBIOS traffic does indeed use the same port on the client and server many protocols do not do that. If your clients always initiate connections you may want to try allowing NEW connections to a restricted IP/port range on the server subnet but allow all ESTABLISHED & RELATED traffic in the other direction.
I am pretty sure that looking at the above ruleset his problem is that he has no rules with the src-port as 135,136,137 and they aren’t getting picked up by connection tracking…
Op: What is on these ports? And post your whole config… export compact.
On these ports is comunication for windows network. I tried src-port dont work. it only work when is Any. Port: even then i must on both rule to add ports that i wont to open. Confusing.
There is no more configuration except this and default rules for ip address mate.
I trust that there is nothing else… but I just find it easier to see your export… if you want me to look through it post the whole export compact. I have time tonight to figure it out.
That will not work.
The problem is that when a client make a season on that port with server, user use some other port on his side, and when you apply reverse rule server also use another port on his side beside that 135,136,137 etc.
An when rules above or mine apply then they block other ports on they side. got it mate ?
Oh,
quick from the head…
ip firewall rule chain forward connection state established action accept
ip firewall rule chain forward connection state releated action accept
Am i correct ?
