I have a problem I wanted to run by everyone to see what ideas and
solutions are generated.

About six months ago we started to toy with this new product called
SharePoint.

What we did was develop a test environment running SharePoint Portal
for local collaboration to see if it would fit our requirements.

We built two servers, one dedicated SQL 2000 server and the other
server running SharePoint (Web, Job, Index, Search).

The server was built via http://svrname which at the time wasn't an
issue (I came into this project mid way though). I feel the web
piece should have been set up better, http://portal.company.com" target="_blank" rel="nofollow">http://portal.company.com for
internal access, both domestically and internationally.

Now our problem, SharePoint was such a great product it got leaked
globally. We set up an alias on our DNS server to point users to the
server by using the http://portal.company.com" target="_blank" rel="nofollow">http://portal.company.com which forwards to
http://svrname.

The problems we encounter are the sites that were set up. This thing
should not have gone into production and now when users who are
global try to access http://svrname which times out, they can't
access it. When new sites are created it defaults back to
http://svrname.

My question is, in order for this thing to be friendlier to the
global community do we need to rebuild the portal or can we
reconfigure the portal settings and web settings etc? We would like
to set up multiple portals for security reasons to meet the
requirements of our different business units.