I cant acces other LAN machines services from my win7 witch CIS firewall enabled, no http, ssh , nothing.
to test it i decided using netcat, so i set up a listener on my linux machine , added nc as a trusted app and the network as a trusted network. but when i try to connect it simply dont get any of the answers from my linux machine (i used wireshark on both machines and compared, on my win7 only the requests were there and on my linux i could see both requests and replies), no logs of any block were created.
after that i changed the netcat policy to also log whenever it allowed any connection, the results were the same, no replies from my linux machine, but now the log shows the allowed connection, still no blocked ones.
When i disable the firewall everything works fine.
I also tried setting the listener on my win7 and connect to it from the linux and it worked too! the connection completed as it should with the same firewall settings as before.
The linux machine is actually a VM in bridged mode (as far as i know it should be working as any other machine in the LAN)
any ideias? (sorry about any english mistakes, hopefully you can understand all i meant to say)
All right jus tried to connect to a real computer and it worked fine.
Now at least i know the problem is using the LAN with a VM , but i still have no ideia how to fix it =/
any ideias?
Im using vmware workstation version 8.0.0 build-471780
i tried with different machines, linux and windows and the results were always the same, tried reinstalling comodo, and still the same…
You need to make the required local network a trusted network. You can follow the tutorial I will provide after this. For VM ware you need to adapt the network address range in which VM Ware operates (it is not the default 192.168.1.x range).
How to make your local network a trusted zone.?
First look up your IP address and subnet mask. In Windows go to Start → Run → cmd → enter → ipconfig → enter → now lookup your IP address and subnet mask.
Second create a zone in My Network Zones (Firewall → Network Security policy). Choose Add → A New Network Zone → fill in a name like My local network → Apply. Now select My Local Network Zone → Add → A new address → choose An IP Address Mask → fill in your local IP something like 192.168.1.x usually and your subnet mask; usually 255.255.255.0 → Apply. Now check and see the new network defined. Exit using Apply.
Now we are going to use the Stealth Ports Wizard to make your local network a trusted network:
Choose “Define a new trusted network and stealth my ports to EVERYONE else” → Next → choose “I would like to trust an existing My Network Zone” → choose your local network zone from the drop down box at the bottom → Finish.
Now check your Global Rules and see your network added.
i guess my english is worse than i thought…
EricJH
i did change my global rules, i did trust my LAN nothing worked, actually On real machines i have no problem at all, and if i try to make my host machine as host everything works fine
i do believe its ome kind of bug realated to vmware bridged connections
fireall is configured , but i still cant get replies,…it doesnt matter wah kinda rules i have , real machines works pretty fine,
i tried making a global rule allowing everything,it didnt work though
CIS log doesnt show anything as blocked, it simply doesnt get the ACK packets, i do believe its some kind of bug with the way vmware manages the bridged connections.
When i set up to log whenever netcat app rule accepted a connection it jus showed up an allowed connection, no blocked ones.
If i set a listener on the host machine (the win7 whith comodo one), i can connect from the VMs normally, the issue is only when im connecting from the host to the VMs
even with an allow everything global rule the results were the same
It looks like we may be looking at a bug. If you have the time and energy please consider filing a bug report in the Bug Reports - CIS board following the format as described in FORMAT & GUIDE - just COPY/PASTE it!.
Reporting of bugs is strictly moderated to make sure Comodo gets clear bug reports. So, please make sure you closely follow protocol. That way your report will certainly be seen by Comodo staff.