|
General Discussion General discussion about SageTV and related companies, products, and technologies. |
|
Thread Tools | Search this Thread | Display Modes |
#1
|
||||
|
||||
Setting up IIS in conjunction w/ Sage Webserver
I've got the Sage webserver setup and running on ssl and accessable from the internet using either my dynamic IP from Cox (same IP for 3 years now) or my domain name from dyndns.org.
Now, I'm trying to setup IIS on same machine to serve a public website and FTP site that has a password protected private page w/ a link to the Sage webserver pages. I have IIS setup and running and I can access it from inside my LAN but not from the internet. I have a Linksys BEFSX41 router and have forwarded port 80 to the static IP of the webserver system but no web requests ever make it to IIS. IIS logs show no connection info from internet addresses, just internal lan IP's. Port 8443 is forwarded to the same machine for the Sage webserver and that works properly. I have looked at the router config till my eyes hurt but cannot figure out why it is not forwarding port 80. I have disabled remote admin on the router so port 80 should be able to be forwarded unless there is another setting for this that I am missing. Maybe it is forwarding port 80 requests but IIS is not recieving them, ignoring them, or just not responding to requests from outside my LAN. I am a network admin and run several IIS webservers at work so I thought this would be easy but I have been banging my head for two weeks trying to figure this out. Of course it slows things down a lot when I have to drive 40 min. to work to test a changed setting. Any ideas from the network gods? |
#2
|
||||
|
||||
You don't need really need to install IIS all you need to do is punch hole port forwarded 8080 to the Sage webserver
|
#3
|
|||
|
|||
Cox blocks port 80 on their switches. They don't block 443 (the SSL port) so that would explain why that works. Change the port in IIS to 81 and see what happens.
EDIT: As a network admin I'm sure you already know this, but for the benefit of others - to access the site if it's listening on port 81 (for instance), you would use the URL: http://<dns name / ip-address>:81 and you'll need to enable a port-forward in your firewall for this port as well. Andy. Last edited by AndyS; 01-22-2005 at 03:56 PM. |
#4
|
||||
|
||||
SHS, I already have the Sage webserver running properly on port 8443 using SSL. What I want to do is set up a little family website open to the public (or whomever I tell the url to since I am not registering the site). Just a little "Welcome to the Leonard Family Website" page with pages for myself, the woman, and the kid. The Sage webserver will be linked to from the family website. I need IIS (or Apache, etc.) since the Sage webserver has no FTP server and is not set up to run anything else but the Sage website (I have looked closely and I think its possible to modify the default install but I want to just leave the Sage webserver as is).
Andy, I suspected this but never got around to trying it. I'll change the port I'm using to something else but I really wanted 80 to make it easy. First time I've found fault w/ Cox internet. BTW, do they also block port 21 (FTP)? probably so since I have the same issue w/ IIS's FTP server. |
#5
|
|||
|
|||
Quote:
What OS/Service-Pack are you running IIS on? Andy. |
#6
|
||||
|
||||
XP SP2, IIS 5.1
Work webservers are on 2000 server. Never played around with XP version but it's practically the same. Got home and configured the ports but I can't test until tomorrow when I go to the office and I just realized IIS is not accessible from any system on my LAN. Trying to remember what I was messing around with last weekend when I was trying to figure out what was wrong. Last thing I remember was that it was 4 am Sunday morning and I was tired of troubleshooting it. Here it is late the next Sat. night and I'm troubleshooting IIS again |
#7
|
|||
|
|||
IIS is built into XP. The administration is done from admintools. If it's not showing up there then you need to install it from add/remove programs and go to the windows programs. add/remove windows components is where you want to look. One thing you might want to turn off though is the ftp service if you have no need of it.
|
#8
|
|||
|
|||
Make sure you've configured the XP SP2 firewall. Because you're safe behind a hardware firewall I'd disable the XP firewall for testing. You can re-enable it and get your setting just right once everything else is working.
You certainly need to get IIS working on port 81 from the local LAN before attempting to get it working over the internet. Andy. |
#9
|
||||
|
||||
The culprit was the XP firewall. IIS opened a hole for itself during installation but it was specific to port 80. I had thought that it would behave like the hole I opened for Sage.exe, i.e. - if I were to change the Sage webserver port and restart Sage the XP firewall would automatically adjust but the IIS hole was only for port 80 not the IIS application. Whenever I would change to an alternate port in IIS it would get blocked. I must have looked at that firewall setting a dozen times scratchin' my head and not seeing the obvious.
FTP is still not working though and it is still on port 21. 21 is not on Cox's list of blocked ports but it is the only thing left. |
#10
|
|||
|
|||
FTP is a pesky critter to get working through a firewall. You need to not only enable port 21 but port 20 as well. The firewall has to totally ignore port 20 and allow everything cause the actual data transfer coming back at you will actually originate from the server on port 20 and the firewall can/will freek out if it's setup to look at that.
|
#11
|
||||
|
||||
Yeah, your not kidding. I did create a hole on port 20 but I still have to uncheck "Use Passive FTP" in IE options. My brother uses a Mac and Mac IE options don't have that setting but I got Safari to work OK from a Mac at work so I think my brother will be OK. Anybody know of a good (and free) FTP client for Mac?
On a slightly different tack, I think I am going to use the IIS web and ftp sites solely for public access and try to setup a VPN from my router to his and another to my dad's (future) router. I have a Linksys BEFSX41 VPN router and I'm going to get them both the same router. Does anyone know if the Linksys will allow internet traffic to be routed to the internet and VPN traffic to be routed thru the VPN at the same time? I can do this on a Cisco router but I know some of the home office routers will route ALL traffic thru the VPN if it is active. |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|