NTP access (AtomTime)

[PoorJohn]

I finally got around to upgrading to WinGate 6 something ("revision" just assures me that I'm running the "latest version") from 2.something, and broke my AtomTime path to NTP. I don't see what setting I've allowed to be different between the two installations.

AtomTime allows one to specify a proxy IP and port, which is set to 80 in the old version. Neither that nor 123 work in the new configuration. According to the developer's notes, the error says AtomTime is finding the time server but not receiving a reply.

If I tell AtomTime to *not* use the proxy, it promptly connects and obtains the correct time. This is true of computers on the internal network as well as the WinGate server.

The WinGate server is on an XPsp3 machine; most of the others are on XPsp2.

When I get that fixed I'll probably have TiVo's connection to make work. Its first whimper will be a need for icmp both ways, plus a bunch of ports. Horribly designed, but you're not allowed to mention that in the Halls of TiVo.

[adrien]

Hi

NTP uses UDP I thought, so using an HTTP (port 80) proxy wouldn't normally work - or is there a TCP mode?

By removing proxy settings, you would have gone over to a NAT connection. WinGate 2 didn't have NAT. So that would account for the difference.

[PoorJohn]

Ah, if I don't bother to tell my internet-accessing clients that there's a proxy server, they do indeed manage to find their own way. I wouldn't run a life-support system on it, but it's pretty good, especially if it remains useful as a firewall while transparently doing its thing.

Kaspersky, otoh, is up to its old tricks - 'unexpected error scanning file'. Kaspersky says it's version 3.0.4. If that's the proper version, I'd be hard pressed to be a happy customer. Doesn't do it often, but 'never' is my expectation. Note that this is a completely new installation - new 2.8 GHz 1GB machine with a clean installation of XPSP3 and doing absolutely nothing but running Wingate, GateKeeper, and Task Manager.