some computers don't show in shared folder

November 9, 2010 at 11:34:58
Specs: Windows XP pro sp3, Intel Core 2 - 6600@2.4gz / 1.97gb
My network has 3 computers and 1 wireless router (192.168.1.1 / 255.255.255.0). Computer 1 (nic=192.168.1.101 / 255.255.255.192) is hardwired to router, computer 2 (nic=192.168.1.129 / 255.255.255.192 and wireles nic=192.168.1.102 / 255.255.255.192) is wireless to router, and computer 3 (nic= 192.168.1.130 / 255.255.255.192) is hardwired to computer 2. All 3 computers have their drives shared, all are on the same workgroup and network bridge is enabled on computer 2. All 3 computers can access the router and the world wide web.Computer 2 lists only itself and computer 1 in the shared network folder but. will communicate with computers 1 & 3. Computer 3 lists only itself but, will communicate only with computer 2. Computer 1 lists itself and computer 2 but, will only communicate with computer 2. All 3 computers will ping each other.

See More: some computers dont show in shared folder

Report •


#1
November 9, 2010 at 12:15:31
Why isn't computer 3 connected to the router? Shouldn't the subnet mask be 255.255.255.0 ?

How do you know when a politician is lying? His mouth is moving.


Report •

#2
November 9, 2010 at 12:28:37
Computer 3 has neither a wireless nic or a network cable to the router. I used
subnet 255.255.255.192 because I really have 2 networks connected together at computer 2.

Report •

#3
November 9, 2010 at 12:32:34
Why are you using subnet mask 255.255.255.192?
this only gives you a range of
192.168.1.1 to 192.168.1.62 which clearly your 101,129,130 are not in.

Solution: use the correct subnet mask or reduce your ips to the supported subnet mask ip range

why did you do this?
"network bridge is enabled on computer 2"

Update:
OK now that question has been answered you don't use that subnet mask because you have two networks.
You use a different ip range.

So on one nic you have 192.168.1.x and on the other you would use 192.168.0.x.
All subnet masks should be 255.255.255.0 in your case and you would engage ICS between the two nics on the host machine.

Update; you may find this link helpful for your future ip planning
http://www.subnet-calculator.com/

another FYI is that you need netbios over tcp/ip enable [tcp/ip properties/wins tab]
BTW with this setup computer1 won't be able to contact computer3 but computer3 should be able to contact computer1

Good luck!

How to properly post a question: http://tinyurl.com/2fsqqmu


Report •

Related Solutions

#4
November 9, 2010 at 12:42:59
My understanding of subnet 255.255.255.192 gives me connections for upto 4 networks. #0 = 001-062, #64 = 065-126, #128 = 129-190, #192 = 193-254.

Computer 2: network #64 = wireless nic to router and computer 1
network #128 = hardwire network to computer 3


Report •

#5
November 9, 2010 at 14:17:52
What does 4 different networks have to do with your situation?

There is this thing called supernetting where you can combine ip ranges like when you have grown from a single class c but don't need a class b. You can combine two class c address ranges together into one subnet.

You are doing exactly the opposite of that. You are taking a single class c subnet and dividing it into 4 networks. This is usually done to separate the networks.

Where is this coming from? What made you think having 3 networks, one on each pc would accomplish what you want?

BTW the solution is simple. You have two choices.

Keep existing subnet mask but only use ips 2-63
Keep existing ips and use subnet mask 255.255.255.0

Then every pc will see each other. I am surprised to learn wireless supports promisious mode which is why bridging is working for you. Last I heard this mode wasn't supported on wireless.

How to properly post a question: http://tinyurl.com/2fsqqmu


Report •

#6
November 9, 2010 at 17:33:10
I vote for choice #2. change the subnet mask.

Wanderer. you touched on something. Do I understand you correctly that promiscuous mode isn't supported by wireless at all? If so, is it due to Windows or the NIC manufacturer?

For example, if I run Wireshark in promiscuous mode on a Windows machine listening on a wireless interface, it never seems to actually put the NIC in promiscuous mode.

How do you know when a politician is lying? His mouth is moving.


Report •

#7
November 10, 2010 at 13:46:04
I had run into the same thing you had and after a little web searching put it down to wireless not supporting promiscuous mode. This is also why most of the wired<>wireless docs talk about ICS vs bridging that I have read. Things keep changing!

How to properly post a question: http://tinyurl.com/2fsqqmu


Report •


Ask Question