DHCP Question

[VRIT]

Why is it that when I create a network and use DHCP on either windows NT 4 or 2k that at some point there is at least 1 IP address that goes wrong and needs to be excluded. Any ideas ?

Thanks in advance

VRIT

 

[Ntr0P]

Your post is a little vague. By "go wrong" do you mean that you have an IP conflict due to another device using the same IP?

If this is the case you can configure NT4 sp6 or 2k to ping before issuing an ip address to a device. This will typically take care of the issue.

If this is not the case, please elaborate.

 

[VRIT]

Sorry, It was a long day.

What I meant was that you get a bad IP address, not a conflict, buy simply an address that when its leased causes problems so it has to be excluded.

I.e. range 192.168.1.1 - 192.168.1.255 and the IP address of 192.168.1.50 for some reason causes problems when leased out to a user.

Hope that gives you more information.

Regards,

VRIT

 

[Ntr0P]

Well, it narrows it down a bit. Can you define problems though?

 

[ricpinto]

Maybe somebody use it as static ip address . .

 

[VRIT]

The problem is that if you ping another valid IP address is works for about 30-60 seconds then times out all then time.

Its not a clash in IP address and it does seem to be a problem with just that IP address. The solution was to explude it from the list and allow that machine to get another address. However I would like to know why it happens.

Thanks

 

[Ntr0P]

If you are using a switches, you might try clearing the arp entries. This may not be feasible for you though.

 

[Alabaster]

I've seen this happen to one of my clients. DHCP pool of 192.168.1.2 - .250, Servers static 251-253 and a router at .1 When ever a client was leased the .2 IP it would work for about 30-60 seconds then stop. R&R would assign the same IP but ping still would not work. We eventually just removed the .2 from the pool, but even after doing that, a static assignment of .2 to a computer was endless trouble. We just opted to "retire" the .2 IP

Sorry this doesn't resolve your problem, but atleast you know your not going crazy and imagining it.

Peter

Peter
---------------------------------------
To error is human
To really botch it up requires Windows®

 

[Whoheard]

Sounds like a Linksys router problem. Yes?

bob

I know what I know and that's all I know.