udp with suspect cable

[pjackson59]

Hello All,

Not exactly a Labview question but I know there are a lot of smart people here.

We have a PC104 computer running WinXP Embedded which is inside a control can which will be at the bottom of the ocean. There is an ethernet connection which has to run through connectors on the can. As a result, this connection is not as good as a regular LAN connection. I am trying to get an NTP client (K9nt) running, which uses UDP port 123.

I created a small Labview program to open a UDP port and display whatever is received.

If I connect a regular ethernet cable directly to the computer, I receive messages on port 123, and K9nt works as expected.

If I connect through the connectors, I can connect with Remote Desktop, ping the server repeatedly with no errors, the main program (written in Labview)  will send and receive UDP commands from a host computer on port 61557 and 61556, my test program displays the commands being sent on 61556, but K9nt will not receive time broadcasts, and my test program receives nothing on port 123.

Does anyone have any hints on this?

Thanks in advance,

Paul J

[Joseph_Loo]

I was looking at k9nt. There does not seem to be a configuration item, I suspect there is a reg edit that might work. The question should be asked, how would k9nt determine that the UDP packets are coming in your new port location. If you can not answer that, then there is a good chance that k9nt can not do it either. You will need to have another ntp program that you can configure the ntp port location.