Messages

1

router & port problems / IIS - range of ports?

« on: November 03, 2009, 08:00:49 AM »

Thank you, Bacter.

I am going to try your suggestions this morning, but I can anticipate a couple of answers:

1. When IIS is running, HFS self test says that I am behind a router, which is true. The thing is that HFS sends a frame but cannot receive the answer through the port it is listening on. I think it has to do with your second suggestion: IIS does not probably only take port 80 or 8080, but a whole range of ports. I will check it thoroughly this morning and let everybody know about the outcome.

2. I have just called my colleague and he says that all our ports are closed, except for those that we specifically open, like 80, 8080, 21 and so on (you know, the standard ones). So, what if we opened a very specific, non-standard port like, e.g. 60001 and set HFS to listen on this one? If we did and it worked, would we always need to specify the port number directly at the address bar of the browser?

Again, my sincere thanks for your help, guys.

2

router & port problems / Re: HFS not compatible with IIS?

« on: October 30, 2009, 07:52:55 PM »

Thank you, Maverick.

I had already tried that but, instead of using port 81, I have set up HFS to use only 8080. No way. It keeps on displaying the same Under construction page (it comes from IIS).

Any other suggestions?

3

router & port problems / HFS not compatible with IIS?

« on: October 30, 2009, 05:31:45 PM »

Hello, there.

I have read many topics in the forum related to port forwarding and so on, but I think my case is specific (I hope it's not):

Last week, I tested HFS working on my local server machine and everything was fine. Either with a fixed port or a dynamic one (I have a static WAN address). Great job and fantastic app! Thanks a lot.


The problem is: my colleague needed to install a web application he had written and it is a requirement that it is run on IIS. He got it working, BUT HFS will not accept any connection from the outside (it does from any machine in the internal network). OK, it shouldn't be a big trouble, as I thought it would be as easy as configuring HFS to listen on a different port (I tried 8181), as it seems that IIS will take all standard HTTP ports, e.g. 80 and 8080.

The thing: when I try to access my shared folder from anywhere else, it does not work and shows an "Under Construction" page presented by IIS. The same thing happens regardless specifying the port in the URL or not.

I needed then to make sure the problem was caused by IIS. How? I turn it off and everything comes back to normal use.

Does anyone here have an idea why this would happen? Any setting I should change in IIS? Platform is Windows 2003 Server with all patches and hotfixes installed.

Thank you so much in advance.