« Previous Next »

Thread: FPSE behind DMZ

Last post 10-12-2007 9:22 AM by NCNOC. 2 replies.

Average Rating Rate It (5)

RSS

Page 1 of 1 (3 items)

Sort Posts:

  • 10-11-2007, 11:59 AM

    • NCNOC
    • Not Ranked
    • Joined on 10-11-2007, 11:44 AM
    • Posts 3

    FPSE behind DMZ

    We have multiple web servers here and I am taking on the task of redoing most of them. In the past, all of our machines are behind a DMZ which has caused some management issues with FPSE. On the other machines we have had to add a host header IP into each site in order to get to the user management of each sites FPSE's. To me this is more work then is necessary, so I want to fix this with the current server I am rebuilding and then reapply the steps to each server there after.

    I currently have FPSE installed on the new server, but when I go to manage the site (ex: http://manweb.netxxx.com/_vti_bin/_vti_adm/fpadmdll.dll?page=webadmin.htm) it fials to load.

     Is there anything I can do to get it so I can manage the sites, but not have to setup host header IPs on each domain when I want to manage it?

  • 10-12-2007, 8:38 AM In reply to

    Re: FPSE behind DMZ

    "Fails to load" means exactly what in terms of errors, expected behavior, etc.?  Have you checked the firewall?

    Jeff

    Look for Wrox's new book Professional IIS 7 in your local bookstore, or order now at Amazon.com
  • 10-12-2007, 9:22 AM In reply to

    • NCNOC
    • Not Ranked
    • Joined on 10-11-2007, 11:44 AM
    • Posts 3

    Re: FPSE behind DMZ

    The page replies with a 404 error and does not load the control panel for FPSE for that particular domain. I have been told that the DMZ causes the issue, but when I look for the _vti_bin folder (Full path: /_vti_bin/_vti_adm/fpadmdll.dll?page=webadmin.htm) it doesn't exist on the domains directory in IIS, so does it actually attempt to point itself to the config directory of FPSE located in (/Program Files/Common Files/..etc)?

    On our other machines we use an assigned IP address (ex: 192.168.255.2) and put it in the web identities window on the domain we are making user changes to and then when we attempt to goto the config for the domain, we substitute the domain with the ip address that we added and it lets us into the domain's FPSE control panel. This is what I want to shy away from having to do because it is a pain to have to make all those changes all the time.

Page 1 of 1 (3 items)
Microsoft Communities