Problem with my IIS at home

[Zakary]

Hi guys!

Hi have a W2k Adv Server at home, with ISS, for a couple of time my IIS is not reachable over the Internet, but only on the LAN. My IIS is setup on the 8080 Tcp port, cause my ISP have block the 80 port. My router is configured correcly, the port 8080 is fowarded to the good LAN IP.

My questions is this;
- How can I know if the 8080 isn't bloc by my ISP, is there a way ?
- What else should I check ?
- Have you an idea why this is happening ?

Many thanks !!
Zak

[-TPM-]

Well you probably have a dynamic IP address which will change from time to time. I've not heard of any ISP's blocking any ports, if they are then there a pretty bad ISP IMO..

Also are you using a router? If so you'll need to setup either a NAT or a DMZ and use the router's external IP.

[dglienna]

Try out NoIP.com as they have software that updates the server when your address changes. It forwards all requests to you then.

[Zakary]

Yes i've a LinkSys WRT54G router and i'm using DynDns.org as dynamic IP "handler",

And yes my ISP Videotron is blocking .. well at least one port the 80, that why my IIS is configured on the 8080, but it no longer work by now ...

Is there a way to know where a port is block ? I meen if the port is block by my ISP or by a bugged router

Zak

[dglienna]

I'm sure your ISP would be happy to tell you. They may even give you the option to let you "UNBLOCK" it.

Go into the setup of your router. Just allow the ports that you want. Routers usually block most ports that are outside of the norm, especially incoming requests.

[nothingofvalue]

To see if your ISP blocks port 80, simply verify that you are absolutely positive you have opened port 80 then do a system scan to see if port 80 is open.

I recommed using :

Shields Up

If the scan says that port 80 is open then you are in business otherwise your ISP is blocking it.


I had a home server for a time just to play with. I used Zone Edit for the dynamic ip part, it's free. I then used Direct Update software to automatically update the IP address each time it changed. Everyting worked very well.

There is a pretty good web site for getting some help. The forum is pretty active by a few knowledgeable people.

DSL Webserver

Good Luck

[Zakary]

To see if your ISP blocks port 80, simply verify that you are absolutely positive you have opened port 80 then do a system scan to see if port 80 is open.

I recommed using :

Shields Up

If the scan says that port 80 is open then you are in business otherwise your ISP is blocking it.


I had a home server for a time just to play with. I used Zone Edit for the dynamic ip part, it's free. I then used Direct Update software to automatically update the IP address each time it changed. Everyting worked very well.

There is a pretty good web site for getting some help. The forum is pretty active by a few knowledgeable people.

DSL Webserver

Good Luck

Thanks for the info i'll look at it !!

[kfcSmitty]

What error are you getting? Do you have persistant port forwarding to the correct PC setup through your router? Have you tried using other ports?

[Zakary]

Yes it a persistent port forwarding problem.. Yes I’ve try different port.
I've also try my FTP, and it has also the same problem ;It work on the LAN but not on the WAN

Yesterday I’ve been doing some test and suddenly light on the router was keeping blinking like if my server was flooding the network and the internet connection have drop.
I've unplug it and the "internet" have came back. After having rebooted the server, all have become as normal on the router but the IIS is still not working. So I suspect the server's network card from being guilty. I think I will execute her next week.

[Ideas Man]

First off, you are aware that if you use a port different to 80 you must supply it in the URL aren't you? e.g. http://www.mydomain.com:8080 Secondly, use the shields up test suggested earlier and check and see if 8080 is listed as open, if it isn't then IIS is not listening on that port and so therefore it isn't working.

How is your router configured to forward the port? Does it forward it from 8080 on your router to 8080 on your IIS server, or from 8080 to 80?

By default, IIS listens on port 80 for the Default Site, if you are tunneling from 8080 to 8080, then you will need to change the listening port on IIS for the website from 80 to 8080 so that it can work properly.

[Zakary]

First off, you are aware that if you use a port different to 80 you must supply it in the URL aren't you? e.g. http://www.mydomain.com:8080 Secondly, use the shields up test suggested earlier and check and see if 8080 is listed as open, if it isn't then IIS is not listening on that port and so therefore it isn't working.

How is your router configured to forward the port? Does it forward it from 8080 on your router to 8080 on your IIS server, or from 8080 to 80?

By default, IIS listens on port 80 for the Default Site, if you are tunneling from 8080 to 8080, then you will need to change the listening port on IIS for the website from 80 to 8080 so that it can work properly.

Yes i supply the port number to the URL. and yes my router forward the port 8080 to 8080 UDP and TCP to my server.

But for long terme solution, I think i'll try to find a cheap web server somewhere to host my web site.
I actually have one but it cust me 6$USD/50 Megs is this a good price ?
I think i need something like 300-400 megs.



Do someone know a good one ?

[Ideas Man]

I dunno about prices, but what did the shields up test say? Is the port open or closed?

[Zakary]

I dunno about prices, but what did the shields up test say? Is the port open or closed?

I've try so much different thing .. don't remember ..
I'll re-take a look after the job.

[Zakary]

Oh God, It work now ... don't ask why

[Zakary]

Stock again ....
it seem to be a intermittent problem...
I have reboot the PC and then .. nothing...

I've take a use "shields up" and the port 8080 seem open...

[dglienna]

Take a look to see what's in the Error Logs. You might get lucky.

[Zakary]

Take a look to see what's in the Error Logs. You might get lucky.

Good idea!!

[Zakary]

Take a look to see what's in the Error Logs. You might get lucky.

Nil, Nothing, nada, rien. The event viewer tell nothing about it.

But I some more info, It work at the office, but not at home

Could some of you test it ?
www.hugo.dufort.com
and tell me if it work ?

[visualAd]

It works for me at the moment. Did you say it is port 8080? - does your router forward port 80 to 8080. Is it a Netgear router by any chance?

[Zakary]

It works for me at the moment. Did you say it is port 8080? - does your router forward port 80 to 8080. Is it a Netgear router by any chance?

Yep I use 8080, and No my router did'nt forward the 80 to the 8080 should I ?
And my router is a LinkSys WRT54G v2.

[nothingofvalue]

If it is working intermittantly then it sounds like a DNS issue. Are you using software (like I mentioned above) to automatically change your address when your ISP changes?

[Zakary]

If it is working intermittantly then it sounds like a DNS issue. Are you using software (like I mentioned above) to automatically change your address when your ISP changes?

You meen something like DynDns.org ? Yes I do
hdufort.dyndns.org


I use NetIdendity.com (hugo.dufort.com) as a web host, on this web host the main page default.htm have a frame in it and this frame refer to my server at home hdufort.dyndns.org:8080

But I will check for my DNS

[Zakary]

I've found 1 for the 3 DNS was wrong but still do not solve the problem, I begging to thing that a device is to blame probably my router...


Thanks to everyone for your help!

[visualAd]

This is what I would recommend. I had this problem with a router of mine. In the end it turned out to be a bug in its firmware. It worked for a short time then all of a sudden it would die, then it would come back again, the nature of the problem was sporadic and it took me a long time to convince the guys at Netgear that the router was the problem.

I found out what caused the problem by installing some packet logging software on the PC which hosted the server and carefully scrutinising the logs available for the router. I then made a dial up connection to access the PC from outside my LAN (this is important) and sure enough, it would work at firs, the packets were received and logged by the router and then sent to the correct server, then, it would suddenly stop working - it would either start forwarding the packets somewhere else or they would just disappear.

I have found the thread where I posted details about the problem here. It might well be a bug with your router. If you have multiple PC's on your LAN - it may be worth installing a web server on them and seeing if the router starts randomly forwarding to any of them.

In the end I just purchased a new router -- problem solved. Its a US robotics ADSL Modem gateway. It has an embedded Linux operating system installed on it which allows you to use telnet to configure the firewall properly and run detailed diagnostics and on problems as well as a web interface.

[Zakary]

And is your US robotics ADSL Modem, work great?

This is what I would recommend. I had this problem with a router of mine. In the end it turned out to be a bug in its firmware. It worked for a short time then all of a sudden it would die, then it would come back again, the nature of the problem was sporadic and it took me a long time to convince the guys at Netgear that the router was the problem.

I found out what caused the problem by installing some packet logging software on the PC which hosted the server and carefully scrutinising the logs available for the router. I then made a dial up connection to access the PC from outside my LAN (this is important) and sure enough, it would work at firs, the packets were received and logged by the router and then sent to the correct server, then, it would suddenly stop working - it would either start forwarding the packets somewhere else or they would just disappear.

I have found the thread where I posted details about the problem here. It might well be a bug with your router. If you have multiple PC's on your LAN - it may be worth installing a web server on them and seeing if the router starts randomly forwarding to any of them.

In the end I just purchased a new router -- problem solved. Its a US robotics ADSL Modem gateway. It has an embedded Linux operating system installed on it which allows you to use telnet to configure the firewall properly and run detailed diagnostics and on problems as well as a web interface.

[visualAd]

Yes, it works fine. i have never had any problems with it. I urge you however, before going down that route to make absolutly sure it is your router and not your ISP

[Zakary]

Yes, it works fine. i have never had any problems with it. I urge you however, before going down that route to make absolutly sure it is your router and not your ISP

Yes .. your're right, If I could put my hand on a another router somewhere to test it could be great ...
Thanks again!!