We are a medium sized company with about 150 users + printers + mobile phones and other such devices connecting to our network. Our servers run Windows Server 2003 SP2 (32 Bit)
Since last week, when i try to join new PC's into our domain, it says AD-DC cannot be contacted. When I give a static IP, default gateway, dns locations etc to the IPv4 properties of the NIC and try to join to domain, it joins without any problem. after joining the domain, when I take out these static values i gave and give automatic settings, it still gives me unidentified network and limited connectivity. So for the time being, I've been giving IP reservations (same IP i gave static to join the domain) to the DHCP Server so that these PCs can remain connected. Can anyone please help with this?
Also, my DHCP scope has reached its limit. Scope options were from 192.168.0.15 to 192.168.0.199 , subnet of 255.255.255.0 with our default gateway (firewall) being 192.168.0.7
So I created another Scope 192.168.1.15 to 192.168.1.199 with same subnet mask 255.255.255.0 and a secondary working IP address for our firewall (192.168.1.7)
To test this new scope, I gave one of the PCs a static IP address of 192.168.1.100 pointing it to default gateway 192.168.1.7, there seems to be no connectivity. I went to DNS server, added 192.168.1.x subnet to reverse look-ups. Is there anything more I need to do to get the new scope to work? or is this happening because of the same problem which is causing my PCs to not find the domain controller?