|
security
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Front Page Server Extensions: Change Port?I started a new ASP.NET Web Service project in VS .NET 2003 on a remote web server and the only way I could get it to work was by installing the Front Page Server Extensions on the server. I feel very uncomfortable, however, because of the insecure nature of the extensions, in the past. After installing, I realized that the extensions used TCP port 80 for transmission. Unfortunately, this makes it impossible for me to close the port at my firewall since this server is used to host our company web site. Is it possible to change the port that the Front Page Server Extensions listen on? Alternatively (and perhaps a better solution), is it possible to enable FPSE on selected virtual web sites and disable them for others? Any other suggestions are welcome. Thank you in advance, -- Sean What version of FPSE are you using? In IIS Manager (for FPSE2000) you can
choose which websites you want to Configure Server Extensions for, and only those websites will allow authoring. In FPSE2002 you use the Sharepoint Administration Site shortcut in your Admin Tools folder, and you choose which website to extend. WRT to the port issue: You can always create a second website, that listens on a different port, which just has the same webroot as the main website. However, whether you can have VS.NET connect to that alternate port is another question (I don't think VS.NET supports that) Alternatively, develop on your local machine, and use some other mechanism for transferring the files across to your production site. Cheers Ken Show quoteHide quote "Fao, Sean" <enceladus***@yahoo.comI-WANT-NO-SPAM> wrote in message news:uwl0QowLFHA.580@TK2MSFTNGP15.phx.gbl... : Hello, : : I started a new ASP.NET Web Service project in VS .NET 2003 on a remote : web server and the only way I could get it to work was by installing the : Front Page Server Extensions on the server. I feel very uncomfortable, : however, because of the insecure nature of the extensions, in the past. : After installing, I realized that the extensions used TCP port 80 for : transmission. Unfortunately, this makes it impossible for me to close : the port at my firewall since this server is used to host our company : web site. : : Is it possible to change the port that the Front Page Server Extensions : listen on? Alternatively (and perhaps a better solution), is it : possible to enable FPSE on selected virtual web sites and disable them : for others? : : Any other suggestions are welcome. : : Thank you in advance, : : -- : Sean
Change in ASP.Net authentication between Win2000 and Win2003
Firewall and Win 2K OWA Exploit RE: How to create a client side certificate on a Windows 2000 Serv Integrated Windows Authentication Error, Re: IIS metabase permissions when creating new VirDir's IIS Security Risks & Vulnerabilities Login security issue. Local Groups Client Certificate accessability |
|||||||||||||||||||||||