Hello,

We are starting to use Sharepoint to communicate with our users, both
on the LAN and remote. I have setup sharepoint so that remote users
can access it via RWW on port 987. This works, and internal users can
also access companyweb via the remote url i.e. [url down].

The issue is a bunch of internal stuff still seems to reference
[url down]..., rather than using the more compatible
[url down]...

For example, when alerts go out, those alerts have links which all
reference [url down]... so they don't work for non-LAN users.

Is there any way to make the experience better for people who are not
on our LAN without compromising it for people who are on the LAN?

Thanks
Blair

And why would you have non LAN users getting alerts regarding issues on the LAN
Just trying to understand the scenario, so as to offer better advise

The simple answer is that content on sharepoint is not limited to
being LAN-only issues & LAN-only content. In our organisation, just
because someone doesn't happen to reside on the same LAN as the SBS
server, does not mean they don't perform some of the same job
functions and therefore need to know some of the same information.

Is there any reason that links are to [url down].. so they
only work for LAN users, when they could be to [url down]...
which is automatically setup to work fine for LAN users, and it would
have the advantage of being able to work out of the box for remote
users as well?

Blair

On Mar 27, 5:12 pm, "Cris Hanna [SBS-MVP]"
<crisnospamha> wrote:
[..]

I guess it would be helpful if you could provide more detailed examples of these "alerts" that don't work, in order to know what's generating them and if they can be modified.

Let's say a document library is set to require content approval. John Doe is one of the users that is allowed to approve content for this library. As a result, he has configured an alert in the SharePoint library to notify him whenever a new item is added to the library (and thus needs approval).

John travels often, but uses Outlook over HTTP on his laptop. He is sitting in an airport waiting for a flight when he receives an email notification from SharePoint that Sally has submitted a new document to the library for approval. The alert that John recieves includes a link to the document that Sally uploaded. However, the link points to [url down] - which obviously cannot be resolved from John's current connection.

Blair -

This is by design on the SharePoint side - links are provided using the primary URL of the web application when it was provisioned. Obviously the SBS team had to use [url down] as the primary URL, because they couldn't anticipate what your public URL would be :^). Let me do some testing and see if there is a way to change the default URL without having to recreate the web application.

Thanks Chad, you've got it.
Look forward to your comments.
Blair

On Mar 28, 5:05 am, "Chad A. Gross"
<chadgr> wrote:
[..]