I've already thought about a scheduling a .cmd to run at regular intervals.
These computers are left logged in "24x7xuntil it dies" so a Startup Program
wouldn't do it (when I say log in remotely, it's via a pc-anywhere type
app). Release / Renew wouldn't work because I use static IP addresses.
I was actually hoping for a solution to force XP to manage its DNS records
like a Windows Server, but I guess that's not possible? If that is not
possible, I will schedule a job to refresh the records.
Thanks for the response
"Kelly" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> Hi Jeremy,
>
> Copy what is listed below into notepad and save as flushdns.cmd with
> quotes as in:
>
> "flushdns.cmd" and place into All Users/Startup Folder
>
> Modify as needed:
>
> ipconfig /release
> ipconfig /renew
> ipconfig /flushdns
> ipconfig /registerdns
>
>
> --
>
> All the Best,
> Kelly (MS-MVP/DTS&XP)
>
> Taskbar Repair Tool Plus!
> http://www.kellys-korner-xp.com/taskbarplus!.htm
>
>
> "Jeremy" <trombone79atgmail.com> wrote in message
> news:(E-Mail Removed)...
>>I have a few computers with Windows XP running apps that don't required
>>full blown server.
>>
>> - They all have static IP addresses configured
>> - They all have multiple DNS servers configured
>> - Each DNS server on our network is also a Domain controller, running
>> Active Directory integraded zones and are configured properly for forward
>> and reverse lookups.
>> - The Windows XP installs are very clean, simply Windows, the app(s) and
>> antivirus. Almost no human interaction.
>>
>> After they are running for a period of a few months, the DNS records
>> disappear. I'm assuming they become stale and are scavenged. We then
>> loose all functionality requiring access to the computer by name, which
>> is pretty much all functionality.
>>
>> I can log in via IP and type 'ipconfig /registerdns', and that gets
>> things rolling again. I want to know if there is a setting in Windows XP
>> to refresh its DNS records on a regular basis so I'm not forced to do it
>> manually.
>>
>> This of course in not an issue on our Windows 2003 member servers
>> configured identically.
>>
>> Thanks
>>
>