I have abit of an odd problem and a rather complex odd network however im going to make it as simple as possible just incase this is an easy fix.
I have two IP Ranges in our network
192.168.0.0 for servers (statically assigned)
10.0.0.0 for client PC's (statically assigned)
I have setup a DHCP Server and a small test range of free 10.0.0.0 addresses (its about 8 in total) on our domain controller that is on ip 10.0.0.4 I am plugging a thin client into the network and it happily gets a DHCP Address from the pool and everyone is happy.
However i have now removed that small test range from the DHCP Server and replaced it with a 172.20.10.0/24 range, but now the thin client is no longer able to get an IP address.
am i correct in thinking that because the firewall is only interested in traffic from the 10 & 192 address ranges (these are the only ones configured on its interfaces) its doing something to stop the thin client from getting an address, or blocking/dropping the traffic?
Im really not that clued up with the cisco equipment or how it works, im being promised training in the next few weeks / months but nothing has materialised yet. so im hoping until then someone here can help me out.
P.S. please do not request a copy of the firewalls config as for security im not able to provide it.
Kris
Best Answer
Ok so I managed to resolve this problem, it appears as the MS DHCP client does not like you adding second IP addresses to the same card in order to try and get it to work across the one interface, you need to have a totally seperate network card installed and configured for the range in question (you also need to leave the gateway address blank on the second card otherwise that generates issues as well).
But its all working now, thanks to everyone who commented, ive learnt a lot.
kris