Windows Forum

Ask something
Discussion Locked

NT Server DHCP Problem...

0 helpful
6 replies

by art23

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I am consulting for a small site that has a Dell Server that was previously built with NT Server. This server has always been set with a static IP, with the workstations receiving IP's from DHCP. I was installing a DSL network and the server would not allow me to change the settings to obtain IP from a DHCP server, even after logging in locally under an admin id. After setting up the router, the workstations work great(on the network and receive IP's like they are suppose to and can surf very nicely), but the server does not see the router at all. I tried to ping it but no resonse. Any help will be greatly appreciated.

6 replies

by don christner

Under control panel|services, make sure that the DHCP client is started. With a static IP in the past, this service would not have been required.

Don

by bthomas

if your nt server is a WINS server you cannot use dhcp to obtain an address on the server. This is because you have to add the servers address to the wins tab to register itself. if it uses dhcp this could change and wins would be disabled.
Typically servers are usually hardcoded anyway.
I would just change the ip so it is in the same subnet of the routers dhcp scope.
hard code the dns servers. and then exclude
the servers address from the routers scope.

by lmaslin

I would suggest that you do not use DHCP on the DSL router. This is fine for a peer to peer network, but doesn't make much sense in any other situation. Why not get your service provider to remove the DHCP functionality and provide you with a small range of IP addresses, and utilize the server for DHCP once again. Make sure your network is protected in any case!

by curlergirl

Your question isn't clear on what IP addressing scheme you're using. First of all, your server should definitely continue to use a static IP. This is not just for WINS purposes, but also because you don't want a server address to suddenly change, as it can if the server is getting its address from a DHCP server, because this could cause network problems. If your server cannot ping the router, then they must be on separate subnets. So, the first thing you need to do is make sure the server and router are on the same IP subnet. You should configure your router so that it has a public IP address (it may be static or it may be dynamically assigned by your ISP's DHCP server, and a second, static IP address in your local subnet. Then connect the router to your internal hub, make sure all internal workstations and servers use the router's local address as the default gateway and everyone should be able to browse, including your server. If this doesn't work for you, you may have some problem in your IP addressing scheme, which I can help you with if you will give more details. Hope this helps!

This discussion is closed to new replies.