Default Application Name

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • Microsoft Newsserver

    #1

    Default Application Name

    Hi,

    I dont get involved with IIS much, but recently we had a situation regarding
    the Default Application name which I dont fully understand.

    In essence, we have a main web and underneath it some virtual directories.

    When I tried to rename/Apply the main webs "Default Application" name, to
    something else, it told me this would reset the UNCPassword for the virtual
    directories underneath it. I did it anyway, but it didnt seem to have much
    effect so far. !!!!

    I am not sure what this UNCPassword is for and how hit related to security
    the the virtual directories underneath the main web

    Any assistance to understand this would be appreciated.


    Regards


  • Cowboy \(Gregory A. Beamer\)

    #2
    Re: Default Application Name

    If you are working with a default install of IIS, it is unlikely what you
    have done will have any impact on you. If everything is working, I would not
    sweat it. I have the same "issue" (or non-issue) on my server and everything
    has been working for a long time. We reorged the names recently and things
    are still working.

    Where you are likely to get burned by these types of changes are when you
    are using a third party software that gets configured when it is installed
    to a web. Some have to have the UNCPassword. By default, it "should" matter
    all the time, but IIS knows the changes, so it is not an issue.

    --
    Gregory A. Beamer
    MVP, MCP: +I, SE, SD, DBA

    Subscribe to my blog


    or just read it:


    *************** *************** **************
    | Think outside the box! |
    *************** *************** **************
    "Microsoft Newsserver" <me@nowhere.com wrote in message
    news:O1T7DsxHJH A.2296@TK2MSFTN GP03.phx.gbl...
    Hi,
    >
    I dont get involved with IIS much, but recently we had a situation
    regarding
    the Default Application name which I dont fully understand.
    >
    In essence, we have a main web and underneath it some virtual directories.
    >
    When I tried to rename/Apply the main webs "Default Application" name, to
    something else, it told me this would reset the UNCPassword for the
    virtual
    directories underneath it. I did it anyway, but it didnt seem to have much
    effect so far. !!!!
    >
    I am not sure what this UNCPassword is for and how hit related to security
    the the virtual directories underneath the main web
    >
    Any assistance to understand this would be appreciated.
    >
    >
    Regards
    >
    >

    Comment

    • Cowboy \(Gregory A. Beamer\)

      #3
      Re: Default Application Name


      I just thought of one other potential burn and that is when you are mapping
      to other machines, using UNC. I still think IIS can handle it as long as you
      are not dealing with third party applications that access IIS, but that is
      another thing that could potentially cause problems.

      With a normal, I am creating virtual directories or subwebs, you are not
      likely to have any issues.

      --
      Gregory A. Beamer
      MVP, MCP: +I, SE, SD, DBA

      Subscribe to my blog


      or just read it:


      *************** *************** **************
      | Think outside the box! |
      *************** *************** **************
      "Cowboy (Gregory A. Beamer)" <NoSpamMgbworld @comcast.netNoS pamMwrote in
      message news:OQw71S0HJH A.3884@TK2MSFTN GP02.phx.gbl...
      If you are working with a default install of IIS, it is unlikely what you
      have done will have any impact on you. If everything is working, I would
      not sweat it. I have the same "issue" (or non-issue) on my server and
      everything has been working for a long time. We reorged the names recently
      and things are still working.
      >
      Where you are likely to get burned by these types of changes are when you
      are using a third party software that gets configured when it is installed
      to a web. Some have to have the UNCPassword. By default, it "should"
      matter all the time, but IIS knows the changes, so it is not an issue.
      >
      --
      Gregory A. Beamer
      MVP, MCP: +I, SE, SD, DBA
      >
      Subscribe to my blog

      >
      or just read it:

      >
      *************** *************** **************
      | Think outside the box! |
      *************** *************** **************
      "Microsoft Newsserver" <me@nowhere.com wrote in message
      news:O1T7DsxHJH A.2296@TK2MSFTN GP03.phx.gbl...
      >Hi,
      >>
      >I dont get involved with IIS much, but recently we had a situation
      >regarding
      >the Default Application name which I dont fully understand.
      >>
      >In essence, we have a main web and underneath it some virtual
      >directories.
      >>
      >When I tried to rename/Apply the main webs "Default Application" name, to
      >something else, it told me this would reset the UNCPassword for the
      >virtual
      >directories underneath it. I did it anyway, but it didnt seem to have
      >much
      >effect so far. !!!!
      >>
      >I am not sure what this UNCPassword is for and how hit related to
      >security
      >the the virtual directories underneath the main web
      >>
      >Any assistance to understand this would be appreciated.
      >>
      >>
      >Regards
      >>
      >>
      >

      Comment

      • Microsoft Newsserver

        #4
        Re: Default Application Name

        Thanks Gregory.

        Appreciated.

        However, Im still not sure what this UNCPassword actually is used for. I
        know its some rediculously long string though.

        Regards


        "Cowboy (Gregory A. Beamer)" <NoSpamMgbworld @comcast.netNoS pamMwrote in
        message news:uVL8mW0HJH A.4816@TK2MSFTN GP06.phx.gbl...
        >I just thought of one other potential burn and that is when you are mapping
        >to other machines, using UNC. I still think IIS can handle it as long as
        >you are not dealing with third party applications that access IIS, but that
        >is another thing that could potentially cause problems.
        >
        With a normal, I am creating virtual directories or subwebs, you are not
        likely to have any issues.
        >
        --
        Gregory A. Beamer
        MVP, MCP: +I, SE, SD, DBA
        >
        Subscribe to my blog

        >
        or just read it:

        >
        *************** *************** **************
        | Think outside the box! |
        *************** *************** **************
        "Cowboy (Gregory A. Beamer)" <NoSpamMgbworld @comcast.netNoS pamMwrote in
        message news:OQw71S0HJH A.3884@TK2MSFTN GP02.phx.gbl...
        >If you are working with a default install of IIS, it is unlikely what you
        >have done will have any impact on you. If everything is working, I would
        >not sweat it. I have the same "issue" (or non-issue) on my server and
        >everything has been working for a long time. We reorged the names
        >recently and things are still working.
        >>
        >Where you are likely to get burned by these types of changes are when you
        >are using a third party software that gets configured when it is
        >installed to a web. Some have to have the UNCPassword. By default, it
        >"should" matter all the time, but IIS knows the changes, so it is not an
        >issue.
        >>
        >--
        >Gregory A. Beamer
        >MVP, MCP: +I, SE, SD, DBA
        >>
        >Subscribe to my blog
        >http://feeds.feedburner.com/GregoryBeamer#
        >>
        >or just read it:
        >http://feeds.feedburner.com/GregoryBeamer
        >>
        >************** *************** ***************
        >| Think outside the box! |
        >************** *************** ***************
        >"Microsoft Newsserver" <me@nowhere.com wrote in message
        >news:O1T7DsxHJ HA.2296@TK2MSFT NGP03.phx.gbl.. .
        >>Hi,
        >>>
        >>I dont get involved with IIS much, but recently we had a situation
        >>regarding
        >>the Default Application name which I dont fully understand.
        >>>
        >>In essence, we have a main web and underneath it some virtual
        >>directories .
        >>>
        >>When I tried to rename/Apply the main webs "Default Application" name,
        >>to
        >>something else, it told me this would reset the UNCPassword for the
        >>virtual
        >>directories underneath it. I did it anyway, but it didnt seem to have
        >>much
        >>effect so far. !!!!
        >>>
        >>I am not sure what this UNCPassword is for and how hit related to
        >>security
        >>the the virtual directories underneath the main web
        >>>
        >>Any assistance to understand this would be appreciated.
        >>>
        >>>
        >>Regards
        >>>
        >>>
        >>
        >

        Comment

        • Cowboy \(Gregory A. Beamer\)

          #5
          Re: Default Application Name

          Short answer: It protects the UNC path so someone cannot use IIS to
          circumvent security. When it matters is when you are attaching to another
          computer through IIS. If you are not doing this, you will probably do fine
          to ignore the warnings.

          --
          Gregory A. Beamer
          MVP, MCP: +I, SE, SD, DBA

          Subscribe to my blog


          or just read it:


          *************** *************** **************
          | Think outside the box! |
          *************** *************** **************
          "Microsoft Newsserver" <me@nowhere.com wrote in message
          news:OOhe2D8HJH A.3668@TK2MSFTN GP02.phx.gbl...
          Thanks Gregory.
          >
          Appreciated.
          >
          However, Im still not sure what this UNCPassword actually is used for. I
          know its some rediculously long string though.
          >
          Regards
          >
          >
          "Cowboy (Gregory A. Beamer)" <NoSpamMgbworld @comcast.netNoS pamMwrote in
          message news:uVL8mW0HJH A.4816@TK2MSFTN GP06.phx.gbl...
          >>I just thought of one other potential burn and that is when you are
          >>mapping to other machines, using UNC. I still think IIS can handle it as
          >>long as you are not dealing with third party applications that access IIS,
          >>but that is another thing that could potentially cause problems.
          >>
          >With a normal, I am creating virtual directories or subwebs, you are not
          >likely to have any issues.
          >>
          >--
          >Gregory A. Beamer
          >MVP, MCP: +I, SE, SD, DBA
          >>
          >Subscribe to my blog
          >http://feeds.feedburner.com/GregoryBeamer#
          >>
          >or just read it:
          >http://feeds.feedburner.com/GregoryBeamer
          >>
          >************** *************** ***************
          >| Think outside the box! |
          >************** *************** ***************
          >"Cowboy (Gregory A. Beamer)" <NoSpamMgbworld @comcast.netNoS pamMwrote in
          >message news:OQw71S0HJH A.3884@TK2MSFTN GP02.phx.gbl...
          >>If you are working with a default install of IIS, it is unlikely what
          >>you have done will have any impact on you. If everything is working, I
          >>would not sweat it. I have the same "issue" (or non-issue) on my server
          >>and everything has been working for a long time. We reorged the names
          >>recently and things are still working.
          >>>
          >>Where you are likely to get burned by these types of changes are when
          >>you are using a third party software that gets configured when it is
          >>installed to a web. Some have to have the UNCPassword. By default, it
          >>"should" matter all the time, but IIS knows the changes, so it is not an
          >>issue.
          >>>
          >>--
          >>Gregory A. Beamer
          >>MVP, MCP: +I, SE, SD, DBA
          >>>
          >>Subscribe to my blog
          >>http://feeds.feedburner.com/GregoryBeamer#
          >>>
          >>or just read it:
          >>http://feeds.feedburner.com/GregoryBeamer
          >>>
          >>************* *************** *************** *
          >>| Think outside the box! |
          >>************* *************** *************** *
          >>"Microsoft Newsserver" <me@nowhere.com wrote in message
          >>news:O1T7DsxH JHA.2296@TK2MSF TNGP03.phx.gbl. ..
          >>>Hi,
          >>>>
          >>>I dont get involved with IIS much, but recently we had a situation
          >>>regarding
          >>>the Default Application name which I dont fully understand.
          >>>>
          >>>In essence, we have a main web and underneath it some virtual
          >>>directorie s.
          >>>>
          >>>When I tried to rename/Apply the main webs "Default Application" name,
          >>>to
          >>>something else, it told me this would reset the UNCPassword for the
          >>>virtual
          >>>directorie s underneath it. I did it anyway, but it didnt seem to have
          >>>much
          >>>effect so far. !!!!
          >>>>
          >>>I am not sure what this UNCPassword is for and how hit related to
          >>>security
          >>>the the virtual directories underneath the main web
          >>>>
          >>>Any assistance to understand this would be appreciated.
          >>>>
          >>>>
          >>>Regards
          >>>>
          >>>>
          >>>
          >>
          >
          >

          Comment

          Working...