DHCP does not extend IP lease

I have a W2003 server setup with Routing and Remote access which I use to
access the internet through an ISP.

My ISP provides me an IP address through DHCP. The address range used is
192.168.224.0.

I also have 2 internal DCHP servers. I first used the address range
192.168.2.x internally. Changing this to 172.16.2.x did not solve the
problem.

The lease period my ISP gives me is 5 minutes. After 2.5 minutes my system
tries to extend the lease, but does not succeed. After 5 minutes it loses
the lease. Directly after loosing the lease my system manages to get another
lease with the same IP-address.

The problem is very annoying, especially because of the very short lease
period of my ISP: every 5 minutes all my connections are reset.

Connecting only one other system to my ISP connection works fine: after 2.5
minutes the lease is extended.

I first thought the problem was with my ISP, but finding out that a single
system is able to extend the lease makes me doubt that now. I tried to
"hide" everything that might look like routing towards my ISP, as I thought
they might nog want me to connect multiple pc's, but this also didn't solve
the problem.

I already reported the problem to my ISP, but no solution yet. Changing ISP
is no option, as it would take a big investment because I'm on a remote
location.

Please advise.

In news:(E-Mail Removed),
Guus Ellenkamp <(E-Mail Removed)> typed:
> I have a W2003 server setup with Routing and Remote access which I
> use to access the internet through an ISP.

>
> My ISP provides me an IP address through DHCP. The address range used
> is 192.168.224.0.l

I suggest you not ask Windows to do this work for you, but stick a
router/firewall appliance between your ISP's modem/router, and your own
network. It (not Windows) should be doing NAT, and it can do DHCP for your
internal network, or not (if you prefer to have your Windows box do it,
which might be preferable if you run AD).

>
> I also have 2 internal DCHP servers.

Hmmmm....why?

> I first used the address range
> 192.168.2.x internally. Changing this to 172.16.2.x did not solve the
> problem.
>
> The lease period my ISP gives me is 5 minutes.


That's insane! What's their justification for this?

> After 2.5 minutes my
> system tries to extend the lease, but does not succeed. After 5
> minutes it loses the lease. Directly after loosing the lease my
> system manages to get another lease with the same IP-address.
>
> The problem is very annoying, especially because of the very short
> lease period of my ISP: every 5 minutes all my connections are reset.
>
> Connecting only one other system to my ISP connection works fine:
> after 2.5 minutes the lease is extended.
>
> I first thought the problem was with my ISP, but finding out that a
> single system is able to extend the lease makes me doubt that now. I
> tried to "hide" everything that might look like routing towards my
> ISP, as I thought they might nog want me to connect multiple pc's,
> but this also didn't solve the problem.
>
> I already reported the problem to my ISP, but no solution yet.
> Changing ISP is no option, as it would take a big investment because
> I'm on a remote location.
>
> Please advise.

Hello,

I don't really understand where is the problem.

You should have one network card connected to the ISP.
=> This card uses the ISP DHCP to receive one address, and can extend the
lease.

You should have anoter network card connected to the local network.
=> Stations on the local network receive addresses from Yours DHCP in
172.16.2.X (or 192.168.2.X).

Where things are different in your configuration?

Bye.
--
Thierry DEMAN-BARCELÒ
MVP Exchange, SQL/Server
http://base.faqexchange.info http://www.faqexchange.info
"Guus Ellenkamp" <(E-Mail Removed)> a écrit dans le message de
news: (E-Mail Removed)...
>I have a W2003 server setup with Routing and Remote access which I use to
>access the internet through an ISP.
>
> My ISP provides me an IP address through DHCP. The address range used is
> 192.168.224.0.
>
> I also have 2 internal DCHP servers. I first used the address range
> 192.168.2.x internally. Changing this to 172.16.2.x did not solve the
> problem.
>
> The lease period my ISP gives me is 5 minutes. After 2.5 minutes my system
> tries to extend the lease, but does not succeed. After 5 minutes it loses
> the lease. Directly after loosing the lease my system manages to get
> another lease with the same IP-address.
>
> The problem is very annoying, especially because of the very short lease
> period of my ISP: every 5 minutes all my connections are reset.
>
> Connecting only one other system to my ISP connection works fine: after
> 2.5 minutes the lease is extended.
>
> I first thought the problem was with my ISP, but finding out that a single
> system is able to extend the lease makes me doubt that now. I tried to
> "hide" everything that might look like routing towards my ISP, as I
> thought they might nog want me to connect multiple pc's, but this also
> didn't solve the problem.
>
> I already reported the problem to my ISP, but no solution yet. Changing
> ISP is no option, as it would take a big investment because I'm on a
> remote location.
>
> Please advise.
>

Things are the same in my configuration. I finally figured out the lease
extension reply from my ISP is sent to the broadcast address x.x.x.255 which
I had filtered out. They also might have changed something in their system,
but it's working now.

"Thierry DEMAN [MVP]" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hello,
>
> I don't really understand where is the problem.
>
> You should have one network card connected to the ISP.
> => This card uses the ISP DHCP to receive one address, and can extend the
> lease.
>
> You should have anoter network card connected to the local network.
> => Stations on the local network receive addresses from Yours DHCP in
> 172.16.2.X (or 192.168.2.X).
>
> Where things are different in your configuration?
>
> Bye.
> --
> Thierry DEMAN-BARCELÒ
> MVP Exchange, SQL/Server
> http://base.faqexchange.info http://www.faqexchange.info
> "Guus Ellenkamp" <(E-Mail Removed)> a écrit dans le message de
> news: (E-Mail Removed)...
>>I have a W2003 server setup with Routing and Remote access which I use to
>>access the internet through an ISP.
>>
>> My ISP provides me an IP address through DHCP. The address range used is
>> 192.168.224.0.
>>
>> I also have 2 internal DCHP servers. I first used the address range
>> 192.168.2.x internally. Changing this to 172.16.2.x did not solve the
>> problem.
>>
>> The lease period my ISP gives me is 5 minutes. After 2.5 minutes my
>> system tries to extend the lease, but does not succeed. After 5 minutes
>> it loses the lease. Directly after loosing the lease my system manages to
>> get another lease with the same IP-address.
>>
>> The problem is very annoying, especially because of the very short lease
>> period of my ISP: every 5 minutes all my connections are reset.
>>
>> Connecting only one other system to my ISP connection works fine: after
>> 2.5 minutes the lease is extended.
>>
>> I first thought the problem was with my ISP, but finding out that a
>> single system is able to extend the lease makes me doubt that now. I
>> tried to "hide" everything that might look like routing towards my ISP,
>> as I thought they might nog want me to connect multiple pc's, but this
>> also didn't solve the problem.
>>
>> I already reported the problem to my ISP, but no solution yet. Changing
>> ISP is no option, as it would take a big investment because I'm on a
>> remote location.
>>
>> Please advise.
>>
>
>

I also wondered why they gave a 5 minute lease on a broadband connection...

Problem is solved. See other reply.

"Lanwench [MVP - Exchange]"
<(E-Mail Removed) ahoo.com> wrote in message
news:%(E-Mail Removed)...
> In news:(E-Mail Removed),
> Guus Ellenkamp <(E-Mail Removed)> typed:
>> I have a W2003 server setup with Routing and Remote access which I
>> use to access the internet through an ISP.
>
>>
>> My ISP provides me an IP address through DHCP. The address range used
>> is 192.168.224.0.l
>
> I suggest you not ask Windows to do this work for you, but stick a
> router/firewall appliance between your ISP's modem/router, and your own
> network. It (not Windows) should be doing NAT, and it can do DHCP for
> your internal network, or not (if you prefer to have your Windows box do
> it, which might be preferable if you run AD).
>
>>
>> I also have 2 internal DCHP servers.
>
> Hmmmm....why?
>
>> I first used the address range
>> 192.168.2.x internally. Changing this to 172.16.2.x did not solve the
>> problem.
>>
>> The lease period my ISP gives me is 5 minutes.
>
>
> That's insane! What's their justification for this?
>
>> After 2.5 minutes my
>> system tries to extend the lease, but does not succeed. After 5
>> minutes it loses the lease. Directly after loosing the lease my
>> system manages to get another lease with the same IP-address.
>>
>> The problem is very annoying, especially because of the very short
>> lease period of my ISP: every 5 minutes all my connections are reset.
>>
>> Connecting only one other system to my ISP connection works fine:
>> after 2.5 minutes the lease is extended.
>>
>> I first thought the problem was with my ISP, but finding out that a
>> single system is able to extend the lease makes me doubt that now. I
>> tried to "hide" everything that might look like routing towards my
>> ISP, as I thought they might nog want me to connect multiple pc's,
>> but this also didn't solve the problem.
>>
>> I already reported the problem to my ISP, but no solution yet.
>> Changing ISP is no option, as it would take a big investment because
>> I'm on a remote location.
>>
>> Please advise.
>
>
>