Cannot ping or RDP to expanded IP address range

We have an expanded DHCP IP address range: 192.168.110.1-192.168.111.255

It appears that when clients are assigned an IP address in the 192.168.111.x range, we cannot ping or RDP to them from the 192.168.110.x range, and vice versa. The machines in the 111 range do have access to file shares and servers in the 110 range.

Our subnet mask is setup as 255.255.254.0.
Is that correct, or should it be changed? Any assistance would be greatly appreciated.
Thanks!
eimonkeyAsked:
Who is Participating?
 
eimonkeyAuthor Commented:
Update:
I found this article regarding the pen icon:
http://blogs.technet.com/b/networking/archive/2008/12/09/dhcp-shows-the-pending-update-icon-even-after-the-a-record-is-added-to-dns.aspx

Adding the Reverse Lookup Zone for the 192.168.111.0 Subnet got us to the point where we would ping the 111 clients, but RDP wasn't quite working yet. I'll follow through with the other steps and see how far I get.
0
 
Patrick TallaricoFSEP Systems AnalystCommented:
Have you tried the 'All subnets are local' option in the Scope options?
0
 
kenyclCommented:
you should use a class b range instead

172.16.0.1 - 172.16.1.254
with subnetmask 255.255.254.0
instead.
use this subnet calculator
http://www.subnet-calculator.com

hope that helps
0
Protect Your Employees from Wi-Fi Threats

As Wi-Fi growth and popularity continues to climb, not everyone understands the risks that come with connecting to public Wi-Fi or even offering Wi-Fi to employees, visitors and guests. Download the resource kit to make sure your safe wherever business takes you!

 
MISOperationsCommented:
Change the subnet mask to 255.255.255.0
0
 
kenyclCommented:
in theory you cant use 255.255.255.0 if you are changing the third octet
0
 
Neil RussellTechnical Development LeadCommented:
"Change the subnet mask to 255.255.255.0"
Nope that will restrict you to a class C address range
What you should be using is something like...
172.16.0.1 - 172.16.1.254
with a subnetmask 255.255.254.0
This is a Class B address and thats is technically what you should be using if you need more than 255 contiguos IP's
0
 
eimonkeyAuthor Commented:
stpmt11: yes we have the 027 All Subnets are local option [Value: 0x0] on that scope.
There is also a pen icon next to all the active leased 111. addresses in the DHCP range, which the error codes say indicates "Active lease, DNS dynamic update pending. This address is not available for lease by the DHCP server."

I can try changing the range to 172.16.x.x but that will take me a while to coordinate and implement if I need to change the static address on the servers. I'll get back to you on that.
0
 
kenyclCommented:
could it be blocking 3389 traffic for that subnet for some reason
0
 
eimonkeyAuthor Commented:
Update: slight improvment after applying the technet article from above
  • Pen icon removed from .111 DHCP clients
  • From .110: We can ping & RDP to .111 clients (if RDP is enabled)
  • From .111 can ping and RDP some .110 clients, but still having problems with others, esp .110 clients with DHCP addresses.
Still trying to troubleshoot & isolate the issue.


0
 
Patrick TallaricoFSEP Systems AnalystCommented:
Do you have reverse lookup zones for both subnets at this time, or just the .111?  We are currently running 6 different class C networks for different locations, each has its own reverse lookup zone, and all computers are in the same forward lookup zone.
0
 
Patrick TallaricoFSEP Systems AnalystCommented:
Also, can you ping the IP address directly, or are you relying on DNS?  If you can ping, can you RDP?  

I'm sorry but I have been assuming that you have been only trying to ping/RDP using the hostname rather than the ip address.
0
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.