Change Sharepoint URL to FQDN with Subsites

I have a Windows Sharepoint Services server running. When I first set it
up, I apparently configured it so that it was only accessible using the url:
http://sps1

We have since created a subsite (http://sps1/subsite)

I would like to be able to access both of these sites using the fully
qualified domain name of the server, e.g.:
http://sps1.domain.com and http://sps1.domain.com/subsite

I tried just adding a host header to the virtual server in Internet Services
manager, but this does not work. (I have since reverted that change, so I
have now made no changes).

Is there a specific sharepoint supported procedure for making it possible to
access the sharepoint site and subsite via the FQDN instead of the hostname?
Thanks.

Craig Matthews
System Administrator
Genesis Group

Mike
Thu Jul 28 23:20:21 CDT 2005

This FAQ message is for changing site names

http://www.asaris-matrix.com/mvp-walsh/Lists/WSS%20FAQ/DispForm.aspx?ID=68

Changing from sps1 to sps1.domain.com is perhaps best done with DNS.

Note that (as chasernl wrote in another thread here) Alerts will continue to
direct people to the URL that was current (and used) at the time the Alert
was created.

Mike Walsh, Helsinki, Finland
WSS FAQ http://wss.collutions.com
please reply to the newsgroup only

"Craig Matthews" <craigm@genesisgroup.com> wrote in message
news:H6ednR2nMJx5aHXfRVn-oQ@giganews.com...
>I have a Windows Sharepoint Services server running. When I first set it
>up, I apparently configured it so that it was only accessible using the
>url: http://sps1
>
> We have since created a subsite (http://sps1/subsite)
>
> I would like to be able to access both of these sites using the fully
> qualified domain name of the server, e.g.:
> http://sps1.domain.com and http://sps1.domain.com/subsite
>
> I tried just adding a host header to the virtual server in Internet
> Services manager, but this does not work. (I have since reverted that
> change, so I have now made no changes).
>
> Is there a specific sharepoint supported procedure for making it possible
> to access the sharepoint site and subsite via the FQDN instead of the
> hostname? Thanks.
>
> Craig Matthews
> System Administrator
> Genesis Group
>
>

Craig
Fri Jul 29 11:46:27 CDT 2005

I was unclear:

Both "sps1" and "sps1.domain.com" both resolve to the correct IP address, so
DNS works. They are the same machine. When I attempt to access Sharepoint
via http://sps1.domain.com, however, I get an HTTP 400 Bad Request.
Accessing via http://sps1 works fine, however.

Craig Matthews

"Mike Walsh" <englantilainen@hotmail.com> wrote in message
news:O%23QEYT$kFHA.3936@TK2MSFTNGP10.phx.gbl...
> This FAQ message is for changing site names
>
> http://www.asaris-matrix.com/mvp-walsh/Lists/WSS%20FAQ/DispForm.aspx?ID=68
>
> Changing from sps1 to sps1.domain.com is perhaps best done with DNS.
>
> Note that (as chasernl wrote in another thread here) Alerts will continue
> to direct people to the URL that was current (and used) at the time the
> Alert was created.
>
> Mike Walsh, Helsinki, Finland
> WSS FAQ http://wss.collutions.com
> please reply to the newsgroup only
>
> "Craig Matthews" <craigm@genesisgroup.com> wrote in message
> news:H6ednR2nMJx5aHXfRVn-oQ@giganews.com...
>>I have a Windows Sharepoint Services server running. When I first set it
>>up, I apparently configured it so that it was only accessible using the
>>url: http://sps1
>>
>> We have since created a subsite (http://sps1/subsite)
>>
>> I would like to be able to access both of these sites using the fully
>> qualified domain name of the server, e.g.:
>> http://sps1.domain.com and http://sps1.domain.com/subsite
>>
>> I tried just adding a host header to the virtual server in Internet
>> Services manager, but this does not work. (I have since reverted that
>> change, so I have now made no changes).
>>
>> Is there a specific sharepoint supported procedure for making it possible
>> to access the sharepoint site and subsite via the FQDN instead of the
>> hostname? Thanks.
>>
>> Craig Matthews
>> System Administrator
>> Genesis Group
>>
>>
>
>

Craig
Fri Jul 29 12:18:27 CDT 2005

FYI: Just to avoid confusion. SPS1 is only the NAME of the SERVER. I am
running WSS, not Sharepoint Portal Server.

Craig

"Mike Walsh" <englantilainen@hotmail.com> wrote in message
news:O%23QEYT$kFHA.3936@TK2MSFTNGP10.phx.gbl...
> This FAQ message is for changing site names
>
> http://www.asaris-matrix.com/mvp-walsh/Lists/WSS%20FAQ/DispForm.aspx?ID=68
>
> Changing from sps1 to sps1.domain.com is perhaps best done with DNS.
>
> Note that (as chasernl wrote in another thread here) Alerts will continue
> to direct people to the URL that was current (and used) at the time the
> Alert was created.
>
> Mike Walsh, Helsinki, Finland
> WSS FAQ http://wss.collutions.com
> please reply to the newsgroup only
>
> "Craig Matthews" <craigm@genesisgroup.com> wrote in message
> news:H6ednR2nMJx5aHXfRVn-oQ@giganews.com...
>>I have a Windows Sharepoint Services server running. When I first set it
>>up, I apparently configured it so that it was only accessible using the
>>url: http://sps1
>>
>> We have since created a subsite (http://sps1/subsite)
>>
>> I would like to be able to access both of these sites using the fully
>> qualified domain name of the server, e.g.:
>> http://sps1.domain.com and http://sps1.domain.com/subsite
>>
>> I tried just adding a host header to the virtual server in Internet
>> Services manager, but this does not work. (I have since reverted that
>> change, so I have now made no changes).
>>
>> Is there a specific sharepoint supported procedure for making it possible
>> to access the sharepoint site and subsite via the FQDN instead of the
>> hostname? Thanks.
>>
>> Craig Matthews
>> System Administrator
>> Genesis Group
>>
>>
>
>

Mike
Sat Jul 30 03:20:47 CDT 2005

I never dreamed you were :) Your first message was very clear in that ...

Mike

"Craig Matthews" <craigm@genesisgroup.com> wrote in message
news:1IqdnXhZopN--XffRVn-vQ@giganews.com...
> FYI: Just to avoid confusion. SPS1 is only the NAME of the SERVER. I am
> running WSS, not Sharepoint Portal Server.
>
> Craig
>
> "Mike Walsh" <englantilainen@hotmail.com> wrote in message
> news:O%23QEYT$kFHA.3936@TK2MSFTNGP10.phx.gbl...
>> This FAQ message is for changing site names
>>
>> http://www.asaris-matrix.com/mvp-walsh/Lists/WSS%20FAQ/DispForm.aspx?ID=68
>>
>> Changing from sps1 to sps1.domain.com is perhaps best done with DNS.
>>
>> Note that (as chasernl wrote in another thread here) Alerts will continue
>> to direct people to the URL that was current (and used) at the time the
>> Alert was created.
>>
>> Mike Walsh, Helsinki, Finland
>> WSS FAQ http://wss.collutions.com
>> please reply to the newsgroup only
>>
>> "Craig Matthews" <craigm@genesisgroup.com> wrote in message
>> news:H6ednR2nMJx5aHXfRVn-oQ@giganews.com...
>>>I have a Windows Sharepoint Services server running. When I first set it
>>>up, I apparently configured it so that it was only accessible using the
>>>url: http://sps1
>>>
>>> We have since created a subsite (http://sps1/subsite)
>>>
>>> I would like to be able to access both of these sites using the fully
>>> qualified domain name of the server, e.g.:
>>> http://sps1.domain.com and http://sps1.domain.com/subsite
>>>
>>> I tried just adding a host header to the virtual server in Internet
>>> Services manager, but this does not work. (I have since reverted that
>>> change, so I have now made no changes).
>>>
>>> Is there a specific sharepoint supported procedure for making it
>>> possible to access the sharepoint site and subsite via the FQDN instead
>>> of the hostname? Thanks.
>>>
>>> Craig Matthews
>>> System Administrator
>>> Genesis Group
>>>
>>>
>>
>>
>
>

Mike
Sat Jul 30 03:24:10 CDT 2005

I'd better pass. This isn't really my area.

My conclusion would be that accessing via the server name is OK but that
there is something wrong with the re-direct as far as a URL is concerned..

What happens if you access via http://192.168.0.1 (change the numbers) ?

Mike Walsh, Helsinki, Finland

"Craig Matthews" <craigm@genesisgroup.com> wrote in message
news:4PadnZ2dnZ16tzzwnZ2dnf7Ad9-dnZ2dRVn-y52dnZ0@giganews.com...
>I was unclear:
>
> Both "sps1" and "sps1.domain.com" both resolve to the correct IP address,
> so DNS works. They are the same machine. When I attempt to access
> Sharepoint via http://sps1.domain.com, however, I get an HTTP 400 Bad
> Request. Accessing via http://sps1 works fine, however.
>
> Craig Matthews
>
> "Mike Walsh" <englantilainen@hotmail.com> wrote in message
> news:O%23QEYT$kFHA.3936@TK2MSFTNGP10.phx.gbl...
>> This FAQ message is for changing site names
>>
>> http://www.asaris-matrix.com/mvp-walsh/Lists/WSS%20FAQ/DispForm.aspx?ID=68
>>
>> Changing from sps1 to sps1.domain.com is perhaps best done with DNS.
>>
>> Note that (as chasernl wrote in another thread here) Alerts will continue
>> to direct people to the URL that was current (and used) at the time the
>> Alert was created.
>>
>> Mike Walsh, Helsinki, Finland
>> WSS FAQ http://wss.collutions.com
>> please reply to the newsgroup only
>>
>> "Craig Matthews" <craigm@genesisgroup.com> wrote in message
>> news:H6ednR2nMJx5aHXfRVn-oQ@giganews.com...
>>>I have a Windows Sharepoint Services server running. When I first set it
>>>up, I apparently configured it so that it was only accessible using the
>>>url: http://sps1
>>>
>>> We have since created a subsite (http://sps1/subsite)
>>>
>>> I would like to be able to access both of these sites using the fully
>>> qualified domain name of the server, e.g.:
>>> http://sps1.domain.com and http://sps1.domain.com/subsite
>>>
>>> I tried just adding a host header to the virtual server in Internet
>>> Services manager, but this does not work. (I have since reverted that
>>> change, so I have now made no changes).
>>>
>>> Is there a specific sharepoint supported procedure for making it
>>> possible to access the sharepoint site and subsite via the FQDN instead
>>> of the hostname? Thanks.
>>>
>>> Craig Matthews
>>> System Administrator
>>> Genesis Group
>>>
>>>
>>
>>
>
>

Todd
Mon Aug 01 15:08:12 CDT 2005

Craig,
Are you using host headers of any kind? If so, make sure sps1.domain.com is
set in your WSS site. This sounds very much like a host header problem.

tk
"Craig Matthews" <craigm@genesisgroup.com> wrote in message
news:4PadnZ2dnZ16tzzwnZ2dnf7Ad9-dnZ2dRVn-y52dnZ0@giganews.com...
>I was unclear:
>
> Both "sps1" and "sps1.domain.com" both resolve to the correct IP address,
> so DNS works. They are the same machine. When I attempt to access
> Sharepoint via http://sps1.domain.com, however, I get an HTTP 400 Bad
> Request. Accessing via http://sps1 works fine, however.
>
> Craig Matthews
>
> "Mike Walsh" <englantilainen@hotmail.com> wrote in message
> news:O%23QEYT$kFHA.3936@TK2MSFTNGP10.phx.gbl...
>> This FAQ message is for changing site names
>>
>> http://www.asaris-matrix.com/mvp-walsh/Lists/WSS%20FAQ/DispForm.aspx?ID=68
>>
>> Changing from sps1 to sps1.domain.com is perhaps best done with DNS.
>>
>> Note that (as chasernl wrote in another thread here) Alerts will continue
>> to direct people to the URL that was current (and used) at the time the
>> Alert was created.
>>
>> Mike Walsh, Helsinki, Finland
>> WSS FAQ http://wss.collutions.com
>> please reply to the newsgroup only
>>
>> "Craig Matthews" <craigm@genesisgroup.com> wrote in message
>> news:H6ednR2nMJx5aHXfRVn-oQ@giganews.com...
>>>I have a Windows Sharepoint Services server running. When I first set it
>>>up, I apparently configured it so that it was only accessible using the
>>>url: http://sps1
>>>
>>> We have since created a subsite (http://sps1/subsite)
>>>
>>> I would like to be able to access both of these sites using the fully
>>> qualified domain name of the server, e.g.:
>>> http://sps1.domain.com and http://sps1.domain.com/subsite
>>>
>>> I tried just adding a host header to the virtual server in Internet
>>> Services manager, but this does not work. (I have since reverted that
>>> change, so I have now made no changes).
>>>
>>> Is there a specific sharepoint supported procedure for making it
>>> possible to access the sharepoint site and subsite via the FQDN instead
>>> of the hostname? Thanks.
>>>
>>> Craig Matthews
>>> System Administrator
>>> Genesis Group
>>>
>>>
>>
>>
>
>