Join Director of Product Management Todd OBoyle on April 26th as he covers the key elements of a phishing protection program. Whether you’re an old hat at phishing education or considering starting a program -- we'll discuss critical components that should be in any program.
Netmask/DNS issue
I needed to expand the IP addresses available for our internal use so I was going to add an additional sequential subnet. The current subnet mask is 255.255.255.254.0 I went to network connections on the server, selected the local area connection and changed the netmask to 255.255.252.0 and now I can not access the server by name from some computers.
When I changed the netmask from 255.255.255.254 to 255.255.255.252 it removed it from some of the DNS servers. It finally updated after 45-60 minutes.
I changed it on another 2008 server without any of these issues.
should changing the netmask on a 2008 64bit server cause this issue?
When I changed the netmask from 255.255.255.254 to 255.255.255.252 it removed it from some of the DNS servers. It finally updated after 45-60 minutes.
I changed it on another 2008 server without any of these issues.
should changing the netmask on a 2008 64bit server cause this issue?
Who is Participating?
Net ask changes must be propagated to all systems.
The likely issue is that the ip a system got based on the 252 sees the server address as local, while the server ip/mask combination does not.
Once you dive down this route, you have to update the dhcp server scope definition to push out the new mask.
A better approach is to define another ip range on the router with an ip helper dhcp relay agent configured to send requests to the dhcp server where you would define another scope iof IPs. The router will then route between the segments.
You went from 2x256-3 possible hosts to 4x256-3possible hosts
The likely issue is that the ip a system got based on the 252 sees the server address as local, while the server ip/mask combination does not.
Once you dive down this route, you have to update the dhcp server scope definition to push out the new mask.
A better approach is to define another ip range on the router with an ip helper dhcp relay agent configured to send requests to the dhcp server where you would define another scope iof IPs. The router will then route between the segments.
You went from 2x256-3 possible hosts to 4x256-3possible hosts
My intention was to change the NetMask on the comptuers/servers with fixed IP addresses then update the DHCP scope.
Currently the netmask is 255.255.255.254 but I am running out of available IP address to assign via DHCP.
DHCP range 10.10.2.0-255
Fixed IP range 10.10.3.0-255
I requested more IP address from our corporate office and was told I could use 10.10.4.4.0-255 which had been assigned to us before I started at the company but never used.
I had planed on updating the netmask on the servers/printers/switches to 255.255.255.252 then updating the DHCP to use 255.255.255.252 as the netmask for assigned IP addresses and finally if I ran into no problems testing fixed ip addresses in the 10.10.4.0 range adding a new pool to the DHCP server.
I changed two servers last night and one disappeared from some of the DNS servers for close to an hour. I changed both back to 255.255.255.254 after that.
We already have multiple VLANS, multiple stacks of switches connected via fiber, a separate outgoing internet connection for guests and both wired and wireless routers and a definite lack of labeling and documentation which I am slowly trying to remedy. I was trying to avoid adding any more complexity to the network
DHCP range 10.10.2.0-255
Fixed IP range 10.10.3.0-255
I requested more IP address from our corporate office and was told I could use 10.10.4.4.0-255 which had been assigned to us before I started at the company but never used.
I had planed on updating the netmask on the servers/printers/switches to 255.255.255.252 then updating the DHCP to use 255.255.255.252 as the netmask for assigned IP addresses and finally if I ran into no problems testing fixed ip addresses in the 10.10.4.0 range adding a new pool to the DHCP server.
I changed two servers last night and one disappeared from some of the DNS servers for close to an hour. I changed both back to 255.255.255.254 after that.
We already have multiple VLANS, multiple stacks of switches connected via fiber, a separate outgoing internet connection for guests and both wired and wireless routers and a definite lack of labeling and documentation which I am slowly trying to remedy. I was trying to avoid adding any more complexity to the network
You are citing a netmask that is not valid. 255.255.255.254 means there are only two IPs in the block, 252 means there are four. These types of netmasks are only used in firewall rules (254 to allow two sequential IPs through the firewall or deny) the 254 or /30 notation is used on a wan connection.
You can have multiple scopes defined in the Dhcp, or super scopes, but you would need to separate the networks/ports by assigning them to separate VLANs and then configuring an IP helper/DHCP Relay agent such that when it proxies the DHCPdiscovery request it will reflect the request such that the response of IP from the DHCP server would be from the 10.10.4.0 255.255.255.0 range.
The router or the switch would then need to be configured to handle the inter segment communication/routing.
You can have multiple scopes defined in the Dhcp, or super scopes, but you would need to separate the networks/ports by assigning them to separate VLANs and then configuring an IP helper/DHCP Relay agent such that when it proxies the DHCPdiscovery request it will reflect the request such that the response of IP from the DHCP server would be from the 10.10.4.0 255.255.255.0 range.
The router or the switch would then need to be configured to handle the inter segment communication/routing.
Changing the netmask can have almost any effect with your configuration, but that is something only you can know or get to know :D. In theory, and with a well configured and documented network, all potential point of failures would be easy to spot. Since you have VLAN, you need to set routing info in the L3 switches correct. Aside from that, nothing obvious should prevent you from changing the netmask.
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
All Courses
From novice to tech pro — start learning today.
-
Course of the Month6 days, 11 hours left to enrollMonitoring and Operating a Private Cloud with System Center 2012 R2 273 lessons
Alter the netmask/scope and import it back.
This way you will maintain any IP reservation you may have as well as IP range exclusion
If you are increasing from a 509 possible usable IPs/host to a 1021 there are many devices where this change Needs to be done including VPN/firewalls if any, managed switches, etc.