Hi Gary, The simplest (and most reliable) test is to send a "ping" from the client. This is found in the "Link" drop down menu (or executed by pressing CTRL-P). You should see in the following frame transmitted in the client's Fldigi: <SOH>00uVE6UQ:7 1234<EOT> The 1234 sequence will be different since it is the check sum and dynamically calculated. I would then check that: 1. The server's Fldigi shows the same frame as received 2. If it is received ok but the server does not reply within 30 seconds, then something is wrong on the server side. If that is the case I would make sure that I started Fldigi first, then the server software. 3. If the server did respond to the ping (non server specific) but not to a connect request then it could be a question of your client not using the proper call-sign when trying to connect. Check that the bottom right box on the pskmail client corresponds to your server's call sign (the one listed in the file pskmailrc.pl in the .pskmail folder under your home folder). Please tell us how far you went in this test sequence and we can take it from there. Good luck, 73, John On Thu, Jul 22, 2010 at 1:59 PM, <barkerg@xxxxxxxxxxxxx> wrote: > I just set up a server and was testing it from a client using a dummy load > on the client so as not to overload the server receiver. I can hear the > tones on the server receiver generated by the connect sequence from the > client but the server never responds. Both ends appear to be using PSK500R > according to the fldigi displays. The server is transmitting its beacon > which is heard on the client receiver audio. > > Can someone provide some troubleshooting tips on this? > > 73, > Gary > VE6UQ > > >