inline below.........
At 09:27 11/01/2007 -0700, you wrote:
You can use 10.0.0.1, 10.10.10.1, 10.30.20.1 or any other ip series you
want. I just think that you have to use one of the subnet masks mentioned
in my previous post that per subnet limits you to 254 or less hosts.
Yes, the plan always was to limit hosts to 254 or less. I did realize how
big the class A series was. In my case, it just seems to work better than
class B or class C. Yes, I remain confused about this a bit.
Technically a Class A network would have a default subnet mask of
255.0.0.0. When assigning your router an IP of 10.0.0.1 and a subnet mask
of 255.255.255.0 you're still creating a subnet with a maximum of 254
hosts whose ip address would have to be in a range of 10.0.0.1-10.0.0.254.
Thank you. This is what I thought and how I proceeded way back in 1999.
This is the "pairing" I have always used since moving to w2k/XP.
Functionally this should be no different than using a Class C address with
the 192.168.x.x ip series. I don't know any reason why one would seem any
slower than the other. I'm curious what you mean about being slow or glitchy??
Hmm. OK. Perhaps my IP addy change process is broken. What I did was go to
each LAN client/server and use the Control Panel applet to change the IP
addy from its' old class A address to its' new class C address. Close the
applet and then run cmd/ipconfig /all to check for typos. Go to next
client..... I did not reboot the clients or server, because w2k/XP does not
seem to require this. Perhaps I blew it here......
Once all the clients/servers/router had their new class C IP addy's, I
would use the Network Neighborhood function to test the connection between
the machines. When addressed in class C, all machines would "stall"
opening their shares. Not very long, but there was a noticeable delay
before the remote machine displayed its' shares. For the first week of
class C, I wrote this delay off to each machine rebuilding its' routing
table and/or other internal TCP/IP business. Perhaps my bad!
And, I even thought maybe my two switches may be adding latency since they
had only been/switched class A addresses since new. Hmm. The only way I
know to reset a consumer switch is to PO-PO. I have never been able to talk
directly to either of my switches (netgear fs-508 and netgear fs-308)
Once I returned everyone to my old class A address scheme
(10.0.0.x/255.255.255.0) all of my clients/server/router returned to
popping open their shares instantly. The LAN seems to back to its' normal
spiffy, speedy, state.
I am willing to admit an amount of PEBCAK is involved.
By using a Class A address you would just be expanding the theoretical
maximum capacity of your private network. A full Class A network subnetted
as 255.255.255.0 would create 65536 subnets. I suppose if you had that
many $30 routers from Best Buy you could create a private network with
over 16 million hosts.
OOOOH. What a possible power trip.... Unfortunately I don't have the space
or $$$ for this! Interesting idea however. Believe I will pass........ :)
I think in some legacy equipment from... say twenty years ago or more,
when this stuff was dreamed up, the logic about class a, b, and c networks
would have been hardcoded to some degree. I don't think these kind of
designations mean much when creating a private lan.
Yes, I though so too. But, as I have seen routers get so much smaller,
more intelligent, and feature rich, I feared that I needed to move to the
network address scheme the router came default (192.168.0.1). So, I tried.
Results were poor, but worked sort of.
Initial:
Clients were assigned addy's of 192.168.218.x
Servers were assigned addy/s of 192.168.219.x
Router assigned addy of 192.168.0.1
Printer assigned addy 192.168.219.60
Subnet mask used was 255.255.0.0
Result: Clients could talk to clients, servers talked to servers. Clients
and servers could not talk to each other......... this made my ESET AV
updates on the LAN stop! Hmm. Pilot error!
(first email to the List!)
Next Try:
Clients were assigned addy's of 192.168.218.x
Servers were assigned addy/s of 192.168.218.x
Router and printer assigned addy's of 192.168.218.x
Subnet mask used was 255.255.255.0
Result: Everybody now talks to everybody else, but inter-machine latency is
noticeably long. Hmm. This is very odd. But everybody talks to each other,
sort of.
(2d email to the List!)
Current:
Clients were assigned addy's of 10.0.0.2-99
Servers were assigned addy/s of 10.0.0.100-199
Router assigned addy of 10.0.0.1
Printer assigned addy of 10.0.0.254
Subnet mask used by all is 255.255.255.0
Result: Everybody now talks to everybody else at normal LAN speed.
Inter-machine latency is not an issue at all.
I am still reading over your explanation of subnet qualification via the
4th octet of the netmask. Think I'm going to make it into a chart for the
wall! This has been a very instructive 2.5 weeks. I am smarter now with
your shares, and the shares of j maccraw, but I am still really afraid to
try the class C IP addy series. It just does not seem to work here.
Perhaps something very subtle on my LAN, and I have not found it in the
last 8 years. And, I freely admit it is my fault. The machines are so much
"smarter" than I feel sometimes. LOL!
Best,
Duncan
-Tharin O.
DHSinclair <[EMAIL PROTECTED]> wrote:
OK. I understand. I will again attempt to apply a class C network
strategy. Even though the LAN runs very much better using class A with a
full (25.255.255.0) netmask. Even the router is happy at
10.0.0.1/255.255.255.0.
