>
> I found the problem and fixed it.  It turned out the some other program 
> was listening on port 21234.  Changing to a new port (21235) fixed the 
> issue.
>
 
For others troubeshooting this problem, run netstat -an from the commands 
line and look for a listener on 21234.  You can run netstat -anb to get 
name of listener.  In my case, though, it was a "unknow" listener.
 
Regards,
 
erd

>  
>

Reply via email to