• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 600
  • Last Modified:

Connection Problems after Resubnetting Newtork

I had a previous network set up of 192.168.1.0 - 192.168.1.255 subnet of 255.255.255.0.  We were adding more devices and had to increase our number of available IP's So I deleted the old scope and made a new one that was 192.168.0.0 - 192.168.1.255 with a subnet of 255.255.254.0.  We now seem to be having some sort of connection issue.  We have several computers that has an IP from the 192.168.0.1 Range that can print\ping to a printer that has a static in the 192.168.1.1 range.  If I give the computers a static address in the same range as the printer then they can print and "see"  the printer fine.  Some computers can print in the above situation though.  Not real sure what the problem is.
0
adamhicks
Asked:
adamhicks
1 Solution
 
d3ath5tarCommented:
Have all the static devices been updated with the new subnet mask?
0
 
wwakefieldCommented:
I might be missing something, but you might need a CANT or something in this somewhere.  

As a guess though, assume you restarted the DHCP server and made sure that all workstations have properly refreshed their IP with the correct sumnet mask.

0
 
Justin OwensITIL Problem ManagerCommented:
Did you make sure your networking equipment (router,etc.) knows about this range change?  Also, as has been mentioned, your DHCP scope leases need to be refreshed.  Perhaps your machines need to do a release/renew on their addresses.

DrUltima
0
Get your Conversational Ransomware Defense e‑book

This e-book gives you an insight into the ransomware threat and reviews the fundamentals of top-notch ransomware preparedness and recovery. To help you protect yourself and your organization. The initial infection may be inevitable, so the best protection is to be fully prepared.

 
Leon FesterCommented:
Agreed, if the DHPC lease has not yet expired, then those machines will still have the old IP Settings.
Run an ipconfig /release, and then ipconfig /renew on these machines.

Check that DNS is updating correctly then everything should work.
Also just double-check your scope options, it's easy for fingers to slip.
0
 
adamhicksAuthor Commented:
Yes the static devices have been updated and I definitely needed to add a Can't.  Some computers Can't print if they are in the opposite IP Range and some can.
0
 
wwakefieldCommented:
Ditto checking the switch, but I am thinking the refresh and renew will do it.  Manually check the ones for the correct mask on the items that are not working properly.
0
 
adamhicksAuthor Commented:
I found the issue.   The printer its self ended up reverting back to the old subnet.  I was only checking the computers.  After setting the Subnet mask on the printer all is good.  Guess I should of check that first! Thanks for all the comments.
0
 
adamhicksAuthor Commented:
found the solution
0

Featured Post

Free recovery tool for Microsoft Active Directory

Veeam Explorer for Microsoft Active Directory provides fast and reliable object-level recovery for Active Directory from a single-pass, agentless backup or storage snapshot — without the need to restore an entire virtual machine or use third-party tools.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now