HFS not compatible with IIS?

[UserK]

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.

[maverick]

I don't use IIS so my reply to you is limited.  There shouldn't be a compatibility issue as others here have used them together.  A quick search led me to the following post which might solve your problem. 

 http://www.rejetto.com/forum/index.php?PHPSESSID=u0cmrd44ho9rmlsasgsf5rjac7&topic=5010.0

[UserK]

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?

[bacter]

there are several tings you can test:

1) What does de selftest of hfs say when IIS is running?

2) Without hfs running, check with some tool (for example: http://www.canyouseeme.org/ what ports are open on you system (and opened with IIS). May be that IIS in it's default configuration listens to a range of ports. See if you can change this configuration, or look for a port out of this range that you can then use for hfs.

[UserK]

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.

[bacter]

You can set hfs to listen to any free port, provided you open this port for incoming traffic in your router. Some ISP's block the standard ports so many hfs users must use alternative non standard ports. You can choose any port that is not used by any software on your systems. Do not use port numbers below 1024. See a list of default port assignment at http://en.wikipedia.org/wiki/List_of_TCP_and_UDP_port_numbers.

If you use any port different from the standard port for any protocol (http: 80, smtp: 25 ...), you have to specify the port number in the url (with port 4820 for example from wan: //userk.no-ip.org:4820 and from lan //computername(or local ip):4820.

If you use a domainname from no-ip or dyndns for example, you can also use a redirect service, that adds the port to the domainname, so your users from wan can use //userk.no-ip.org without specifying th port.

[ninjapimp]

i'm having difficulty in getting HFS to work alongside IIS 7.0

I run a windows server 2008 and host multiple IIs 7 websites

I've read in detail the above suggestions. tried several ports. gone into my router and done port mapping.

but I simply can not get HFS to work when IIS 7 is running.

if i disable IIS7 then HFS seems to work but the moment i turn on iis7 hfs will not work.

I simply MUST have IIs 7 running, there is no option to turn it off, part of my business requires i have iis7 to host my websites which i've been doing for years.

i run the self test and it comes back good but from a web browser it times out. i check the port and its visible on the net.

i'm simply dumb founded i can not make HFS work while IIS is running and my guess is as follows:

because HFS needs my static IP address, it conflicts with the IP address used by IIS so the only way i can see this working is if I get another static IP address and put HFS on that one.

IIS will bind to the static IP address hence any other app that runs from same ip address will conflict with iis

[bacter]

Hi ninjapimp:

There is no problem to run different servers on the same ip, as lonbg as each uses different port(s).

So keep running your iis7 thing and select a port (above 1024) that is not in use by another service to set up your hfs.

To verify that your selected port is not in use, use a utility like TCPview to see all connections.
Also test from your browser to access that page using this port to veryfy that the 'under construction' page does not appear.

After, set up hfs with this port, and setup firewall(s) and router for this port.

[ninjapimp]

i got it working second time round.
it turns out it was windows firewall that was blocking the port.
thanks again