Somehow over the past two CPF updates (I’m now on 2.3.5.62), I’ve lost the ability to share files & folders over my home network. I can see the shared folders that I’d previously been using, but they now give me the “resource is unavailable” error.
I have added my network as Trusted in CPF on each of my PC’s. Internet access works, but none of the PC’s can “see” each other anymore.
If I try to add a new Network Place, each PC sees only itself in the MSHOME network browse.
Everything was OK a few days ago using 2.2.0.11, with its default settings. I’m sure it’s something I haven’t set right, but I just can’t figure it out.
I’m attaching a JPG of my current rules, in case it’s helpful. Any suggestions are most welcome!
Posted by: bmuse
Somehow over the past two CPF updates (I’m now on 2.3.5.62), I’ve lost the ability to share files & folders over my home network. I can see the shared folders that I’d previously been using, but they now give me the “resource is unavailable” error. –When CPF is turned off, are you still able to share files and see other PCs ?
If I try to add a new Network Place, each PC sees only itself in the MSHOME network browse. –Try WORKGROUP - This is usually the default except when changed.
I’m attaching a JPG of my current rules, in case it’s helpful. Any suggestions are most welcome! – The rules looks alright to me though.
Your rules are correct. Do you have “Security->Advanced->Miscellaneous->Block all outgoing connections while booting” option enabled? IF so, make sure to disable it.
IF not, can you please paste us tyour CPF logs so that we can see what is happening?
i am having the same problem – can’t even see the shared folders or computers
Block all outgoing connections while booting – is not checked
laptop running comodo firewall
other computer is running ZA free version
the only way i am able to share is by turning off the network monitor
please help
UPDATE:
well, i don’t know what has changed – but i am able to see other computers on my network and can access them, so i guess issue is solved (:SHY)
but a new issue has come up – has nothing to do with comodo firewall – my other computers can’t access the network any more, they are behaving wierdly, it may be ZA, not sure though,
may be i will install comodo firewall on them as well
I’m probably barking up the wrong tree with my very limited knowledge of networking but I took a look at my CPF rule and I notice a difference from yours.
My IP addresses are 192.168.1.0/192.168.1.255. You have a zero in the third position. Could that be your problem?
I assume you are behind a router. I thought the IP’s given by the router were like mine and not yours.
You have: 192.168.1.0/192.168.1.255
He has : 192.168.0.0/192.168.0.255
They’re both correct !
The set of addresses that most home users are familiar with is the private range 192.168.0.0 through 192.168.255.255, which is 256 blocks of 256 addresses. Each block of 256 addresses (count them!) is what used to be called a “Class C” block. Note that your private network can be on any of 256 Class C blocks, from 192.168.0.0 through 192.168.255.0. If you want to be “different,” you can pick any valid number for that third byte, not just zero.
Every computer that communicates over the Internet is assigned an IP address that uniquely identifies the device and distinguishes it from other computers on the Internet. An IP address consists of 32 bits, often shown as 4 octets of numbers from 0-255 represented in decimal form instead of binary form.
For example, the IP address
168.212.226.204
in binary form is
10101000.11010100.11100010.11001100.
But it is easier for anyone to remember decimals than it is to remember binary numbers, so, hence why decimals are being use to represent IP addresses when describing them. However, the binary number is important because that will determine which class of network the IP address belongs to. An IP address consists of two parts, one identifying the network and one identifying the node, or host. The Class of the address determines which part belongs to the network address and which part belongs to the node address. All nodes on a given network share the same network prefix but must have a unique host number.
Class A Network – binary address start with 0, therefore the decimal number can be anywhere from 1 to 126. The first 8 bits (the first octet) identify the network and the remaining 24 bits indicate the host within the network.
An example of a Class A IP address is 102.168.212.226, where “102” identifies the network and “168.212.226” identifies the host on that network.
Class B Network – binary addresses start with 10, therefore the decimal number can be anywhere from 128 to 191. (The number 127 is reserved for loopback and is used for internal testing on the local machine.) The first 16 bits (the first two octets) identify the network and the remaining 16 bits indicate the host within the network.
An example of a Class B IP address is 168.212.226.204 where “168.212” identifies the network and “226.204” identifies the host on that network.
Class C Network – binary addresses start with 110, therefore the decimal number can be anywhere from 192 to 223. The first 24 bits (the first three octets) identify the network and the remaining 8 bits indicate the host within the network.
An example of a Class C IP address is 200.168.212.226 where “200.168.212” identifies the network and “226” identifies the host on that network.
Class D Network – binary addresses start with 1110, therefore the decimal number can be anywhere from 224 to 239. Class D networks are used to support multicasting.
Class E Network – binary addresses start with 1111, therefore the decimal number can be anywhere from 240 to 255. Class E networks are used for experimentation.