DHCP or DNS problem?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi all,
I just added a 2003 member server to my 2000 network (I also did adprep so
that I change to a dc later).
My problem is that now I am having problems connecting a new machine. It is
set to enable dhcp and it assigns an ip but it is a wrong ip. our network is
a private network but it assigns an ip like 169.254.27.21 subnet mask
255.255.0.0. I don't know where it is getting these ips.
Is this a dns or dhcp problem. My 2000 dc server is acting as the dns
server. Is there a setting somewhere telling it to look elsewhere for ips or
is dhcp not configured correctly? It was working before I added the 2003
server.
Please help,
Sher
 
This is an APIPA address automatically assigned to the system when a static
IP does not exist, and no DHCP server responds to the DHCP Discovers. you
should user a network sniffer and see if you are in fact receiving a DHCP
Offer. Also make sure your DHCP server is authorized etc.
 
Hi Dusty,
Ok I did some checking and my scope has enough ips to assign to new
computers but it is not. I tested it my changing my scope from
start 192.168.1.51
end 192.168.1.240
to
192.168.1.50
192.168.1.240
and the new machine connected and assigned ip 192.168.1.50.
so I'm thinking dhcp is working
is there a command to use to maybe refresh or release unused ip address
within that scope?
Thanks for your help
Sher
 
Then you have a physical problem. Verify it by giving the machine a valid
"static" network configuration, if there is a physical problem the machine
will still not work on the network.

Never waste time fooling with DHCP to solve problems. Always eliminate DHCP
by using a statically assigned network configuration, make sure everything
works *perfectly*,...then...set the machine to use DHCP after that.
 
The first thing I did was assign a static ip address and dns ip. the machine
works fine with static but if I shutdown and change it back to dhcp then it
finds the auto ip again and not a good ip.

Phillip Windell said:
Then you have a physical problem. Verify it by giving the machine a valid
"static" network configuration, if there is a physical problem the machine
will still not work on the network.

Never waste time fooling with DHCP to solve problems. Always eliminate DHCP
by using a statically assigned network configuration, make sure everything
works *perfectly*,...then...set the machine to use DHCP after that.


--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


Sher said:
Hi Dusty,
Ok I did some checking and my scope has enough ips to assign to new
computers but it is not. I tested it my changing my scope from
start 192.168.1.51
end 192.168.1.240
to
192.168.1.50
192.168.1.240
and the new machine connected and assigned ip 192.168.1.50.
so I'm thinking dhcp is working
is there a command to use to maybe refresh or release unused ip address
within that scope?
Thanks for your help
Sher


-- rights
--
Click to expand...
Click to expand...
 
Back
Top