Good morning!

Now, I will confess to not doing any research on this so if someone wants to
tell me to "rtfm" I will not get mad!

Anyway, we have a client for whom we are setting up SharePoint Services on
SBS2003. That SBS2003 box is also running IIS and Exchange Server 2003 SP2.
My question is in regards to accessing SharePoint from the"outside" world.
So, just open up Internet Explorer and enter [url down]
and sign in and there you have it.

My colleague has mentioned to me that we need a second external IP Address
(get from the ISP) to do this. I completely believe him but he is not so
well versed with SBS 2003 and I know that SBS2003 does things differently
from Windows 2003 Standard (in some cases).

So, my question is: with SBS2003 - running Exchange 2003 - is there truly a
need for a second external IP Address, or is there some "SBS2003 way" of
doing it without that second WAN IP Address?

Now, life is not so tragic. All of the guys and gals in sales do use
Terminal Server, so there is always an "internal" method to access
SharePoint ([url down]). We would just like SharePoint to be
available to them without having to necessarily connect to the TS first.

Thanks,

Cary

Cary,

There is no need for a second IP address. You can use a different port to
access the site or port 80 with a host header. Actually, a similar
discussion started yesterday on another forum and the following link was
mentioned for anyone that needs a step-by-step on how to do that
http://davidschrag.com/schlog/167/in...-2003-standard

If you are asking - as you say you are - about the "SBS 2003 way" of
doing things, then the newsgroup to ask would be

microsoft.public.windows.server.sbs

There, aren't I nice, I didn't mention a M at all...

As WSS 2.0 is a standard part of a SBS 2003 installation, those very
bright people there can answer questions about WSS 2.0 in SBS 2003 too.

Mike Walsh
WSS FAQ [url down]
no questions by e-mail please



Cary Shultz wrote:
[..]

It is very do-able without using the same IP. Unfortunately I have not found
a single manual, but there are good blogs that discuss segments of the
process. One link has already been provided.

Alternate access mapping in WSSv3 is not intuitive to the first time user.
There is a very good white paper from Microsoft discussing AAMs (sorry I
can't provide the link right now). Make a point of finding it. Once
understood, AAMs are a piece of cake.

Good luck. Have fun.

"Cary Shultz" wrote:
[..]

Mike,

No issues. I sent this to both news groups...just to be safe. I figured
that I might get a reply like this.....Lord knows I used to give that sort
of reply when I was answering tons of questions in the AD news groups...

Cary

"Mike Walsh" <englantilainen> wrote in message
news:5980
[..]