Discussion Locked

Netmasking

0 helpful
13 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
Out network techs configured netmasking on a dhcp server to dish out more IP address about a week ago. It started out with small problems the normal problems, realease/renew. Now the world wide web publishing service on the proxy server keeps stopping on its own. Two other servers keep shutting down, one is running sql server7.0 and the other is our extranet server. Could these problems be caused by bad configurations to the dhcp. How can this problem be solved.

13 replies

by steve cody

It sounds like they may have set up a block of addresses includes one that is already assigned to a computer. You need to check your System log in the Event viewer on the SQL server, and the proxy server. See if it mentions the NBT service failingand mentioning a duplicate IP address on the network.
Also, make sure you update the DHCP server system to the latest service pack. There are issues with the issuing an IP address when one already exists that is fixed in the later service packs. I think SP5 or higher fixes that, but can't remember off the top of my head.
Also, go into the DHCP server scope settings and exclude the addresses for the proxy server and sql servers and set those systems up statically.
- Steve

by arwjnplanotx

The only thing I can think of is that you are possably using public internet IP addresses. For your internal network you should only be using private IP addresses. Generally the network address of 192.168.0.1 through 192.168.255.254 are reserved forprivate networks. All of your servers should have DHCP reserved or static (permanant) IP addresses because, if something is referencing them via their IP address and it keeps changing then the connections will be lost.

I hope this will help you track down the problem.

by garetjax

Jason -

Sound like your NetTechs errored in their DHCP reconfig to include your server IPs in the DHCP scope. A quick fix would be to exclude the server addresses from the DHCP scope. You then need to find the workstations with the DHCP-assigned server IPs and release/renew them. Lastly, restart your servers so that they regain their original IPs.

Good luck.

by mckaytech

I'm curious as to whether the DHCP changes made were just a change of scope (as assumed by the other writers) or whether they did, indeed, change the subnet mask to permit more available IP addresses on the subnet.

If they changed the subnet mask, the boundaries of the subnet change and you can get all sorts of IP address conflicts and weird behavior especially if the scope was left the same.

Almost without fail, servers and printers should have static addresses and those addresses shouldbe excluded from the scope.
So I would take a look at that as the other answers suggested.

But also look at the subnet mask and make sure you're not trying to assign IP addresses across subnet boundaries.

paul

by arwjnplanotx

Just a little follow up. Here are the official IP network addresses and subnet masks reserved for internal networks:

network address default mask
10.0.0.0 255.0.0.0
172.16.0.0 255.240.0.0
192.168.0.0 255.255.0.0

This discussion is closed to new replies.