Have you taken a look to make sure that the local firewalls on each of the computers are allowing file/print sharing traffic through?

Yes, of course each computer requires a unique IP address on the network. If you have a router, then it should have the DHCP service running and assigning your clients a dynamic IP address.

Just to validate, go to each computer, open a command prompt and type ipconfig.

You should see the IP address for each PC. I would assume that they will be configured on the 192.168.0.x network. If not, that's OK, but you want to make sure that all of your PCs all share the first three octects (a.b.c.?). The last number needs to be unique for each computer on the subnet.

Once you validate the IPs, you should be able to PING each other. PING 192.168.1.1 for example..

Of course, your local firewall on each computer would have to allow ICMP packets (PING) to traverse the firewalls.

AS long as the one NIC has an IPv4 address that's OK. The others will show disconnected because you have no cable plugged into it. As a best practice, I always disable the unused NICs from Control Panel --> Network Connections.

It's good to know that you like research. Check that all of the computers are set to the same Workgroup, and that the folders you would like to see on the other computers are set as shared on those computers

Hai, kindly run me through the process of setting up a simple network of 3 or 4 computers that are running on the same OS i.e Windows 7,iving limitations and tests that would indicate that the computers are properly pinged.

@SammyN,

It appears that you are a new member of this community. You may consider starting your own threads when you have a question, or need assistance, rather than hijacking someone's elses thread.

Error 0x80070035 simple means "Network Path Not Found" which is what your problem is. It could be a variety of issues such as network connectivity, a name resolution issue, NetBIOS over TCP/IP, or firewall related.

I am still not clear on your basic network health. I've asked if you are able to PING each of the computers. I do not beleive that you have validated that this is the case. Can you ping by IP and by Name?

If its name resolution related, you should be able to access the share by supplying the target computer's IP address in the UNC path.

For example, instead of trying \computer1\sharename, try \ipaddress\sharename.

I wish that I could provide you with more help but I'm not sure what else I can add that would be of value.

With regard to ipconfig, you may not be understanding the information that is displayed on the screen. When you open a command prompt and type ipconfig, this command will display the IP configuration for the network adapters for that single computer. If you have multiple adapters (physical and logical), you will get results for all of them. If you only have one cable plugged in, then all of the other adapters will show as "media disconnected". That is OK. The point of using ipconfig on your computers was just to validate that each computer has an IP address and they are all on the same logical network.

So, i would suggest to take a step back. Not being to access network shares could be prevented by a large number of issues. When troubleshooting network problems, you start low in the OSI model and work your way up to the application layer.

The first thing you need to validate is network connectivity for all of your hosts. This is where PING comes into play. From one of the computers, are you able to PING all of the rest of them? If you are not familiar with PING, i have a guide you can review.
Using PING to Test for Network Connectivity

I'm assuming that this is all done and your network is OK.

Once you have established that your network connectivity is OK, then the next step is to troubleshoot this at a higher layer.

Box(B) can see the folder I want to share from Box(A) but I cannot access the folder from Box(B)

What do you mean by that statement. You can see the folders on Box(A) from Box(B), but you cannot access the folders. So when you browse to computerA, you can see the shares? If you click on a folder, you get the error? Does this happen from all of the other computers, or just this one? If its only one computer, what is different about the configuraiton on this computer? NetBIOS settings, firewall?

I think he may need to look at the permissions on those folders. The way to test if it is a matter of permissions is to log into the shared PC using an account on that computer via the network. We need to ask about his Router, make and model.

However, setting up a network of computers running Windows 7 is normally a straightforward affair, as CaperJack points to in his post. Microsoft also provided a simplistic method for setting up a network. Please be careful about making too many tweaks as there is something glaringly obvious about this problem, and you may find yourself trying to workout which tweaks to undo afterwards, or tweaks that will impact on something else down the line. There must be one basic factor to effect all of the Computers simultaneously.

Has the option/setting of Simple File Sharing been considered?

@JorgeM You have asked him to Ping other computers including the address 192.168.1.1 - that IP address is typically the Router's address, would you agree? Has he assigned any of his computers with that address?

I'm just concerned that this is being over-complicated.

I agree that the suggestions I have provided so far could be overly complicated if Siberian is not familiar with these TCP/IP utilities.

With regard to the IP 192.168.1.1, it was just an example. If you really wanted to find out what the IP address is of the router, just get that information from IPCONFIG. It will be the address listed for the Default Gateway.

I am trying to keep this as simple as possible, but when dealing with application layer errors, there may be half a dozen things going on.

I would agree that the best course of action is to stop at this point, locate a Windows 7 Networking guides (the one that BigPaw linked to is a good start) and go from there.