Solved

Why have workstation IP addresses have changed since new server installation?

Posted on 2008-06-17
6
196 Views
Last Modified: 2010-04-18
This is pretty cut and dry:

We recently replaced one of our servers and since that time, people's ip addresses have changed from the 172.16.5 network to the 162.16.1 network.  I am no longer able to connect remotely to the workstations in my domain without their new IP address.  Name resolution no longer works.

I set a few workstations to Static IP to see if I could regain name resolution, and was able to. I would just prefer to be using DCHP on the 172.16.5 network. What do you suppose is set up incorrectly? Thanks.
0
Comment
Question by:johnnymac08
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
6 Comments
 
LVL 4

Expert Comment

by:pamiken
ID: 21804864
did you install a dhcp server on the new server you setup???
0
 
LVL 9

Accepted Solution

by:
craigothy earned 250 total points
ID: 21804875
Is there a possibility that your old server was providing DHCP for 172.16.5.x and your new server is not configured the same way?
0
 
LVL 6

Assisted Solution

by:DocCan11
DocCan11 earned 250 total points
ID: 21804898
If all your clients now have a different IP address and are using DHCP the problem is one of two.. FIrst someone has put a DHCP server on your network and it is giving out the worng IP's.. or two someone has changed your scope on your DHCP server.. The easiest way to find out is on one of the new clients type ipconfig /all from the command prompt and look for the IP address of the DHCP server that gave them the address.. this is your culprit
0
NEW Veeam Agent for Microsoft Windows

Backup and recover physical and cloud-based servers and workstations, as well as endpoint devices that belong to remote users. Avoid downtime and data loss quickly and easily for Windows-based physical or public cloud-based workloads!

 
LVL 13

Expert Comment

by:ocon827679
ID: 21805404
Agree with DOC.  Go shoot the admin that put up a dhcp server and had the priviledges (Enterprise Admin) to authorize the server.  (Or do you think that there is an applicance that someone configured on the network giving out the addresses)  Of course, anyone can put up an NT 4 server and load DHCP Server.  That would do it also.

OK - don't shoot him, usually a threat of bodily harm will suffice!
0
 

Author Comment

by:johnnymac08
ID: 21805424
Yes. DHCP server has been installed on new server.
Yes, looking at the old server, DNS reverse lookup zones look different.  Also, the old server is still hooked up.   I think the issue is with the scope on the DHCP server.  A colleague who helped set this up is coming out now. Thanks  
0
 

Author Comment

by:johnnymac08
ID: 21805952
The scope had changed, and for some reason the old 172.16.5 entires were screwing things up.  I manually removed the 172.16.5 entries and now am using the 172.16.1. network. Name resolution is back... thanks all.
0

Featured Post

Announcing the Most Valuable Experts of 2016

MVEs are more concerned with the satisfaction of those they help than with the considerable points they can earn. They are the types of people you feel privileged to call colleagues. Join us in honoring this amazing group of Experts.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

If you have a multi-homed DNS setup in windows, you can have issues with connectivity to the server that hosts the DNS services (or even member servers of your domain if this same DNS server is a DC). This is because windows registers all of its IPs…
Learn about cloud computing and its benefits for small business owners.
Email security requires an ever evolving service that stays up to date with counter-evolving threats. The Email Laundry perform Research and Development to ensure their email security service evolves faster than cyber criminals. We apply our Threat…
Attackers love to prey on accounts that have privileges. Reducing privileged accounts and protecting privileged accounts therefore is paramount. Users, groups, and service accounts need to be protected to help protect the entire Active Directory …

756 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question