Windows 2000 server problem

  • Thread starter Thread starter Barbara
  • Start date Start date
B

Barbara

We have a border manager server for dhcp. When connecting
a Windows 2000 server it pulled 169 IP addresses. I know
now that this is what Windows 2000 sends out. My numbers
are actually in 10. range. The machines affected seem to
want to pull a 169 number even though the 2000 server has
been disconnected. If I can get the 169 number to release
from the NIC it will reset with the 10 number but is still
extremely slow in starting Windows 98 and pulling my
Netware Client. I found the Windows Client on the machines
that are booting slowly and deleted that, reset switches,
hubs, the border manager and the problem remains. Does
anyone know what is going on and how to remedy this
problem??
 
The 169 address is not coming from your server. Windows98 and above have
this 'feature' of Auto IP address Configuration so it has nothing to do with
your Win2k machine. Any machine that is Win98 and up set to DHCP will use a
169. address when it cannot contact a DHCP server. So your DHCP server is
the problem or your network is routed into subnets that are blocking the
bootp broadcasts.

--
Scott Harding
MCSE, MCSA, A+, Network+
Microsoft MVP - Windows NT Server

scrockel@***No_SPAM***hotmail.com
 
Back
Top