Hello, I have an AD environment with 2 DC 2003 R2 servers, the PDC also plays
the role of DHCP server. While a Linux DHCP will issue ip addresses over
wireless without a glitch as soon as I stop the linux server the wireless
does not renew the lease on the MS DHCP. A restart of the service or the AP
(Netgear Prosafe WG 302) will fix things temporarily.
I have not seen anything in the scope options that might , except
creating a WINS server.
Any pointers on where I might track this issue down?
Thanks,

Ozz.

Hello Ozz,

Please describe your cabling with the server, AP and Netgear router/switch.

Maybe this s (follow the answers):
http://techrepublic.com.com/5208-623...222572&start=0

http://technet.microsoft.com/en-us/n.../bb530679.aspx


Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** us YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> Hello, I have an AD environment with 2 DC 2003 R2 servers, the PDC
> also plays
> the role of DHCP server. While a Linux DHCP will issue ip addresses
> over
> wireless without a glitch as soon as I stop the linux server the
> wireless
> does not renew the lease on the MS DHCP. A restart of the service or
> the AP
> (Netgear Prosafe WG 302) will fix things temporarily.
> I have not seen anything in the scope options that might , except
> creating a WINS server.
> Any pointers on where I might track this issue down?
> Thanks,
> Ozz.
>

First of all thanks for the answer.
There have been some developments since this was posted, most workstations
have been able to get an ip address and there is just a handful that resists
still.
The Netgear Prosafe WG 302 is not a wireless router, it's a true AP (no WAN
port).
We have 2 access points on different floors and most workstations are now
working well. The issue cannot be related to cabling as we have a Linux DHCP
server and while at use all workstations do get and ip over wireless...
There is now less than a dozen (out of 150 WS) that will need a restart of
the WAP in order to get an ip address.
There is 1 WS that does not get an ip at all.
That is the whole picture.
Thanks again,

Ozz.

"Meinolf Weber" wrote:

> Hello Ozz,
>
> Please describe your cabling with the server, AP and Netgear router/switch.
>
> Maybe this s (follow the answers):
> http://techrepublic.com.com/5208-623...222572&start=0
>
> http://technet.microsoft.com/en-us/n.../bb530679.aspx
>
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and confers
> no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** us YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>
> > Hello, I have an AD environment with 2 DC 2003 R2 servers, the PDC
> > also plays
> > the role of DHCP server. While a Linux DHCP will issue ip addresses
> > over
> > wireless without a glitch as soon as I stop the linux server the
> > wireless
> > does not renew the lease on the MS DHCP. A restart of the service or
> > the AP
> > (Netgear Prosafe WG 302) will fix things temporarily.
> > I have not seen anything in the scope options that might , except
> > creating a WINS server.
> > Any pointers on where I might track this issue down?
> > Thanks,
> > Ozz.
> >
>
>
>