[Server 2003][DHCP] Going nuts, help!!!!

[Steve]

We're doing a clean install of Server 2003 on a new box, nothing ever on it before. We have cable modem feeding into a D-Link DI604 VPN/Firewall and from there to a D-Link 48-port switch.

The IP addressing scheme is 172.24.58.x

The DI605 is set to .2 and I have DHCP fully disabled on it.

The server has a fixed IP of 172.24.58.3. It is the primary DNS server, with the DI605 set as the secondary (which in turn updates from the cable ISP). The server is the DHCP server as well, with a scope of 172.24.58.1 through 172.24.58.254, with .1 through .3 being excluded from assignment.

The server can connect to the Internet just fine.

If we manually configure a WinXP client and assign a fixed IP on the network range, we can authenticate to the domain and login and the client is then able to access the Internet.

When we try to have the client obtain an address from DHCP, it's not seeing the DHCP server, it's picking up a 169.something IP.

There is a second (as yet unused) ethernet card in the server. When we set the TCP/IP properties to "automatically obtain IP address", it picks up that 169.something IP which is the automatic default range when a DHCP server cannot be found.

So that tells me the DHCP server isn't working.

But I'm damned if I can figure out why.

Any suggestions?

[mrRT]

Can you ping from client to server Steve..>>???

also can you try the ipconfig /release and then go with the /renew


if still an issue....maybe post for me ipconfig /all

could be a gateway issue too....

[FrankF]

We're doing a clean install of Server 2003 on a new box, nothing ever on it before. We have cable modem feeding into a D-Link DI604 VPN/Firewall and from there to a D-Link 48-port switch.

The IP addressing scheme is 172.24.58.x

The DI605 is set to .2 and I have DHCP fully disabled on it.

The server has a fixed IP of 172.24.58.3. It is the primary DNS server, with the DI605 set as the secondary (which in turn updates from the cable ISP). The server is the DHCP server as well, with a scope of 172.24.58.1 through 172.24.58.254, with .1 through .3 being excluded from assignment.

The server can connect to the Internet just fine.

If we manually configure a WinXP client and assign a fixed IP on the network range, we can authenticate to the domain and login and the client is then able to access the Internet.

When we try to have the client obtain an address from DHCP, it's not seeing the DHCP server, it's picking up a 169.something IP.

There is a second (as yet unused) ethernet card in the server. When we set the TCP/IP properties to "automatically obtain IP address", it picks up that 169.something IP which is the automatic default range when a DHCP server cannot be found.

So that tells me the DHCP server isn't working.

But I'm damned if I can figure out why.

Any suggestions?

We have some flakey equipment at work (JTAG probes made by Agilent) that we tried to network.

The place where I work owns the 159.201.x.x block of IP numbers. If we assigned a fixed 159.201.x.x IP to the JTAG probes, and a subnet mask of 255.255.0.0, we could not communicate with them.

Solution was to give them a subnet mask of 0.0.0.0.

[Steve]

We solved the problem by removing DHCP as a server role and using the DLink firewall as the DHCP server. Everything's fine now! No idea what the original problem was but all I care about is that we have a working network :)

Thanks for the replies, guys.

[mrRT]

glad you are up and running