DNS only handles the IP address - you need either a host header (which
allows you to run more than 1 IIS site on port 80) or something that
will do a port direct. A http:// URL without a port number will always
try to contact port 80, an https:// URL port 443.



Bryan Hart | Technical Consultant | Solanite Consulting, Inc.



From: sharepoint@yahoogroups.com [mailto:sharepoint@yahoogroups.com] On
Behalf Of Kris Pahel
Sent: Thursday, July 09, 2009 5:47 AM
To: sharepoint@yahoogroups.com
Subject: RE: [SharePoint] My Sites running on its own web application..,








Bryan,

Would a DNS redirect work for this using the cname? I can't remember if
that would still want a port 80.

BTW...over the last year I have learned a ton from your posts. You have
a lot of good advice and I thought you should know that I appreciate
your work. Are you on twitter?

Kris A. Pahel

Database Manager

United Way of Greater Portland
207.874.1000 X310
www.unitedwaygp.org <http://www.unitedwaygp.org/>

LIVE UNITED (tm)

Give. Advocate. Volunteer.

From: sharepoint@yahoogroups.com <mailto:sharepoint%40yahoogroups.com>
[mailto:sharepoint@yahoogroups.com <mailto:sharepoint%40yahoogroups.com>
] On
Behalf Of Bryan Hart
Sent: Wednesday, July 08, 2009 8:02 PM
To: sharepoint@yahoogroups.com <mailto:sharepoint%40yahoogroups.com>
Subject: RE: [sharepoint] My Sites running on it's own web
application..,

Typically you'd do this with a "host header" site running on port 80.
There isn't really a good way to get a friendly URL on an alternate port
without involving some sort of URL re-writing proxy like ISA.

Bryan Hart | Technical Consultant | Solanite Consulting, Inc.

From: sharepoint@yahoogroups.com <mailto:sharepoint%40yahoogroups.com>
<mailto:sharepoint%40yahoogroups.com>
[mailto:sharepoint@yahoogroups.com <mailto:sharepoint%40yahoogroups.com>
<mailto:sharepoint%40yahoogroups.com>
] On
Behalf Of celts340520
Sent: Monday, June 15, 2009 2:10 PM
To: sharepoint@yahoogroups.com <mailto:sharepoint%40yahoogroups.com>
<mailto:sharepoint%40yahoogroups.com>
Subject: [sharepoint] My Sites running on it's own web application..,

Hello, we'll soon be rolling out My Sites to the masses at our company.

When initially setting up SharePoint we configured My Sites to run on
its own web app (as well as its own iis web site and app pool on port
83).

This generated a URL with the port number, 83, included.

What I'm trying to do is give a My Sites web application in SharePoint
running on port 83 (also currently on its own iis site and app pool) a
more user friendly URL - i.e. the port number 83 doesn't show - when
users browse their My Sites page and all subsequent pages underneath it.

We definitely want to keep My Sites on its own SharePoint 2007 Web
Application for performance and administrative purposes.

Is this an acceptable method to display a more user friendly URL...

We created a C-name record in DNS that resolves mysitestest to the ip of
our dev Moss server.

When creating our SSP we made My Sites its own web application using a
newly created IIS site and app pool on port 83.

We'll call the My Sites web app http://servername:83/

The primary Web app is http://servername on port 80.

The AAM I create for the My Sites web app is http://mysitestest (note:
no port specified in the AAM)

After this when I go into the edit shared service provider properties
page (My Site Location URL) or the My Site Settings page (Personal site
provider) within the SSP Admin page I see the My Sites Location URL
listed as http://mysitesdev:80/

Is this approach acceptable? Could it cause any potential issues?

Cheers

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]





[Non-text portions of this message have been removed]