- IIS works on all ports on local LAN, only some ports remotely
- Posted by newsgroups.comcast.net on May 3rd, 2007
Can anyone help me? I can't access any IIS websites on my Windows 2003/SP2
server from outside our LAN, except if it runs on port 80. What could cause
this problem, which appears to be a server problem (rather than a firewall
problem)?
I want to run a HTTPS server at a nonstandard port, say
https://myserver.mylan.com:9999/. I can access it from compute inside the
local lan (where the address gets mapped to 10.2.xx.xx), but from a remote
computer (which maps it to some number like (207.xx.xx.xx) outside the LAN,
I can not access it. Meanwhile, HTTP on the standard port 80 works fine.
In fact, if I change my standard http web site to listen to port 9999, I
have the same problem: http://myserver.mylan.com:9999/ works only from
inside, not outside.
The IT folks opened up the firewall for this port 9999. Also, this used to
work, I installed some updates since then (I think I installed SP2), and now
I can't get to this port anymore.
Does anyone have any suggestions as where to start looking?
- Posted by CreateWindow on May 3rd, 2007
Hi,
I would ask if the firewall people actually did open port 9999 for
forwarding to your IIS box.
CreateWindow
http://justpageprobe.com
The FREE Web page utility you always wanted.
Keep your router connected.
Email your IP to where you need it.
Monitor your enterprise Web Servers.
"newsgroups.comcast.net" <zanzabar@gotome.com> wrote in message
news:_r-dnWy2Lecv7aTbnZ2dnUVZ_o-knZ2d@comcast.com...
- Posted by David Wang on May 3rd, 2007
Why do you suspect it's a server problem?
You said that everything works from local LAN, and since IIS does not
distinguish between local LAN and remote, the problem has nothing to
do with IIS nor the server.
I would start by looking at:
1. Any firewall on the server that rejects non-local IP
2. Any firewall on the LAN which does not forward external IP:Port to
internal IP:Port
3. If port is forwarded, is it still for the correct internal IP (i.e.
internal IP can change with DHCP -- you have not shown that your prior
port forwarding is still valid)
I would refrain from blaming unexplainable behavior on "some updates".
There are plenty of moving parts in networking -- if you think
networking is reliable, then you are in for a big surprise.
//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//
On May 2, 10:18 pm, "newsgroups.comcast.net" <zanza...@gotome.com>
wrote:
- Posted by ZZ on May 3rd, 2007
Yeah, they confirmed that nothing changed. The port was working until I
installed a few updates (a few updates, a few apps, added memory, and added
a new HD).
How about this... If I wanted to block access to certain ports from
computers that are not on my local lan, how would i go about doing this?
"CreateWindow" <createwindow@gmail.com> wrote in message
news:JoOdnQq9Sr3EGaTbnZ2dnUVZ_u2dnZ2d@giganews.com ...
- Posted by David Wang on May 3rd, 2007
1. Configure the LAN firewall to not allow access.
2. Configure the LAN firewall to not forward ports
3. Configure the LAN firewall to not forward ports to your server's
internal IP
4. Configure the Windows Firewall to only allow local subnet access.
5. Configure another application to listen to that port
//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//
On May 3, 3:03 am, "ZZ" <zanza...@gotome.com> wrote:
