CheckingPorts

Is there a utility that can be ran on a server to see if port 80 is
opened. Do I have to use routing and remote access to get the websites
on IIS accessable from outside my firewall? We have tested the DSL
modem and linksys router and they seem to be working properly. We can
not get access to our websites outside the firewall, port 80 seems to be
blocked at the server. We can get to our ftp server just fine and we
can remote desktop into our webserver using www.domainname.net just fine.

TIA

Re: CheckingPorts

At a command window, type:

netstat -an

to find out what ports are currently being listened on. You can use the
Sysinternals (now Microsoft) TCPView tool if you want to see what process is
listening on each port.

Are you sure your ISP isn't blocking port 80?

Cheers
Ken

"gh" wrote in message
news:eTb%23DYR6HHA.1208@TK2MSFTNGP03.phx.gbl...
> Is there a utility that can be ran on a server to see if port 80 is
> opened. Do I have to use routing and remote access to get the websites on
> IIS accessable from outside my firewall? We have tested the DSL modem and
> linksys router and they seem to be working properly. We can not get
> access to our websites outside the firewall, port 80 seems to be blocked
> at the server. We can get to our ftp server just fine and we can remote
> desktop into our webserver using www.domainname.net just fine.
>
> TIA

Re: CheckingPorts

From the net, you can try this site to check.
http://www.canyouseeme.org/


--
Regards,
Bernard Cheah
http://www.iis.net/
http://msmvps.com/blogs/bernard/


"gh" wrote in message
news:eTb%23DYR6HHA.1208@TK2MSFTNGP03.phx.gbl...
> Is there a utility that can be ran on a server to see if port 80 is
> opened. Do I have to use routing and remote access to get the websites on
> IIS accessable from outside my firewall? We have tested the DSL modem and
> linksys router and they seem to be working properly. We can not get
> access to our websites outside the firewall, port 80 seems to be blocked
> at the server. We can get to our ftp server just fine and we can remote
> desktop into our webserver using www.domainname.net just fine.
>
> TIA

Re: CheckingPorts

Bernard:

Thanks for the link. I get a Connection timed out error message for
port 80. Port 21 is working fine.

Thanks


Bernard Cheah [MVP] wrote:
> From the net, you can try this site to check.
> http://www.canyouseeme.org/
>
>

Re: CheckingPorts

Try telnetting in from the outside:

Command prompt:

telnet hostname 80

(Replace "hostname" with your site name)

You should get a blank cursor, press enter several times until it kicks you
out. If it's IIS, it will tell you basically "iis kicked you out"

If something else happens:

- timeout of about 45 seconds, the port is not open
- reject with no wait = probably a firewall issue
- some other device has a web server on it listening for a web interface
(try using just the IP address in a browser and see if anything comes up),
some routers (including home versions) are known to be able to listen on
port 80 and interrupt web traffic in.

Also, windows has a firewall built into it in some versions, have you
checked for that?

"gh" wrote in message
news:uC0xFDX6HHA.2380@TK2MSFTNGP02.phx.gbl...
> Bernard:
>
> Thanks for the link. I get a Connection timed out error message for port
> 80. Port 21 is working fine.
>
> Thanks
>
>
> Bernard Cheah [MVP] wrote:
>> From the net, you can try this site to check.
>> http://www.canyouseeme.org/
>>

Re: CheckingPorts

Well, in this case it is either block or your forwarding is not configured
correctly.

--
Regards,
Bernard Cheah
http://www.iis.net/
http://msmvps.com/blogs/bernard/


"gh" wrote in message
news:uC0xFDX6HHA.2380@TK2MSFTNGP02.phx.gbl...
> Bernard:
>
> Thanks for the link. I get a Connection timed out error message for port
> 80. Port 21 is working fine.
>
> Thanks
>
>
> Bernard Cheah [MVP] wrote:
>> From the net, you can try this site to check.
>> http://www.canyouseeme.org/
>>

Re: CheckingPorts

Bernard Cheah [MVP] wrote:
> Well, in this case it is either block or your forwarding is not configured
> correctly.
>

It turned that the DSL Modem was blocking several ports. The firmware
has a bug in it. I had to get a different model of the modem. Thanks
for all the help.