IIS sites can be configured to run on different ports, different host headers or different IP addresses. We have a setup where we have 4 sites on one box. Two of these sites run on port 80 with no host headers, but with different IP Addresses (1.4.202.13 and 1.4.202.14). SPS runs on the one site and Workspace runs on the other. After a clean install, workspace only returns a white page with a tiny red 404 error message in the center. I guessed that workspace attempted to connect to the wrong site, not being aware of the scenario. I changed the C:Program FilesK2.net 2003K2WSWorkspaceweb.config file as indicated below to use the IP Address and workspace worked correctly. The server name is TEST006, but attempting to connect to http://TEST006/K2V3 (default value after installation) will fail, as that is an ambiguous request. A call to http://1.4.202.14/K2V3 works.

Review WebServer appsetting after change

<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<system.web>
<compilation defaultLanguage="vb" debug="false" />
<customErrors defaultRedirect="Error_Page.htm" mode="On" />
<authentication mode="Windows" />
<trace enabled="false" requestLimit="10" pageOutput="false" traceMode="SortByTime" localOnly="true"
/>
<sessionState mode="InProc" stateConnectionString="tcpip=127.0.0.1:42424" sqlConnectionString="data source=127.0.0.1;user id=sa;password="
cookieless="false"
timeout="99999" />
<globalization requestEncoding="utf-8" responseEncoding="utf-8" />
<identity impersonate="true" />
</system.web>
<appSettings>
<add key="ServerName" value="TEST006" />
<add key="WebServer" value="http://1.4.202.14/K2V3" />
<add key="ViewXML" value="False" />
</appSettings>
</configuration>