Windows 7 being removed from DNS?

I have started deploying Windows 7 on netbooks within the organization.
What I have noticed is the machines seem to be removed from DNS after some
period of time. Staff usually connect via Cisco VPN and don't always
physically plug into the network on a regular basis. Could this be the
problem? If so, what is a recommended solution besides having them plug in
frequently?

But why does this only seem to affect the windows 7 machines? Windows XP
seems to stay.


"Bill Kearney" <> wrote in message
news: t...
> Set up DHCP reservations for them? Or configure DNS and DHCP not to
> expire records so soon?
>
> "JackH" <> wrote in message
> news:...
>>I have started deploying Windows 7 on netbooks within the organization.
>>What I have noticed is the machines seem to be removed from DNS after some
>>period of time. Staff usually connect via Cisco VPN and don't always
>>physically plug into the network on a regular basis. Could this be the
>>problem? If so, what is a recommended solution besides having them plug
>>in frequently?
>>

I've noticed additional info today.

This is also happening with windows xp machines not using VPN.
I'm wondering if DHCP is the issue.

the original DHCP is still running on the old domain controller on the old
domain. The machines in question are running on the new 2008 domain. I've
been manualy setting the DNS to the new dns servers on the new domain on the
machines until I'm ready to switch to the new dhcp server. Could this be
causing the issue? I didn't think DHCP did anything with DNS other than
handing out the IPs and DNS settings. The machines themselves are set to
register DNS.


"Bill Kearney" <> wrote in message
news: t...
> Well, without a lot more information about how the two different machines
> are configured, it's impossible to guess.
>
> I'd be inclined to think it has something do with how the DHCP leases are
> being setup, AND how they're being doled out through the VPN connections.
> Typical mistakes like having too few address setup for leases out through
> the VPN. The addresses get recycled more often than is desired. There
> are, however, good reasons for limiting the number of addresses made
> available on the VPN, and whether they're deliberately released upon
> disconnect.
>
>
> "JackH" <> wrote in message
> news:...
>> But why does this only seem to affect the windows 7 machines? Windows XP
>> seems to stay.
>>
>>
>> "Bill Kearney" <> wrote in message
>> news: t...
>>> Set up DHCP reservations for them? Or configure DNS and DHCP not to
>>> expire records so soon?
>>>
>>> "JackH" <> wrote in message
>>> news:...
>>>>I have started deploying Windows 7 on netbooks within the organization.
>>>>What I have noticed is the machines seem to be removed from DNS after
>>>>some period of time. Staff usually connect via Cisco VPN and don't
>>>>always physically plug into the network on a regular basis. Could this
>>>>be the problem? If so, what is a recommended solution besides having
>>>>them plug in frequently?
>>>>
>>
>>
>

Ignore that last post. They are registering in DNS.


"JackH" <> wrote in message
news:...
> I've noticed additional info today.
>
> This is also happening with windows xp machines not using VPN.
> I'm wondering if DHCP is the issue.
>
> the original DHCP is still running on the old domain controller on the old
> domain. The machines in question are running on the new 2008 domain.
> I've been manualy setting the DNS to the new dns servers on the new domain
> on the machines until I'm ready to switch to the new dhcp server. Could
> this be causing the issue? I didn't think DHCP did anything with DNS
> other than handing out the IPs and DNS settings. The machines themselves
> are set to register DNS.
>
>
> "Bill Kearney" <> wrote in message
> news: t...
>> Well, without a lot more information about how the two different machines
>> are configured, it's impossible to guess.
>>
>> I'd be inclined to think it has something do with how the DHCP leases are
>> being setup, AND how they're being doled out through the VPN connections.
>> Typical mistakes like having too few address setup for leases out through
>> the VPN. The addresses get recycled more often than is desired. There
>> are, however, good reasons for limiting the number of addresses made
>> available on the VPN, and whether they're deliberately released upon
>> disconnect.
>>
>>
>> "JackH" <> wrote in message
>> news:...
>>> But why does this only seem to affect the windows 7 machines? Windows
>>> XP seems to stay.
>>>
>>>
>>> "Bill Kearney" <> wrote in message
>>> news: t...
>>>> Set up DHCP reservations for them? Or configure DNS and DHCP not to
>>>> expire records so soon?
>>>>
>>>> "JackH" <> wrote in message
>>>> news:...
>>>>>I have started deploying Windows 7 on netbooks within the organization.
>>>>>What I have noticed is the machines seem to be removed from DNS after
>>>>>some period of time. Staff usually connect via Cisco VPN and don't
>>>>>always physically plug into the network on a regular basis. Could this
>>>>>be the problem? If so, what is a recommended solution besides having
>>>>>them plug in frequently?
>>>>>
>>>
>>>
>>
>
>

"JackH" <> wrote in message news:...
> I've noticed additional info today.
>
> This is also happening with windows xp machines not using VPN.
> I'm wondering if DHCP is the issue.
>
> the original DHCP is still running on the old domain controller on the old
> domain. The machines in question are running on the new 2008 domain. I've
> been manualy setting the DNS to the new dns servers on the new domain on the
> machines until I'm ready to switch to the new dhcp server. Could this be
> causing the issue? I didn't think DHCP did anything with DNS other than
> handing out the IPs and DNS settings. The machines themselves are set to
> register DNS.
>
>

Are you saying you have two different domains that are not of the same forest, on the same physical network? If so, you are saying the old domain controller is still the DHCP server for all DHCP client machines both domains on the same physical network? If that's the case, I assume on the old DHCP server, Option 006 (the DNS addresses it gives out), are still pointing to the old domain controller DNS server. If not, and the old DHCP server's Option 006 is set to the new 2008 DNS server (on the new domain), then I can see an issue if the zone is set to Secure Updates only. First, that would keep the old DHCP server from registering into the zone(s), and second, if set to Unsecure and Secure updates, the old DHCP server cannot own the record in order to update any changes.

Windows DHCP and Windows DNS works hand in hand to provide Dynamic DNS Updates. The DHCP server will register the A record in the forward lookup zone, and the client machine itself will register the PTR record. That's by default. If you are in a mixed, co-existing environment, you are introducing numerous variables that may alter this behavior, depending on what settings you've set on the zone, and in DHCP properties, as well as suffix settings on the machine and/or DHCP Option 015. This makes it extremely difficult to diagnose without knowing all the specifics on each side (DHCP options settings, suffixes on the machine, which domain they are joined to, zone settings, DHCP property settings, scavenging, TTL of the records, etc).

My suggestion is to move everything over as soon as you can to eliminate the complex variables, retire the old system, and go from there.


--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and confers no rights.

Please reply back to the newsgroup or forum for collaboration benefit among responding engineers, and to help others benefit from your resolution.

Ace Fekay, MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
Microsoft MVP - Directory Services

If you feel this is an urgent issue and require immediate assistance, please contact Microsoft PSS directly. Please check http://support.microsoft.com for regional support phone numbers.

You are correct!! I thought I had updated it but had not.

I have one remote site now completely using the scope on the new DHCP server
and it is working perfectly. I can't wait to get everything over and off
that ancient DC.




"Ace Fekay [MVP-DS, MCT]" <> wrote in message
news:...
"JackH" <> wrote in message
news:...
> I've noticed additional info today.
>
> This is also happening with windows xp machines not using VPN.
> I'm wondering if DHCP is the issue.
>
> the original DHCP is still running on the old domain controller on the old
> domain. The machines in question are running on the new 2008 domain.
> I've
> been manualy setting the DNS to the new dns servers on the new domain on
> the
> machines until I'm ready to switch to the new dhcp server. Could this be
> causing the issue? I didn't think DHCP did anything with DNS other than
> handing out the IPs and DNS settings. The machines themselves are set to
> register DNS.
>
>

Are you saying you have two different domains that are not of the same
forest, on the same physical network? If so, you are saying the old domain
controller is still the DHCP server for all DHCP client machines both
domains on the same physical network? If that's the case, I assume on the
old DHCP server, Option 006 (the DNS addresses it gives out), are still
pointing to the old domain controller DNS server. If not, and the old DHCP
server's Option 006 is set to the new 2008 DNS server (on the new domain),
then I can see an issue if the zone is set to Secure Updates only. First,
that would keep the old DHCP server from registering into the zone(s), and
second, if set to Unsecure and Secure updates, the old DHCP server cannot
own the record in order to update any changes.

Windows DHCP and Windows DNS works hand in hand to provide Dynamic DNS
Updates. The DHCP server will register the A record in the forward lookup
zone, and the client machine itself will register the PTR record. That's by
default. If you are in a mixed, co-existing environment, you are introducing
numerous variables that may alter this behavior, depending on what settings
you've set on the zone, and in DHCP properties, as well as suffix settings
on the machine and/or DHCP Option 015. This makes it extremely difficult to
diagnose without knowing all the specifics on each side (DHCP options
settings, suffixes on the machine, which domain they are joined to, zone
settings, DHCP property settings, scavenging, TTL of the records, etc).

My suggestion is to move everything over as soon as you can to eliminate the
complex variables, retire the old system, and go from there.


--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Please reply back to the newsgroup or forum for collaboration benefit among
responding engineers, and to help others benefit from your resolution.

Ace Fekay, MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE &
MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
Microsoft MVP - Directory Services

If you feel this is an urgent issue and require immediate assistance, please
contact Microsoft PSS directly. Please check http://support.microsoft.com
for regional support phone numbers.

"JackH" <> wrote in message news:...
> You are correct!! I thought I had updated it but had not.
>
> I have one remote site now completely using the scope on the new DHCP server
> and it is working perfectly. I can't wait to get everything over and off
> that ancient DC.
>


I'm glad I was able to help. Now let's get rid of the old, and move on with the new!!!!

Ace

Hey ACe, while I have your attention. Do you have any tips on fine tuning
2008 terminal server? I have a 32bit access runtime I have to use and it
seems to slow down or hog the servers. The vendor won't be coming out with
a x64 till at least the end of the year.



"Ace Fekay [MVP-DS, MCT]" <> wrote in message
news:...
"JackH" <> wrote in message
news:...
> You are correct!! I thought I had updated it but had not.
>
> I have one remote site now completely using the scope on the new DHCP
> server
> and it is working perfectly. I can't wait to get everything over and off
> that ancient DC.
>


I'm glad I was able to help. Now let's get rid of the old, and move on with
the new!!!!

Ace

"JackH" <> wrote in message news:...
> Hey ACe, while I have your attention. Do you have any tips on fine tuning
> 2008 terminal server? I have a 32bit access runtime I have to use and it
> seems to slow down or hog the servers. The vendor won't be coming out with
> a x64 till at least the end of the year.
>
>
>
> "Ace Fekay [MVP-DS, MCT]" <> wrote in message
> news:...
> "JackH" <> wrote in message
> news:...
>> You are correct!! I thought I had updated it but had not.
>>
>> I have one remote site now completely using the scope on the new DHCP
>> server
>> and it is working perfectly. I can't wait to get everything over and off
>> that ancient DC.
>>
>
>
> I'm glad I was able to help. Now let's get rid of the old, and move on with
> the new!!!!
>
> Ace
>
>

No, sorry, not really. I would take a look at the app itself and see what they have to offer to increase efficiency.

Ace




--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and confers no rights.

Please reply back to the newsgroup or forum for collaboration benefit among responding engineers, and to help others benefit from your resolution.

Ace Fekay, MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
Microsoft MVP - Directory Services

If you feel this is an urgent issue and require immediate assistance, please contact Microsoft PSS directly. Please check http://support.microsoft.com for regional support phone numbers.