Single DNS Name
- From: "tom.pacyk@xxxxxxxxx" <tom.pacyk@xxxxxxxxx>
- Date: Sun, 27 Jan 2008 00:30:29 -0800 (PST)
I'm having some trouble doing (at least what I consider) to be a
simple WSS 3.0 setup. I've found tons of information on AAM which
seems be what I need to do, but nothing specifically for what I'm
looking for.
The ultimate goal is a single DNS name used for SharePoint access both
internally and externally, say sharepoint.company.com. How do I
accomplish this? Is it really as confusing as it seems?
If I use AAM and leave the default name of "http://server"; and add an
Internet and Intranet public name of "sharepoint.company.com", only
the http://server address works. If I browse to sharepoint.company I
am prompted for credentials, but proper credentials don't work at all.
I've tried adding the address to both the trusted and intranet zone in
IE, but I never get logged in. I tried adding sharepoint.company.com
as a host header to the IIS web site, but no luck.
I've seen some info on extending the application.... is that the route
I need to go? It seems overkill to create an additional site just to
support a different name. If I do that can I delete the original site
the installation created?
I'm planning on doing this as an HTTPS implementation ultimately, so
any help on that would be appreciated too. Do I need to extend the
application again? I figured I'd start easy and just sort out this
name stuff first...
So if someone could point me to some resources I'd be grateful. I've
read Troy's blog and bunch of other suggestions, but they all seem
geared towards using different internal and external addresses or
involving ISA, which won't be used in my case. Any tips?!
.
- Follow-Ups:
- Re: Single DNS Name
- From: BizWorld
- Re: Single DNS Name
- Prev by Date: Re: Front End WSS3.0 Server
- Next by Date: RE: EditForm.aspx only shows Name field
- Previous by thread: WSS FAQ additions and corrections - 20th - 26th January 2008
- Next by thread: Re: Single DNS Name
- Index(es):
Relevant Pages
|
