I have 1 DHCP server that we have been successfully using for the 3 plus years. The Server is a Windows 2003 Server. This Server acts as :
1. Active Directory Server.
2. DHCP Server.
3. DNS Server.
4. Backup Server.
The DHCP scope is (Starting) 10.220.21.55 - 10.220.21.254 (Ending). The Server's IP address is 192.168.1.X; but, the scope that is gives out is 10.220.21.X/24 . This problem is only with PC's on the DHCP Vlan.
One may wish to referece another separate Experts question as well
Our Windows Domain Client PC's receive DHCP on a specific VLan(DHCP relay is enabled) and again it has been working fine for 3 - Plus years. But recently some computers on the DHCP VLan are not connecting into the network. When I check to see what is going on with the "rouge" pc's I notice that they have a different IP address.
Def. Gtwy: 192.168.1.1
Which is weird because the 192.168 - Scheme that the DHCP server uses is different. The IP Scheme (for what we call VLan-1) is:
Def. Gtwy: 192.168.1.25
So, to correct the 'Rouge' pc's that are not getting on our network and are on the DHCP VLan, I just open a command prompt and type
1. ipconfig <enter>
a. I see the incorrect ip-scheme.
2. ipconfig /release <enter>
a. to zero out the ip address info.
3. ipconfig /renew <enter>
a. to pull a new (and correct) ip address.
4. problem solved.
This is happening to more and more users, if they turn on their PC's with time. If the users do not restart they are fine. Its an easy fix; but, it is annoying?
My 2 questions are:
1. Why is this happening.
2. What can I do to stop this from happening?
I thought that someone connected a home router into a DHCP VLan'd network jack. And this other router is competing with the corporate network to give out IP Addresses.