idiot level IIS question (two sites, different ports) [Answered]RSS

2 replies

Last post Dec 05, 2018 07:21 PM by cokezero

  • idiot level IIS question (two sites, different ports)

    Dec 05, 2018 06:44 PM|cokezero|LINK

    Hello! I am trying to set up two sites on same server with different ports. Let's call the server WEBSERV1.

    1. I have Default Website which is All Unassigned, port 80, no host header. It has a web application called tdd.

    Site has anonymous authentication disabled, windows auth is enabled.

    I can browse to Default Website and hit the IIS default page from http://localhost/ or from http://webserv1/ on a workstation.

    I can browse tdd web application from http://localhost/tdd or from a http://webserv1/tdd on a workstation.

    2. I have a second site called wss which is All Unassigned, port 8080, no host header.

    Site has anonymous authentication disabled, windows auth is enabled. Site also uses PHP.

    I can browse and hit it from http://localhost:8080 

    On a workstation, if I go to http://webserv1:8080 

    I get:

    This site can’t be reached

    The connection was reset.

    Is there anything obvious that I am doing wrong for trying to set this up?

    I realize the better way to do it is using A records connected to IP and then using host headers and binding to IPs, but I am trying to get this to work in Dev with the different ports.

  • Re: idiot level IIS question (two sites, different ports)

    Dec 05, 2018 07:18 PM|lextm|LINK

    cokezero

    Is there anything obvious that I am doing wrong for trying to set this up?

    Like Windows Firewall? TCP port 8080 for inbound traffic.

    Lex Li
    Affordable IIS Consulting Services at https://support.lextudio.com/services/consulting.html
    ---------------------------
    This posting is provided "AS IS" with no warranties, and confers no rights.
  • Re: idiot level IIS question (two sites, different ports)

    Dec 05, 2018 07:21 PM|cokezero|LINK

    LOL yes, that is obvious and also the correct answer. Thanks for catching that. I really appreciate it.