i!-Schedule Time Sync

TurnipTruck

Greetings,

In using the time sync function of I Schedule, I have selected DayTime protocol which calls for TCP and UDP port 13. Are those ports supposed to be forwarded to the master? Here is what the log is now showing since I added the I-Schedule time sync function. Please help. Is this working correctly?

Thank you.

97: 05-10-2006 WED 16:14:40 Interpreter CIpEvent::OnError 0:3:7
98: 05-10-2006 WED 16:14:40 Interpreter CIpEvent::OffLine 0:3:7
99: 05-10-2006 WED 16:14:40 SocketManager CIpSocketMan::ProcessPLPacket - Socket Already Closed
100: 05-10-2006 WED 16:14:39 Interpreter Exiting TCP Read thread - closing this socket for local port 3
101: 05-10-2006 WED 16:14:39 Interpreter CIpEvent::OnLine 0:3:7
102: 05-10-2006 WED 16:14:39 SocketManager Connected Successfully
103: 05-10-2006 WED 16:04:40 Interpreter CIpEvent::OffLine 0:3:7
104: 05-10-2006 WED 16:04:40 Interpreter Exiting TCP Read thread - closing this socket for local port 3
105: 05-10-2006 WED 16:04:39 Interpreter CIpEvent::OnLine 0:3:7
106: 05-10-2006 WED 16:04:39 SocketManager Connected Successfully
107: 05-10-2006 WED 15:54:40 Interpreter CIpEvent::OnError 0:3:7
108: 05-10-2006 WED 15:54:40 Interpreter CIpEvent::OffLine 0:3:7
109: 05-10-2006 WED 15:54:40 SocketManager CIpSocketMan::ProcessPLPacket - Socket Already Closed
110: 05-10-2006 WED 15:54:39 Interpreter Exiting TCP Read thread - closing this socket for local port 3
111: 05-10-2006 WED 15:54:39 Interpreter CIpEvent::OnLine 0:3:7
112: 05-10-2006 WED 15:54:39 SocketManager Connected Successfully
113: 05-10-2006 WED 15:44:40 Interpreter CIpEvent::OffLine 0:3:7
114: 05-10-2006 WED 15:44:40 Interpreter Exiting TCP Read thread - closing this socket for local port 3
115: 05-10-2006 WED 15:44:39 Interpreter CIpEvent::OnLine 0:3:7
116: 05-10-2006 WED 15:44:39 SocketManager Connected Successfully
117: 05-10-2006 WED 15:34:46 Interpreter CIpEvent::OnError 0:3:7
118: 05-10-2006 WED 15:34:46 Interpreter CIpEvent::OffLine 0:3:7
119: 05-10-2006 WED 15:34:46 SocketManager CIpSocketMan::ProcessPLPacket - Socket Already Closed
120: 05-10-2006 WED 14:36:37 Interpreter Exiting TCP Read thread - closing this socket for local port 3
121: 05-10-2006 WED 14:36:37 Interpreter CIpEvent::OnLine 0:3:7
122: 05-10-2006 WED 14:36:37 SocketManager Connected Successfully

DHawthorne

You only have to forward ports if the originator of the connection is outside your network. i!-TimeManager originates the connection, no forwarding is necessary. However, you do need to make sure the ports aren't blocked by a firewall. It is pretty standard to block the time server ports, but I don't think that is your issue.

That log shows connections being made, but an error happening after the connection. Add an ONERROR event to the IP device, and parse the return; Software History documents the IP connect error codes so you can get a better idea what is happening. My guess is it's timing out on the far end and you need to connect to a different server.