Remote admin stops working

[indisbaltic]

Hi,

We're running the FTP server on a Win2K server, dedicated IPaddress with the FTP server @ port 82 and the remote admin at port 81. Remote admin only works for a few pages (~20, clicking on some options, seeing som evalues) and afterwards it 'freezes': page cannot be loaded. Nothing appears in the event logs.
FTP server keeps on working, it's just the remote admin. Only restarting the ability service solves it. Any ideas how to overcome this ?

Best,

Peter Quintus

[Code Crafters]

This could be an issue with your browser, antivirus software maybe or even your network connectivity. If the FTP server doesn't record any problems in the logs then the request isn't making it to the FTP server. Try access to remote admin from the FTP server machine to see if that works ok and slowly work backwards checking all firewalls, router, antivirus and different browsers to see if you can identify the cause of the problem.

[indisbaltic]

Hi Chris,

Also checked it directly on the server, when Remote Admin 'hangs', it also 'hangs' when I try to access it directly on the server.
Nothing strange appears in the logfiles. Any possibility to perhaps log more ? (like verbose) ?

Cheers,

Peter

[Code Crafters]

There should be no reason why the remote admin session hangs on login unless you mail server is very busy. There are logging settings that allow you to use debug logs for each of the areas of the mail server.

[indisbaltic]

Hi Chris,

Mailserver? I was talking about the FTP server, in fact that server doens't run any mailserver only IIS, bind to a different IP address.
Remote admin doesn't hang on login, it hangs (doesn't respond) after ~20/30 actions/pageviews. Only restarting the service solves it.
What does it actually use for the remote admin HTTP ? Some built in little webserver?

[Code Crafters]

Sorry, FTP server remote admin. We haven't had any other reports of this problem occuring but will look into it. If we can replicate the problem, we can fix it so any other information you can give as to your operating system, browser and version etc. would help. Remote admin uses Code-Crafters own built in web server with custom scripting to allow more flexible implementation.

[indisbaltic]

Chris, any news ?
We are using a Win2K server with IIS and MS FTP running on one IPaddress and Ability FTP/Remote admin on a different IPaddress (not the localhost one). Perhaps that could be the issue ? That somewhere internally there is reference to localhost instead of the IPaddress specified as to which it should listen ?

Cheers,

Peter

[Code Crafters]

I think I might know what the problem is here. If you are running remote admin on the same port as IIS is running websites etc. then there is a bug within IIS that causes it to wrongly grab all IPs, bind to the ones it wants then release the others for other applications to use. It shouldn't do this and this causes other applications to not be able to bind properly until IIS is finished. With our mail server we added an option to start the service after a delay period to allow IIS to finish hogging all the IPs for its ports. We will try to build this into the FTP. For now though, I'd advise you either use a different port for Remote Admin, or there is also a microsoft article on how to fix the IIS problem. If you aren't binding to ports that IIS is using then just make sure that you are binding to an IP that exists on your FTP server computer and use the IP not localhost or other domains.

[indisbaltic]

Changed it and seems to be working now (at least already much longer than before).
If anything happens I'll let you know. Still you might want to change the URL that loads when you click on the console to start up Remote Admin. It defaults to localhost:prt nr and not to the entered IPaddress: prt nr

Cheers,

Peter

[Code Crafters]

That's possibly Windows translating the IP using its hosts file but I'll check it out anyway. Glad you got sorted out.

[indisbaltic]

Hi Chris,

Unfortunately it is not yet solved. Remote admin works more stable since it listens to port 83, but still it simply stops working sometimes after a little while, sometimes after a longer while. The client also contacted you and to them you replied that port 7088 on the server should be reachable. It is, it's not blocked by a firewall nor by a router. It could be related to sessions that are not being kept alive, any ideas on that one ?
Else, it could be that remote admin stops working when for instance a port scan is being performed, any ideas on that one?

Bottom line is that the software is unfortunately still not working the way it should and the client is getting a bit desperate....

Best,

Peter

[Code Crafters]

Port 7088 is the default remote admin port. If you are using a different port (e.g. 82) then 7088 doesn't need to be used at all. When remote admin stops working try connecting to it directly on the FTP server machine to see if the problem still exists whent he firewalls and router don't interfere with the connections. If it does work locally then at least the software is ok and its either firewalls, routers, antivirus software, your browser, client computer or connection to the FTP server that's the problem. Start at the FTP server machine and work backwards from there eliminating each of the potential causes above to try to find the cause of the problem.