"JayDee" <> wrote in message
news:0218dad7-3642-4962-8533-...
> we have computers that are built on a lab subnet, then put into
> production when it is finished. we've found that when we move the
> computers from one subnet to another, they do not register their -new-
> IP address for a few days (there are no problems with the initial
> registration, and that is the entry that remains when it is moved)
>
> I'm thinking this might have something to do with the 2003 refresh
> interval settings and if so, why not make these values minimal?
>
> what else might i check if not for these settings?
>
> thanks!
>
> - j
By default, it should register within 15 minutes. If you are looking at a
DNS server in a different Site, then it will take longer, depending on your
Site replication schedule. If it is not registering until 3 days later, than
something has been changed or altered from the defaults, or the client
machine (if it is a client machine), is not configured properly, such as
using an ISP's DNS, Primary DNS suffix doesn't match, etc.
Are the machines DHCP or static configurations?
When you run an ipconfig /registerdns, does it register within 15 minutes?
Please provide an ipconfig /all from the client machine so we can get a
better idea and evaluate the config.
--
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, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA
2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
For urgent issues, please contact Microsoft PSS directly. Please check
http://support.microsoft.com for regional support phone numbers.