Windows Server

AMondaleNoSpam · Guest

Does anyone know of a way to work around "IP-bound virtual servers are not
supported in SharePoint Portal Server 2003 or in Windows SharePoint
Services"? The post at
http://support.microsoft.com/default.aspx?scid=kb;en-us;830342 suggests that
host headers are a "workaround" but host headers don't function under HTTPS,
so we cannot use "all unassigned." Any help appreciated.

There is a suggestion that registering Web Parts into the GAC is one method
of circumventing the problem, but I am having issues with the Public Key
being different on the dev box where I build the WP and the production
environment (where the IP-bound site lives). Has anyone utilized this fix?

Wei-Dong XU [MSFT] · Guest

Hi,

For your scenario, I have two suggestions:
1. use different port for your SPS site.
IIS has three methods to identify one site for routing each internet
request:
a. IP (same port; however, not applicable for the scenario now)
b. host header (baned for SSL)
c. port (different port ) ***
You can assign one different port for your WSS site. If your scenario
doesn't permit to append the port number after the url http://serverdnsname
or https://serverdnsname , you can set the default 80 site to redirect the
internet request to your WSS site. Steps below:
a> open Internet management console by typing "inetmgr" (without quotation
mark) at start->run
b> right-click the default web site and select the command entry
"properties"
c> at the properties window, choose the tab "Home Directory"
d> under the section "the content for this resource should come from",
please select "A rediretion to a URL" and type the WSS site url in the
"Redirect to:" inputbox.

And if the default site has been used, you can create one virtual directory
(for example, VD) under default site and point to your WSS site. So the
users can only need to visit the http://serverDNS/VD will be redirect to
the https WSS site.

2. For the public key for the web part, you can use the delay-sign featuer
of .Net framework. You can delay-sign your assembly at the development
level. At the release time, to sign the assemlby with one public key so
that you can keep all the assembly at the development and the production
machine containing the same public key. The article below will introduce
the detailed information for you regarding this topic:
Delay Signing an Assembly
http://msdn.microsoft.com/library/en-us/cpguide/html/cpcondelayedsigningasse
mbly.asp

The section "Delayed Signing" of this article will be helpful as well:
..NET Framework: Building, Packaging, Deploying, and Administering
Applications and Types¡ªPart 2
http://msdn.microsoft.com/msdnmag/issues/01/03/buildapps2/default.aspx

Please feel free to let me know if you have any question.

Best Regards,
Wei-Dong XU (WD.XU)
Microsoft Product Support Services
Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.

	Windows Server Forum Index -> Windows Services	All times are GMT
Page 1 of 1