Posted:  18 Aug 2010 18:04   Last Edited By: Ash575
	Registered User Currently Offline	Posts:  3 Join Date: Aug 2010
I downloaded the trial version of this FTP server and got it to work once.  Now each time I try to start the server I get the Sysax Mulit Server service could nto be started. Checking the log files it says the ports are already in use. From a command prompt I do a netstat -a to see what ports are in use:   Proto  Local Address          Foreign Address        State   TCP    0.0.0.0:80             <servername>:0          LISTENING   TCP    0.0.0.0:135            <servername>:0          LISTENING   TCP    0.0.0.0:443            <servername>:0          LISTENING   TCP    0.0.0.0:445            <servername>:0          LISTENING   TCP    0.0.0.0:3389           <servername>:0          LISTENING   TCP    0.0.0.0:5357           <servername>:0          LISTENING   TCP    0.0.0.0:47001          <servername>:0          LISTENING   TCP    0.0.0.0:49152          <servername>:0          LISTENING   TCP    0.0.0.0:49153          <servername>:0          LISTENING   TCP    0.0.0.0:49154          <servername>:0          LISTENING   TCP    0.0.0.0:49155          <servername>:0          LISTENING   TCP    0.0.0.0:49174          <servername>:0          LISTENING   TCP    0.0.0.0:49177          <servername>:0          LISTENING   TCP    192.168.102.242:80     <servername>:58359      TIME_WAIT   TCP    192.168.102.242:80     <servername>:58366      TIME_WAIT   TCP    192.168.102.242:80     <servername>:58368      TIME_WAIT   TCP    192.168.102.242:80     <servername>:58370      TIME_WAIT   TCP    192.168.102.242:139    <servername>:0          LISTENING   TCP    192.168.102.242:3389   <servername>::1369        ESTABLISHED   TCP    192.168.102.242:49220  <servername>:microsoft-ds  ESTABLISH   TCP    192.168.102.242:49249  <servername>:microsoft-ds  ESTABLISH   TCP    192.168.102.242:49250  <servername>:microsoft-ds  ESTABLISH   TCP    192.168.102.243:80     <servername>:30152      TIME_WAIT   TCP    192.168.102.243:80     <servername>::30201      TIME_WAIT   TCP    192.168.102.243:80     <servername>:30243      TIME_WAIT   TCP    192.168.102.243:80     <servername>:30278      TIME_WAIT   TCP    [::]:80                <servername>:0          LISTENING   TCP    [::]:135               <servername>:0          LISTENING   TCP    [::]:443               <servername>:0          LISTENING   TCP    [::]:445               <servername>:0          LISTENING   TCP    [::]:3389              <servername>:0          LISTENING   TCP    [::]:5357              <servername>:0          LISTENING   TCP    [::]:47001             <servername>:0          LISTENING   TCP    [::]:49152             <servername>:0          LISTENING   TCP    [::]:49153             <servername>:0          LISTENING   TCP    [::]:49154             <servername>:0          LISTENING   TCP    [::]:49155             <servername>:0          LISTENING   TCP    [::]:49174             <servername>:0          LISTENING   TCP    [::]:49177             <servername>:0          LISTENING   UDP    0.0.0.0:123            *:*   UDP    0.0.0.0:500            *:*   UDP    0.0.0.0:3702           *:*   UDP    0.0.0.0:3702           *:*   UDP    0.0.0.0:4500           *:*   UDP    0.0.0.0:5355           *:*   UDP    0.0.0.0:58039          *:*   UDP    127.0.0.1:51840        *:*   UDP    127.0.0.1:51842        *:*   UDP    127.0.0.1:54939        *:*   UDP    127.0.0.1:56354        *:*   UDP    127.0.0.1:59145        *:*   UDP    127.0.0.1:61120        *:*   UDP    192.168.102.242:137    *:*   UDP    192.168.102.242:138    *:*   UDP    [::]:123               *:*   UDP    [::]:500               *:*   UDP    [::]:3702              *:*   UDP    [::]:3702              *:*   UDP    [::]:5355              *:*   UDP    [::]:58040             *:* I dont see where 21, 88 or 990 are in use.  Anything else to check? Thanks

Posted:  18 Aug 2010 21:38
	Registered User Currently Offline	Posts:  3 Join Date: Aug 2010
Looks like I fixed this issue.  I had to uninstall and then search through the registry to find all entries for Sysax and delete those as well.  Rebooted the server.. Installed the softare and it started to work again.

Posted:  09 Feb 2011 13:35
	Moderator Currently Offline	Posts:  367 Join Date: Nov 2008
The most common reason for this problem is that the server software is configured to use a port that is already being used by another application. Under windows only one application can have access to a specific ip address-port combination. ------------------------------------ Secure FTP Server Solutions simplified

Copyright © 2021 Codeorigin, LLC - All Rights Reserved.
RSS 2.0 Atom 1.0