Re: Proxy and Firewalls

"laz" <laz@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:F3489D96-FC3B-4321-BED1-F0990C8C9311@xxxxxxxxxxxxx...

We use SBS 2003 Prem, (have not installed ISA).
We are a Company of 12 Consultants and use SBS to access Email and
sharepoint via web from our customer sites.
OWA works great from all our customers, but sharepoint does not. this is
because of port 444. All our customers have Proxy servers and Firewalls, and
in many cases they will not open port 444, this is especially true for the
large multi national companies.
This serverly impacts the advantages of SBS and sharepoint to us, any
sugestions on how we could work around this will be appreciated. Just note it
needs to work through most firewalls and proxy installations.

Relevant Pages

• Re: Is it me or does Vista suck with SBS03?
  ... If you've got any customers that utilize sharepoint to a greater extent, Office 2k7 is pretty sweet - even moreso in combination with sharepoint V3. ... When SBS 2k3 came to market, most of my customers were on Office 2k, and that's part of the reason sharepoint didn't get more traction. ...
  (microsoft.public.windows.server.sbs)
• Proxy and Firewalls
  ... We use SBS 2003 Prem, ... OWA works great from all our customers, but sharepoint does not. ... needs to work through most firewalls and proxy installations. ...
  (microsoft.public.windows.server.sbs)
• Re: replication
  ... This in fact may be one of those customers who may not be a great fit for SBS. ... If Sharepoint is that critical to their business, they may wish to look into hosted Sharepoint solution. ... Of course you'd need to configure MX records to have mail go to the west coast server if the east coast was down. ...
  (microsoft.public.windows.server.sbs)
• Re: SharePoint Services
  ... I'm under the impression that the data tables can be uploaded to a SharePoint location, and that read / edit permissions could be enabled for different users??? ... It was common for customers to have accounts in more than one store / town ... ... However if you do not have share point services setup, nor do you have the expertise and training and resource personnel to run and set up those servers + SharePoint, **if** you users NOW have some type of connection to you network, then then I think the easiest and least amount of effort would be to simply put the backend database on SQL server and and link your front ends to that back end user. ... So, if these people are outside of your corporate network now, then expertise and ability to set up secure connections to allow them to come into your corporate network and pull data from sql server is VERY seriuos issue. ...
  (comp.databases.ms-access)
• I broke Sharepoint :(
  ... SBS was installed and the server was up and running including the default ... After 2 days I was looking at SQL backups I relaised that Sharepoint ... database and the other instances were not migrated accross. ...
  (microsoft.public.windows.server.sbs)