On Tue, 04 Jan 2005 20:46:35 +0000, johnydeath
<(E-Mail Removed)> wrote:
>a little (lot of) advice please
>
>My friend has an office with 10 pcs. Currently they are connected to
>the internet via a switch and an isdn modem. There is a server which
>runs exchange for the emails to be internally distributed from an
>externally hosted website.
>
>I am guessing that the exchange server is used purely because the the
>domain name is being taken from the webservice and then the exchange
>server adds the user as the prefix. ie webservice is domain.co.uk,
>exchange dials in to webservice, collects all *@domain.co.uk and then
>internally forwards them on to (E-Mail Removed), (E-Mail Removed)
>etc. He does get shedloads of spam mail.
By default Exchange can't actually do this out of the box. There is a
package called the POP3 connector for SBS server, not sure when it
first was included though.
>
>This seems a little cumbersome and not cost effective so I am trying to
>investigate and recommend a cheaper, less maintainance solution.
Yes, but later on you mention about talking to the company file server
remotely via VPN, be careful that by stripping out parts you don't
loose features which they use for years. One significant one would be
Exchange shared calendars.
>
>If he upgrades to adsl and bins his Highway Robbery (thanks for all the
>tips in that thread currently running) and the webhoster service
>provides 10x pop3 mail addresses, am I correct in saying that he can
>then bin his exchange server and set up his 10x pop3 accounts as
>(E-Mail Removed) etc etc. Ok there will be no redundancy for email
>accounts but that is not a problem - it is a very small close office.
Be sure you have a web control panel and multiple passwords for the
accounts - i.e, not just one master password. Again beware of
stripping off features which they have been using for a number of
years.
>
>I would appreciate comments, advice and if it can be done - pros and
>cons. Would it be better to leave the exchange server on a
>non-waranteed old pc running NT4 because it works? (at the moment!)
I take it its Exchange 5.5 then? Do you know if its Small Business
server (I think it may have been called Small Business Back Office
Server then)? This is basically a package of applications put
together to give the user a "single box does everything" experience.
If the Exchange server is causing issues, then you need to look at:
- Company requirements now and in the future
- What they have already
- Budgets
- Where they want to go
- Problems with the current system.
The SBS box also acted as the primary domain controler, if you take
this out and clients are using this it could cause a lot of work.
>
>She is also looking for a homeworking solution whereby he can either
>remotely connect to his PC to use a particular application, or to the
>company fileserver. I am guessing that providing the new adsl
>modem/router has VPN passthrough and the fileserver is running XPpro (XP
>Pro is running on home PC) then this would be possible.
You need something a bit more substancial on the server side than just
an XP pro to XP pro connection. The latest SBS can do VPN and also
supports connecting to PCs to view the desktop/interact with
applications etc.
There are also other solutions, depending on how much you want to
spend. Quite a lot of these run in Linux boxes with easy to configure
front ends for low maintanance use - products such as:
NetPilot
http://www.netpilot.com
Net-Inter-Net
http://www.kyzo.com
SME Server
http://www.contribs.org (free, but takes a bit of work
getting it going).
I don't have experience with all these products, but have them in a
list for times like these. Some of them may even run on your old NT
machine!
The other advantage of these boxes is that they also contain
antispam/virus software for only a little extra cost (the NIN
especially), whereas on a new SBS box you need to purchase Windows
server versions, which are expensive.
I am not advocating any solution, just bare in mind the above.
Andrew.
--
Andrew Hodgson in Bromyard, Herefordshire, UK.
My Email: use <andrew at hodgsonfamily dot org>.