NTPD on RedHat ES4 not synching to Win2K3 domain controler

I’m having an incredibly difficult time trying to get my red hat server to sync its time to our 2K3 domain controller. I’ve been through numerous ntp.conf revisions and it always ends up that the domain controller is not even listed as a contender in the ntpq output. Even with my ntp.conf file at is most simple state:

server my.server.ip

it still fails to sync. It never receives an asterisk to indicate its synced up. If I include the local clock fudged to stratum 10 ntpd will even choose that over our domain controller. Something is quite wrong but I can’t seem to figure out what. This command works as expected:

ntpdate my.server.ip

it sets the system clock appropriately so I believe communications are working just fine.

Please help.
Thanks, Donovan

“The W32Time service is not a full-featured NTP solution that meets time-sensitive application needs.”

IMHO it gives an answer to a simple ntpdate command, but it advertises itself as a non-reliable source to any ntpd client.

Check more discussion of this question.

Related posts:

1. Why is ntpd not updating the time on my server?
2. Configure ntpd to just measure, don’ set the clock?
3. From Win2k3 Secondary DC to Primary DC of New Domain?
4. System clock drifting out of sync with hwclock and ntpd
5. Using NTPD on OpenBSD to get time from Linux using portforwarding