Encountering the frustrating “There is a time and/or date difference between the client and the server” error when using PsExec on a Windows XP machine? You’re not alone. This, coupled with “access denied” messages when attempting remote time synchronization via commands like at \clientname time /interactive "net time \server /set /y", can severely hinder remote management efforts. Many administrators face this challenge when dealing with older systems like Windows XP, especially given its release date was back in 2001, and the potential for configuration drift over time is significant. Directly accessing the machine to run net time locally resolves the issue, but a remote solution is always preferable. Let’s explore a reliable remote fix.
Remote Solution for PsExec Time and Access Issues on Windows XP
Thanks to a clever workaround leveraging local administrator accounts, a fully remote solution is indeed achievable. This method is particularly effective in environments where, common in many organizations at the time of Windows XP’s widespread use post-release date, PCs share the same local administrator account credentials.
Initially, the remote solution might appear to fail if a domain administrator account with identical login credentials exists. To circumvent this, temporarily disable the conflicting domain administrator account. Once disabled, PsExec can successfully utilize the local admin credentials. The command structure is as follows:
>psexec \systemname -u Administrator cmdInterestingly, even after establishing a successful PsExec session via the local admin account, direct time synchronization commands like time or net time might still prove problematic. Remote execution of net time might seem successful, but local review of scheduled “at” commands often reveals a “could not start” error.
However, the crucial observation is that a successful remote connection using the local admin account unlocks the ability to use regular PsExec with your domain account. Furthermore, network access via Explorer using the system name (e.g., \systemname) becomes possible:
alt text
Once remote access is restored, the next step involves utilizing Scheduled Tasks. Create a new scheduled task with your domain administrator account credentials. The task should execute the following command:
net time \servername /set /yesAfter configuring the scheduled task, simply right-click on it and select “Run”. This action should successfully synchronize the time on the Windows XP machine with your server.
To validate this fix, experiment on another desktop. Intentionally skew the system time to replicate the initial “time difference” condition that triggers the PsExec errors. Then, apply the described remote fix. The solution should effectively resolve the time synchronization issue and restore remote management capabilities, even on systems running an operating system as mature as Windows XP, long past its initial release date.
Conclusion
This method provides a robust remote solution for resolving “time difference” and “access denied” errors when using PsExec on Windows XP. By leveraging local administrator accounts and scheduled tasks, you can effectively synchronize system time and regain remote access, even without physically interacting with the machine. This is particularly valuable for maintaining and managing older Windows XP systems, remembering its release date marks a significant point in computing history, yet these systems still require management in some environments today.
