It's not about what I've thought about doing.. just things that people may have found out while doing it.. something that surprised them, snags.. etc..
I mean, I have my entire transition mapped out device by device.. but maybe someone found out that certain software no longer worked correctly, etc..
Ive had a really good think about this one but surely, chaging the subnet mask on every device on the network from 255.255.255.0 to 255.255.0.0 will do the trick????
well it'll be more complicated than that, as I am actually going to be using a private IP range.. so it'll be more than just the subnet mask..
But I also have to manually change the IPs on all servers, printers, etc.. as well as the DNS, WINS, DHCP stuff on the servers. My networking equipment will change as well..
Just wondered if anyone has ran into any problems related to changing from a Class C to a Class B.
Ok I presumed you were using for example 44.0.0.0 on a class C and want to expand to 44.0.0.0 on a class B, however your going from 192.168.0.0 /24 to 172.16.0.0 /16.
You`ve got your work cut out. If you are looking after DNS, DHCP and static entries etc, and all your layer 3 devices, I would think that would cover it. However we have some pants programmers here who use hard coded IP addresses in their apps rather than use DNS ( I know ) so I guess you`d have to watch out for pitfalls like that. Ive done a couple of office changes ( bringing them inline with the IP schema ) and didnt` really hit any pit falls.
Well some of the applications I'm involved in don't like you to change an IP address.
So if your moving from 192.168.x.0/24 to let say 172.16.0.0/16 the system is a mess.
The problem is at the application level application programmers are sometimes messing with OSI Layer 2,3 and 4 in their applications. Not realising that the application of them is not the only one on the network.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.