Just something that's always evaded my comprehension. I always use the 192.168.0.0 - 192.168.255.255 range for internal networks. Usually the first 9 reserved for servers (.1-.10) and the rest clients. From all the documentation I've read this is a Class B network (16 bit), and to use it I should netmask 255.255.0.0.
I was at a customer's the other day who uses the 192.168.1.x range. I put a pre-prepared Linux box (RH7.2 if it matters) down there, with my usual 192.168.0.1 ip set-up, but the clients just would not connect to it. Not even ping it. The client's netmask WAS set to 255.255.0.0, so my question is this: Can a client at let's say 192.168.1.x with netmask 255.255.0.0 connect to a server at 192.168.0.1 with netmask 255.255.0.0? I've never pondered this before because as I said, I normally use the 192.168.0 range only, but in this case, I had to change the server to 192.168.1 range to make it work, when, from what I understand, I shouldn't have had to. In the end it's all good and works, but why not with the 192.168.0 range? I realise it's a different sub-net, but the mask should take care of that no? Can anyone please kindly refer me somewhere that explains in plain English what I'm misunderstanding? TIA -- Edward Dekkers (Director) Triple D Computer Services Pty. Ltd. _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
