Is it impossible to sync time on Windows XP?

2,431

The following KB article covers setting up (and troubleshooting) the ability of Windows to sync with an external NTP time source:

http://support.microsoft.com/kb/816042

In the troubleshooting section, it says:

Troubleshooting

For the Windows Time service to function correctly, the networking infrastructure must function correctly. The most common problems that affect the Windows Time service include the following:

There is a problem with TCP/IP connectivity, such as a dead gateway.
The Name Resolution service is not working correctly.
The network is experiencing high volume delays, especially when synchronization occurs over high-latency wide area network (WAN) links.
The Windows Time service is trying to synchronize with inaccurate time sources.

2,431

skel625

Updated on September 17, 2022

Comments

skel625 almost 2 years
Auto-binding of request params seems like default behaviour, but I can't find a lot of documentation on it. Here is my example:
```
<form:form modelAttribute="test" action="testsubmit.do" method="POST">
  Name: <form:input path="name" />
  Nested Name: <form:input path="test.nestedName"/> 
<input type="submit"/>
```
```
public class Test {
    public String name;
    public String name2;
    public TestNested test;
    ...
```
```
public class TestNested {
    public String nestedName;
    ...
```
Now with my mapping:
```
@RequestMapping(value = "/testsubmit")
public String testSubmit(Test test){
    ...
```
The test object is binding the form values including the nested value. This seems to me like expected behavior, but I am a bit confused by the @ModelAttribute annotation and its use with respect to objects specified as mapped method parameters.

15.3.2.8 Providing a link to data from the model with @ModelAttribute says:

When you place it on a method parameter, @ModelAttribute maps a model attribute to the specific, annotated method parameter (see the processSubmit() method below). This is how the controller gets a reference to the object holding the data entered in the form.

When I bind the object test to the form on load, I set a value to name2.
```
@RequestMapping(value = "/test")
public String test(Model model) {       
    Test test = new Test();
    test.setName2("test name2");
    model.addAttribute("test", test);
    return "test";
}
```
This doesn't get passed through on the submit method when I annotate the test parameter with @ModelAttribute("test"):
```
@RequestMapping(value = "/testsubmit")
public String testSubmit(@ModelAttribute("test") Test test) {
    ...
```
This is expected to me as name2 was not specified as a form field/request param, but it doesn't help me understand the point of the @ModelAttribute("test") usage. Can anyone shed some light on this for me?
Admin over 14 years

No, no firewall.
memoryisram over 14 years

1. I tracert time.nist.gov and saw no dead gateway 2. Name resolution works 3. Does not explain why I get an error every time 4. I tried every time service
Sean Earp over 14 years

In the middle of that KB article are some steps that involve changing registry settings. Take a look at the section titled: Configuring the Windows Time service to use an external time source
Sean Earp over 14 years

Oh! I just remembered the solution that worked for me back in the day when I was building new computers... if the time/date (as set in Windows) is too far off from the real time (I don't know the threshold, maybe a day?), Windows will not update via NTP. Try setting the time to something close to the real time and try again. If that didn't work, just waiting a day or so usually resolved whatever random intermittent problem I was hitting.
user5336 over 14 years

If it's only 2-3 seconds off, though, I think that's permissible ntp drift, and it would resync properly after not long.
memoryisram over 14 years

thanks for the answers, i am still at a loss though