Nope...  they're still not updating properly.  Same error in Windows and the NTP reply looks the same:

Internet Protocol, Src: 207.46.130.100 (207.46.130.100), Dst: 10.227.10.44 (10.227.10.44)
Network Time Protocol
Flags: 0xdc
   11.. .... = Leap Indicator: alarm condition (clock not synchronized) (3)
Peer Clock Stratum: unspecified or unavailable (0)
Reference Clock ID: NULL
Reference Clock Update Time: Apr  3, 2007 17:00:27.2667 UTC
Originate Time Stamp: Apr 19, 2007 04:17:21.3438 UTC

This is with the new server, if the IP address given by Matthew is the correct one.