Home Network Dilemma

I've been trying to make sense out of an assortment of products from
Microsoft involving multiple computers and I'm getting lost. I have a home
network of three machines running Windows 95 SE, Windows XP, and Vista. The
later two machines have legal copies of Office 2003 Professional. Outlook is
my mail server program.



These machines are on separate floors, I'm the sole user, and they are often
all on at the same time. The 95SE machine gets little use and if it has to
be excluded to find my solution, it's alright. The other two, however, must
be able to access my POP3 email and Outlook's Calendar, and Contact files.
Ideally, I'd like the XP machine to retain the Office Suite with the
elaborate filters and folders for email plus the calendar and all it's
reminders and alarms but I need to have access to it from the Vista machine.



This is not an enterprise, just a dream perhaps involving an elaborate
network for a home system. I'm retired, have the time, and the interest to
make one of these machines a server .but I'd be starting nearly from scratch
on the learning curve.



Can someone put me on a path to finding a way to get this accomplished in
the most cost-effective way? I've read about Microsoft Exchange and
SharePoint but they sound like they're for enterprises and probably bring
enterprise-size costs... but I'm not sure.

"jaygreg" <(E-Mail Removed)> wrote in message
news:%23i%(E-Mail Removed)...

> later two machines have legal copies of Office 2003 Professional. Outlook
> is my mail server program.

Outlook is not a Mail Server.

> be able to access my POP3 email and Outlook's Calendar, and Contact files.
> Ideally, I'd like the XP machine to retain the Office Suite with the
> elaborate filters and folders for email plus the calendar and all it's
> reminders and alarms but I need to have access to it from the Vista
> machine.

1. You have to have an Exchange Server ($$$$$$$$). That is what does the
"work".

2. You can't use POP3. You have to use Outlook as a MAPI Client (aka, an
Exchange Client),...which means You have to have an Exchange Server
($$$$$$$$).


--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------

>>Exchange Server ($$$$$$$$)<<

That's a service. Approximately how much for access from two machines by one
account holder?

"Phillip Windell" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> "jaygreg" <(E-Mail Removed)> wrote in message
> news:%23i%(E-Mail Removed)...
>
>> later two machines have legal copies of Office 2003 Professional. Outlook
>> is my mail server program.
>
> Outlook is not a Mail Server.
>
>> be able to access my POP3 email and Outlook's Calendar, and Contact
>> files. Ideally, I'd like the XP machine to retain the Office Suite with
>> the elaborate filters and folders for email plus the calendar and all
>> it's reminders and alarms but I need to have access to it from the Vista
>> machine.
>
> 1. You have to have an Exchange Server ($$$$$$$$). That is what does the
> "work".
>
> 2. You can't use POP3. You have to use Outlook as a MAPI Client (aka, an
> Exchange Client),...which means You have to have an Exchange Server
> ($$$$$$$$).
>
>
> --
> Phillip Windell
> www.wandtv.com
>
> The views expressed, are my own and not those of my employer, or
> Microsoft,
> or anyone else associated with me, including my cats.
> -----------------------------------------------------
>
>

"jaygreg" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
>>>Exchange Server ($$$$$$$$)<<
>
> That's a service. Approximately how much for access from two machines by
> one account holder?

It is a Server Application.
Wherever you buy it from can explain the Licensing But you need an Exchange
Client Access License (ECAL) for each human that uses it. It is about $70
per human (I don't know if Exchange comes with any ECALs out of the box or
not). The OS that it runs on will need Server CALs,...but Server 2003
already comes with 5 CALs


--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------

"jaygreg" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
>>>Exchange Server ($$$$$$$$)<<
>
> That's a service. Approximately how much for access from two machines by
> one account holder?

Well, it's actually a server that offers mail services, to straighten out
the technical terminology.

You can download the demo version from Microsoft's site. The current demo is
for Exchange 2007.

HOWEVER. You must understand Active Directory first, in order to implement
Exchange. This is because the user account database, and numerous other data
that Exchange uses. Matter of fact, Exchange must alter Active Directory
prior to installation, to accomodate the changes. This is a very huge topic,
and there are separate newsgroups for each. On top of that, an understanding
of DNS is required, because AD will not work if DNS is not implemented
properly for its internal use only, and on top of that, an understanding of
DNS on the internet is required in order to manipulate public records so
others in the world can 'find' your mail server on your network. In
addition, an understanding of your router and how to remap ports internally
in order to receive mail, and this depends on if your internet provider will
allow this type of traffic inbound because many block it in order to stop
people from running servers on their network.

Not trying to disuade you, but there's a learning curve that needs to be
addressed before jumping in. I would suggest, that if you have this much
time on your hands and have a few bucks to spend, to attend classes, and
this type of stuff is not a simple how to use Windows or Outlook class,
rather MSCE and MCITP classes that addresses the engineering level of
Windows, basic Windows services, application services (such as Exchange,
Active Directory), networking basics (TCPIP, DNS, firewalls, routing,
subnetting, network infrastructure designs), etc.

I hope that helps to steer you in the right direction.

--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSA Messaging, MCT
Microsoft Certified Trainer
(E-Mail Removed)

For urgent issues, you may want to contact Microsoft PSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

"Efficiency is doing things right; effectiveness is doing the right
things." - Peter F. Drucker
http://twitter.com/acefekay

Forgot to mention,...Exchange requires an Active Directory Domain,...which
requires a Domain Controller,...which requires another copy of the Server OS
($$$$)...which requires another Server($$$$).

If you want Exchange to be on the same box as the DC then you should use it
in a Virtual Machine,....or buy small business Server that is *designed* to
have them on the same machine. SBS2003 is that last version os SBS "all on
one box".

The next version of SBS use three machines. They can all 3 be physical
machines or it can be one physical machine and two virtual machines.

I am not an "SBS guy",...if you want more details on SBS you need to ask
people who specialize in SBS.

--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------

"Phillip Windell" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
>
> The next version of SBS use three machines. They can all 3 be physical
> machines or it can be one physical machine and two virtual machines.
>
> I am not an "SBS guy",...if you want more details on SBS you need to ask
> people who specialize in SBS.
>


Good point, SBS may be the better solution for him since everything is
combined. However, I still believe there will be a huge learning curve to
understand it, since it still runs AD, Exchange, and everything else on SBS.

Ace

Look at the Outlook Connector http://office.microsoft.com/en-us/ou...225181033.aspx and create a Hotmail account.

--

Jeff


"jaygreg" <(E-Mail Removed)> wrote in message news:%23i%(E-Mail Removed)...
I've been trying to make sense out of an assortment of products from
Microsoft involving multiple computers and I'm getting lost. I have a home
network of three machines running Windows 95 SE, Windows XP, and Vista. The
later two machines have legal copies of Office 2003 Professional. Outlook is
my mail server program.



These machines are on separate floors, I'm the sole user, and they are often
all on at the same time. The 95SE machine gets little use and if it has to
be excluded to find my solution, it's alright. The other two, however, must
be able to access my POP3 email and Outlook's Calendar, and Contact files.
Ideally, I'd like the XP machine to retain the Office Suite with the
elaborate filters and folders for email plus the calendar and all it's
reminders and alarms but I need to have access to it from the Vista machine.



This is not an enterprise, just a dream perhaps involving an elaborate
network for a home system. I'm retired, have the time, and the interest to
make one of these machines a server .but I'd be starting nearly from scratch
on the learning curve.



Can someone put me on a path to finding a way to get this accomplished in
the most cost-effective way? I've read about Microsoft Exchange and
SharePoint but they sound like they're for enterprises and probably bring
enterprise-size costs... but I'm not sure.

Would being able to access the XP computer from the other two solve your
dilemma? If so, then you just need to install a remote control program on
the XP computer. Here are two options I would suggest:



1.) If you have Windows XP Professional (not Home) on the XP computer,
then just enable remote desktop. See
http://www.microsoft.com/windowsXp/u...moteintro.mspx.
The Vista computer already has the software needed to connect to remote
desktop. I don't believe 95 would have that, but you should be able to
download a version for it.

2.) Install something like VNC. See
http://realvnc.com/products/free/4.1/download.html. You'll need to install
the "server" component on the XP computer and the client component on 95 and
Vista.



Note that the two options don't work exactly the same. With option 1, the XP
desktop gets locked if you connect to it remotely. With option 2, anyone
walking by can see what you're doing because the XP screen is not locked (at
least not be default).



On another note, someone commented that Outlook can only be used as a MAPI
client. That is completely untrue. The full version of Outlook (from 2007 on
back several versions) can be used as a MAPI, IMAP, or POP3 client.


--
Regards,
Mel K.
MCSA: M

"jaygreg" <(E-Mail Removed)> wrote in message
news:%23i%(E-Mail Removed)...
> I've been trying to make sense out of an assortment of products from
> Microsoft involving multiple computers and I'm getting lost. I have a home
> network of three machines running Windows 95 SE, Windows XP, and Vista.
> The later two machines have legal copies of Office 2003 Professional.
> Outlook is my mail server program.
>
>
>
> These machines are on separate floors, I'm the sole user, and they are
> often all on at the same time. The 95SE machine gets little use and if it
> has to be excluded to find my solution, it's alright. The other two,
> however, must be able to access my POP3 email and Outlook's Calendar, and
> Contact files. Ideally, I'd like the XP machine to retain the Office Suite
> with the elaborate filters and folders for email plus the calendar and all
> it's reminders and alarms but I need to have access to it from the Vista
> machine.
>
>
>
> This is not an enterprise, just a dream perhaps involving an elaborate
> network for a home system. I'm retired, have the time, and the interest to
> make one of these machines a server .but I'd be starting nearly from
> scratch on the learning curve.
>
>
>
> Can someone put me on a path to finding a way to get this accomplished in
> the most cost-effective way? I've read about Microsoft Exchange and
> SharePoint but they sound like they're for enterprises and probably bring
> enterprise-size costs... but I'm not sure.
>
>

I appreciate the description of the minefield that lies ahead if I choose to
proceed with Exchange. I may take a class this Fall under the Senior Guest
plan (free for Ohio residents ... if there's space available and the prof is
agreeable - they always are). Sounds a little like eating soup with a fork
though at this point; a lot of activity but little nourishment!

Jeff and Phil introduced me to alternatives I was unaware of. I'll look at
them later in the day. Thank you very much for your help. I may have a few
more questions after I look at those links.


"Mel K." <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Would being able to access the XP computer from the other two solve your
> dilemma? If so, then you just need to install a remote control program on
> the XP computer. Here are two options I would suggest:
>
>
>
> 1.) If you have Windows XP Professional (not Home) on the XP computer,
> then just enable remote desktop. See
> http://www.microsoft.com/windowsXp/u...moteintro.mspx.
> The Vista computer already has the software needed to connect to remote
> desktop. I don't believe 95 would have that, but you should be able to
> download a version for it.
>
> 2.) Install something like VNC. See
> http://realvnc.com/products/free/4.1/download.html. You'll need to install
> the "server" component on the XP computer and the client component on 95
> and Vista.
>
>
>
> Note that the two options don't work exactly the same. With option 1, the
> XP desktop gets locked if you connect to it remotely. With option 2,
> anyone walking by can see what you're doing because the XP screen is not
> locked (at least not be default).
>
>
>
> On another note, someone commented that Outlook can only be used as a MAPI
> client. That is completely untrue. The full version of Outlook (from 2007
> on back several versions) can be used as a MAPI, IMAP, or POP3 client.
>
>
> --
> Regards,
> Mel K.
> MCSA: M
>
> "jaygreg" <(E-Mail Removed)> wrote in message
> news:%23i%(E-Mail Removed)...
>> I've been trying to make sense out of an assortment of products from
>> Microsoft involving multiple computers and I'm getting lost. I have a
>> home network of three machines running Windows 95 SE, Windows XP, and
>> Vista. The later two machines have legal copies of Office 2003
>> Professional. Outlook is my mail server program.
>>
>>
>>
>> These machines are on separate floors, I'm the sole user, and they are
>> often all on at the same time. The 95SE machine gets little use and if it
>> has to be excluded to find my solution, it's alright. The other two,
>> however, must be able to access my POP3 email and Outlook's Calendar, and
>> Contact files. Ideally, I'd like the XP machine to retain the Office
>> Suite with the elaborate filters and folders for email plus the calendar
>> and all it's reminders and alarms but I need to have access to it from
>> the Vista machine.
>>
>>
>>
>> This is not an enterprise, just a dream perhaps involving an elaborate
>> network for a home system. I'm retired, have the time, and the interest
>> to make one of these machines a server .but I'd be starting nearly from
>> scratch on the learning curve.
>>
>>
>>
>> Can someone put me on a path to finding a way to get this accomplished in
>> the most cost-effective way? I've read about Microsoft Exchange and
>> SharePoint but they sound like they're for enterprises and probably bring
>> enterprise-size costs... but I'm not sure.
>>
>>
>
>