G
Guest
Hi there
1. We currently run only ONE server(windows 2000 SBS) which is DC (AD-Domain Controller, DHCP, DNS, WINS, Print, Application, File, BackupServer etc)
2. The person who setup has given the IP address Pool for intranet in DHCP as 10.0.0.1 to 10.0.0.254
3. Have exclusions defined in DCHP within the above stated 10.0.0.x block.
I want to change the IP addressing pool from 10.0.0.x range to 10.q.r.s. This is because the octect that is reserved for the server (main Server which is DHCP, DNS, DC, IIS and Print server) is 10.0.0.1 with the subnetmask 255.255.255.0 . And i'm not comfortable with this IP address for security reasons as it is the first octect in the 10.0.0.x block and anyone (a potential hacker can have his first guess corrrect). AND THE MAIN REASON BEING we just have less than 254 hosts at the moment as defined in the dhcp and I'm intending to expand the network in the future and we might run out of IP addresses
I was wondering if i can change THE PRESENT WORKING SYSTEM to
1. The IP Address pool from 10.0.0.1 to 10.0.0.254 to 10.0.0.1 to 10.0.255.255 with sunetmask 255.255.0.0?
2. The IP address for the server from 10.0.0.1 to say 10.0.230.20 and change the name of the server from say bingo to complexBingo and then update any references to the old server name from client machines to new one (any shortcuts to \\bingo to \\complexBingo for example) would be enough???
Can anyone please help me understand the consequences of doing this and if this is a better way of doing it???? because i don't want to change and then get flooded with calls from users next day and land myself in chaos
Regards
kiran
1. We currently run only ONE server(windows 2000 SBS) which is DC (AD-Domain Controller, DHCP, DNS, WINS, Print, Application, File, BackupServer etc)
2. The person who setup has given the IP address Pool for intranet in DHCP as 10.0.0.1 to 10.0.0.254
3. Have exclusions defined in DCHP within the above stated 10.0.0.x block.
I want to change the IP addressing pool from 10.0.0.x range to 10.q.r.s. This is because the octect that is reserved for the server (main Server which is DHCP, DNS, DC, IIS and Print server) is 10.0.0.1 with the subnetmask 255.255.255.0 . And i'm not comfortable with this IP address for security reasons as it is the first octect in the 10.0.0.x block and anyone (a potential hacker can have his first guess corrrect). AND THE MAIN REASON BEING we just have less than 254 hosts at the moment as defined in the dhcp and I'm intending to expand the network in the future and we might run out of IP addresses
I was wondering if i can change THE PRESENT WORKING SYSTEM to
1. The IP Address pool from 10.0.0.1 to 10.0.0.254 to 10.0.0.1 to 10.0.255.255 with sunetmask 255.255.0.0?
2. The IP address for the server from 10.0.0.1 to say 10.0.230.20 and change the name of the server from say bingo to complexBingo and then update any references to the old server name from client machines to new one (any shortcuts to \\bingo to \\complexBingo for example) would be enough???
Can anyone please help me understand the consequences of doing this and if this is a better way of doing it???? because i don't want to change and then get flooded with calls from users next day and land myself in chaos
Regards
kiran