V
Vince C.
Hi.
Our company has changed the network topology from static to dynamic
addressing using Windows 2000 DHCP capabilities. We are using private class
A for dynamic IP range. 255 workstations addresses are allocated from
10.10.1.0 to 10.10.1.254. Subnet mask is 255.255.0.0. All static IPs are on
a separate IP group, i.e. all but 10.10.1.xxx.
We are experiencing IP conflicts in the dynamic allocated addresses. We also
noticed some machines took an IP that was already allocated to another one
while we were performing connectivity checks. Also in the DHCP snap-in
(Address leases) there are a couple of IPs that are marked "bad_address".
All machines are DHCP enabled. So why do we have conflicts? Why are there
"bad_address"? DHCP service runs on a Windows 2K SP3 server. A WINS is also
running on an NT4 server.
Thanks for helping.
Vince C.
Our company has changed the network topology from static to dynamic
addressing using Windows 2000 DHCP capabilities. We are using private class
A for dynamic IP range. 255 workstations addresses are allocated from
10.10.1.0 to 10.10.1.254. Subnet mask is 255.255.0.0. All static IPs are on
a separate IP group, i.e. all but 10.10.1.xxx.
We are experiencing IP conflicts in the dynamic allocated addresses. We also
noticed some machines took an IP that was already allocated to another one
while we were performing connectivity checks. Also in the DHCP snap-in
(Address leases) there are a couple of IPs that are marked "bad_address".
All machines are DHCP enabled. So why do we have conflicts? Why are there
"bad_address"? DHCP service runs on a Windows 2K SP3 server. A WINS is also
running on an NT4 server.
Thanks for helping.
Vince C.