Windows Forum

Ask something
Discussion Locked

Port 123 unavailable

0 helpful
9 replies

by ctdak 2 views

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have used the "net time /setsntp:192.5.41.209" command to set my server's time with the US Naval Observatory clock. My server dials out every 15 or 45 minutes (whatever the default is) trying to synchronize with this clock. I believe I'm not getting out on port 123 and that's why the server keeps on trying. Port 123 must be unavailable for some reason. Is there a way to find out what (if anything) is using port 123? Can another port be used instead for this function? If so, how do you change the SNTP port default. (Note: This was happening before I put a hardware firewall in place, so it?s not related to the firewall.)

9 replies

by lordinfidel

I know that this is not the answer you were looking for.

But what address are you pointing to for the USNO. The reason I ask this, is because I noticed last week that my time synch program started throwing connection errors to the USNO.

I have not gotten around yet to looking into it. But if you are not able to connect all of a sudden and you are going to basically the same place I am, then it might be an issue on their end.

Just a thought.

by ctdak

I am using 192.5.41.209 or 192.5.41.41 for USNO. I have never had success getting synched with either of these addresses over several months.

by lordinfidel

You can run this command from a command prompt. (assuming nt or 2k)
(start/run/type cmd /press ok)

netstat -a (enter)

This will list all ports that are active on your machine.

To see if your server is reacting to the 123 port, you can also ping the server with this command: where x = ip adress of server.
(*note run this on the server, not remotely, and not loopback)

ping x.x.x.x -v 123

You should get an output like this x4
Reply from x.x.x.x: bytes=32 time<10ms TTL=128

You will notice that ping translated the 123 port to time. If it did not translate it then that may be your problem.

Try running the command again but instead of using 123 use the word time ( -v time)

What happens?

Look for anything that is connected to either time or 123 (both udp and tcp)

Did you open up both udp and tcp 123 at the firewall or just tcp 123. (i know you said that it was before the firewall was installed) The second part to this is do you have any filters installedon your adapters?
(right click net neighb/properties/right click on adapter/properties, click tcp/ip/properties/advanced/options/ip filters) Make sure that you have the appropiate filters, If you have them set up at all. If there are no filters then disregard this section.

Remember that NTP/time is a RFC standard protocol. Not wise to try to change it's mapping.

by lordinfidel

******

If all else fails. Remove TCP/IP.... Reboot. Then add it back in.

It could just be a problem with the stack, maybe something corrupted the stack.

Does this machine have the latest SP, and was any hotfixes applied?

by curlergirl

I forgot you had said you were using a firewall but the problem happened before it was put in place. I'd double-check anyway to make sure it's not blocking port 123.

This discussion is closed to new replies.