Either way should work as long as the subnet masks are right. If you are having issues browsing shares but can run them directly "\\machine\share", then you have a master browser issue AFAIK..
Using classic "classful" addressing a private class C network, 192.168.x.y, was /24 (255.255.255.0) subnet mask using one of 256 subnets containing 254 hosts, range from 192.168.0.1 to 192.168.255.254. http://en.wikipedia.org/wiki/Classful_network CIDR on the other hand has shifted 192.168.x.y to a /16 (255.255.0.0) subnet yielding 65534 hosts on a single subnet. http://en.wikipedia.org/wiki/Private_network http://en.wikipedia.org/wiki/RFC_1918 DHSinclair wrote: > Am living through the initial weeks of high-speed bliss. > I may have gone really goofy with my re-address of my > machines. > > Initially, I set up all my clients (4) with a 192.168.2XX.x IP addy. > The subnet mask is 255.255.0.0. > > I then set up my "servers" (4) with a 192.168.2XY.x IP addy. > The subnet mask is 255.255.0.0. > > Yes, my router (1) is in the 192.168.2XY.x range. > My printer (1) is in the 192.168.2XY.x range. > My subnet mask for these two is 255.255.0.0. > > If I sit at a machine on an address of 192.168.2XY.x, I can not > open the net neighborhood 'shares' of w2k machines that are > addressed as 192.168.2XX.x. Is this normal? > > I am now thinking that I need to move everyone to an IP addy in > the 192.168.2XX.x range and change my subnet mask to > 255.255.255.0. > > Your thoughts, reccs, and suggestions are very welcome. > Best, > Duncan __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
