Exchange problem

We are currently running SBS 2003 in a mixed PC/Mac network. Initial setup
was in 2004 and all worked well. Mac users use Outlook 2001 to access
exchange mail, cal, etc. In summer of 2004 any new account that was setup
could only be accessed by a PC and not a Mac. They get a message that the
logon credentials cannot be accepted.

Users can access their exchange account in Entourage by setting up an IMAP
account, but cannot access Exchange using Entourage 2004 LDAP/Web-DAV
account. This is not a good solution as those users cannot access shared
calendars. It I take an old user account that was setup prior to these
errors I can change the user name and that account can be access by using
Outlook 2001. Changing the user's password at the server level also causes
the account to no longer be accessed by Outlook 2001.

Also cannot get OWA to work. It seems that somewhere along the line
something got corrupted with Exchange.

Was on maternity leave and now back to work full-time and want to get this
resolved. Which would be the wisest course of action to take:

a reinstall of SBS
Running Repair
Installing service packs and seeing if that fixes the problem.

Any suggestions or advice would be appreciated. Thank you.

Lianne

Hello Lianne,

Thank you for posting in the SBS newsgroup.

According to your description, I understand that the Mac users cannot
access Exchange using Entourage 2004 LDAP/Web-DAV account. If I have
misunderstood your concern, please don't hesitate to let me know.

Since I am not sure how you configured your MAC client to use email against
SBS 2003, I would like to suggest you refer to the following steps to
configure your MAC client for using email:

Access E-mail Using Entourage 2004
=====================
In order to use the Microsoft Entourage 2004 e-mail and personal
information manager to access e-mail messages on the server, complete the
following steps:
- Verify that the client computer is properly resolving DNS queries
to the server.
- Set up an Exchange Server account on the client computer.
- Add the server to the proxy exclusion list.

Verify that the client computer is properly resolving DNS queries to the
server
============================================
1. Open a Web browser and go to https://ServerFQDN/exchange, where
ServerFQDN is the fully qualified domain name of the Exchange server (for
example, https://sbsserver.smallbuiness.local/exchange). The Exchange
server is also the computer running Windows Small Business Server 2003. If
you can log in and use Outlook Web Access, continue to the next procedure.

2. If you are using Microsoft Internet Explorer 5 for Mac, you might
get this error: "The identity certificate is invalid." This error indicates
that there is a self-signed certificate on the server that Internet
Explorer cannot process. However, this error also indicates that the name
resolved properly, so you can continue to the next procedure. If you want
to verify further, use another Web browser to go to the same Web site
https://ServerFQDN/exchange. The other browser might also generate an alert
related to the certificate, but you will be able to continue.

3. If the client computer does not resolve the fully qualified
domain name of the server, and the domain name ends in ".local," follow the
instructions in "Step 2: Configure DNS," to resolve the issue.

Set Up an Exchange Server Account on the Client Computer
==================================
You can set up an Exchange Server account in Entourage 2004 by using one of
the following methods:
- Setup Assistant,
- Manual configuration.
To set up an Exchange Server account for a user, you need to know the
user's e-mail address, account ID (which is the same as their domain logon
name), their password, and the fully qualified domain name of the computer
running Windows Small Business Server 2003.

To set up and Exchange Server account on a client computer by using Setup
Assistant
1. On the Tools menu of the client computer, click Accounts, and
then click New.
2. If prompted, enter the username and password of the Macintosh
user.
3. Select the My account is on an Exchange server check box (see
Figure 4).
4. In E-mail address, type the e-mail address of your Windows Small
Business Server domain user account ( for example,
).
5. In User ID, type the domain user name of the user .
6. In Domain, type the domain name for the server. Use either the
NetBIOS domain name or the fully qualified domain name (for example,
smallbusiness ). To locate the NetBIOS name on the server, click Start,
click Run, and then type cmd. At the command prompt, type Set. The NetBIOS
domain name is listed as USERDOMAIN.
7. In Password, enter the user's logon password.
8. Click the right-arrow to continue.
9. If automatic configuration fails, click the right-arrow in the
Automatic Configuration Failed page to continue.
10. The Verify and Complete Settings window appears. In Your name,
type the user's full name. (See Figure 5.)
11. In Exchange Server, type https://ServerFQDN/exchange, where
ServerFQDN is the fully qualified domain name of the server (for example,
https://sbsserver.smallbusiness.local /exchange).
12. In LDAP Server, type the fully qualified domain name of the
server (for example, https://sbsserver.smallbusiness.local).
13. Select the Use SSL for these servers check box .
14. Click the right-arrow to continue.
15. Click Verify Settings. If there is a self-signed certificate on
the server, you might get the following error: "Unable to establish a
secure connection to [serverFQDN] because the correct root certificate is
not installed." Click OK to continue.
16. If the account settings are correct, click the right-arrow to
continue. Otherwise, click the left-arrow and correct the information as
necessary.
17. Click Finish to close the Account Setup Assistant.

To manually set up and Exchange Server account on a client computer
1. On the Tools menu on the client computer, click Accounts, click
the Exchange tab, and then click New.
2. Select the My account is on an Exchange server check box, and
then click Configure my account manually.
3. In Account name, type the name of the Exchange account for that
user (this can be the same as the user's logon name).
4. In Account ID, type the logon name of the domain user account.
5. In Password, type the user's logon password.
6. In Domain, type the domain name for the server. Use either the
NetBIOS domain name or the fully qualified domain name (for example,
smallbusiness ). To locate the NetBIOS name on the server, click Start,
click Run, and then type cmd. At the command prompt, type Set. The NetBIOS
domain name is listed as USERDOMAIN.
7. In Exchange Server, type https://ServerFQDN/exchange, where
ServerFQDN is the fully qualified domain name of the server (the computer
running Windows Small Business Server 2003). (See Figure 6. )
8. In E-mail address, type the e-mail address of your Windows Small
Business Server domain user account ( for example
), and then click OK.
9. Click the Directory tab.
10. In LDAP server, type the fully qualified domain name of the
server (for example, sbsserver.smallbusiness.local).
11. In the Entourage is now synchronizing message box, click OK.
12. Click the Click here for advanced options button.
13. Select the This server requires me to log on check box.
14. Select the Override default LDAP port check box, and then type
3268 in the box next to it.
15. Click the Advanced tab.
16. In Public folders server, type https://ServerFQDN/public, where
ServerFQDN is the fully qualified domain name of the server.
17. Select the Synchronize all items to server check box.
18. Select the DAV service requires secure connection (SSL) check
box, and then click OK.

To add the server to the proxy exclusion list
========================
Note
Skip this procedure if the server is not running Microsoft Internet
Security and Acceleration Server (ISA) and the client computer is not
configured to go through the ISA server for Web proxy.

1. From the Apple menu on the client computer, click System
Preferences.
2. Click the Network icon.
3. Click Built-in Ethernet, and then click Configure.
4. Click the Proxies tab.
5. Verify that the Web Proxy (HTTP) and Secure Web Proxy (HTTPS)
check boxes are selected, then in Bypass proxy settings for these Hosts &
Domains, type the NetBIOS name and the fully qualified domain name of the
server. Type each name on a separate line.
6. Click Apply Now.

Please follow the steps above and see if you can now read emails in
Entourage.

I am appreciated your time and cooperation. If anything is unclear, please
feel free to let me know. I am looking forward to hearing from you.

Best regards,

Nathan Liu (MSFT)
Microsoft CSS Online Newsgroup Support
Get Secure! - www.microsoft.com/security
================================================== ===
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
>Thread-Topic: Exchange problem
>thread-index: AcWHK2Cjj7EbkrQDS02a5eA5FhFV0A==
>X-WBNR-Posting-Host: 198.107.22.167
>From: =?Utf-8?B?WXVraXJh?= <>
>Subject: Exchange problem
>Date: Tue, 12 Jul 2005 14:48:02 -0700
>Lines: 27
>Message-ID: <4AC39326-8CD8-4098-BC69->
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.windows.server.sbs
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFT NGXA03.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:135168
>X-Tomcat-NG: microsoft.public.windows.server.sbs
>
>We are currently running SBS 2003 in a mixed PC/Mac network. Initial
setup
>was in 2004 and all worked well. Mac users use Outlook 2001 to access
>exchange mail, cal, etc. In summer of 2004 any new account that was setup
>could only be accessed by a PC and not a Mac. They get a message that the
>logon credentials cannot be accepted.
>
>Users can access their exchange account in Entourage by setting up an IMAP
>account, but cannot access Exchange using Entourage 2004 LDAP/Web-DAV
>account. This is not a good solution as those users cannot access shared
>calendars. It I take an old user account that was setup prior to these
>errors I can change the user name and that account can be access by using
>Outlook 2001. Changing the user's password at the server level also
causes
>the account to no longer be accessed by Outlook 2001.
>
>Also cannot get OWA to work. It seems that somewhere along the line
>something got corrupted with Exchange.
>
>Was on maternity leave and now back to work full-time and want to get
this
>resolved. Which would be the wisest course of action to take:
>
>a reinstall of SBS
>Running Repair
>Installing service packs and seeing if that fixes the problem.
>
>Any suggestions or advice would be appreciated. Thank you.
>
>Lianne
>

Nathan,

Thank you for your reply. The setting information you provided was very
helpful. Unfortunately I am still having problems. The main problem seems
to be that our SBS does not seem to recognize or accept our account
passwords. This only happens on brand new accounts using Outlook 2001 or
when trying to go through Entourage. When using a PC passwords are accepted
just fine. I think there is definitely a problem with the SBS as we did not
have this problem for the first 6 months after we set up the server. I am
wondering if it is better to try to apply all the service packs or do a
repair of the server setup. What do you think.

Thank you.

Lianne

"Nathan Liu [MSFT]" wrote:

> Hello Lianne,
>
> Thank you for posting in the SBS newsgroup.
>
> According to your description, I understand that the Mac users cannot
> access Exchange using Entourage 2004 LDAP/Web-DAV account. If I have
> misunderstood your concern, please don't hesitate to let me know.
>
> Since I am not sure how you configured your MAC client to use email against
> SBS 2003, I would like to suggest you refer to the following steps to
> configure your MAC client for using email:
>
> Access E-mail Using Entourage 2004
> =====================
> In order to use the Microsoft Entourage 2004 e-mail and personal
> information manager to access e-mail messages on the server, complete the
> following steps:
> - Verify that the client computer is properly resolving DNS queries
> to the server.
> - Set up an Exchange Server account on the client computer.
> - Add the server to the proxy exclusion list.
>
> Verify that the client computer is properly resolving DNS queries to the
> server
> ============================================
> 1. Open a Web browser and go to https://ServerFQDN/exchange, where
> ServerFQDN is the fully qualified domain name of the Exchange server (for
> example, https://sbsserver.smallbuiness.local/exchange). The Exchange
> server is also the computer running Windows Small Business Server 2003. If
> you can log in and use Outlook Web Access, continue to the next procedure.
>
> 2. If you are using Microsoft Internet Explorer 5 for Mac, you might
> get this error: "The identity certificate is invalid." This error indicates
> that there is a self-signed certificate on the server that Internet
> Explorer cannot process. However, this error also indicates that the name
> resolved properly, so you can continue to the next procedure. If you want
> to verify further, use another Web browser to go to the same Web site
> https://ServerFQDN/exchange. The other browser might also generate an alert
> related to the certificate, but you will be able to continue.
>
> 3. If the client computer does not resolve the fully qualified
> domain name of the server, and the domain name ends in ".local," follow the
> instructions in "Step 2: Configure DNS," to resolve the issue.
>
> Set Up an Exchange Server Account on the Client Computer
> ==================================
> You can set up an Exchange Server account in Entourage 2004 by using one of
> the following methods:
> - Setup Assistant,
> - Manual configuration.
> To set up an Exchange Server account for a user, you need to know the
> user's e-mail address, account ID (which is the same as their domain logon
> name), their password, and the fully qualified domain name of the computer
> running Windows Small Business Server 2003.
>
> To set up and Exchange Server account on a client computer by using Setup
> Assistant
> 1. On the Tools menu of the client computer, click Accounts, and
> then click New.
> 2. If prompted, enter the username and password of the Macintosh
> user.
> 3. Select the My account is on an Exchange server check box (see
> Figure 4).
> 4. In E-mail address, type the e-mail address of your Windows Small
> Business Server domain user account ( for example,
> ).
> 5. In User ID, type the domain user name of the user .
> 6. In Domain, type the domain name for the server. Use either the
> NetBIOS domain name or the fully qualified domain name (for example,
> smallbusiness ). To locate the NetBIOS name on the server, click Start,
> click Run, and then type cmd. At the command prompt, type Set. The NetBIOS
> domain name is listed as USERDOMAIN.
> 7. In Password, enter the user's logon password.
> 8. Click the right-arrow to continue.
> 9. If automatic configuration fails, click the right-arrow in the
> Automatic Configuration Failed page to continue.
> 10. The Verify and Complete Settings window appears. In Your name,
> type the user's full name. (See Figure 5.)
> 11. In Exchange Server, type https://ServerFQDN/exchange, where
> ServerFQDN is the fully qualified domain name of the server (for example,
> https://sbsserver.smallbusiness.local /exchange).
> 12. In LDAP Server, type the fully qualified domain name of the
> server (for example, https://sbsserver.smallbusiness.local).
> 13. Select the Use SSL for these servers check box .
> 14. Click the right-arrow to continue.
> 15. Click Verify Settings. If there is a self-signed certificate on
> the server, you might get the following error: "Unable to establish a
> secure connection to [serverFQDN] because the correct root certificate is
> not installed." Click OK to continue.
> 16. If the account settings are correct, click the right-arrow to
> continue. Otherwise, click the left-arrow and correct the information as
> necessary.
> 17. Click Finish to close the Account Setup Assistant.
>
> To manually set up and Exchange Server account on a client computer
> 1. On the Tools menu on the client computer, click Accounts, click
> the Exchange tab, and then click New.
> 2. Select the My account is on an Exchange server check box, and
> then click Configure my account manually.
> 3. In Account name, type the name of the Exchange account for that
> user (this can be the same as the user's logon name).
> 4. In Account ID, type the logon name of the domain user account.
> 5. In Password, type the user's logon password.
> 6. In Domain, type the domain name for the server. Use either the
> NetBIOS domain name or the fully qualified domain name (for example,
> smallbusiness ). To locate the NetBIOS name on the server, click Start,
> click Run, and then type cmd. At the command prompt, type Set. The NetBIOS
> domain name is listed as USERDOMAIN.
> 7. In Exchange Server, type https://ServerFQDN/exchange, where
> ServerFQDN is the fully qualified domain name of the server (the computer
> running Windows Small Business Server 2003). (See Figure 6. )
> 8. In E-mail address, type the e-mail address of your Windows Small
> Business Server domain user account ( for example
> ), and then click OK.
> 9. Click the Directory tab.
> 10. In LDAP server, type the fully qualified domain name of the
> server (for example, sbsserver.smallbusiness.local).
> 11. In the Entourage is now synchronizing message box, click OK.
> 12. Click the Click here for advanced options button.
> 13. Select the This server requires me to log on check box.
> 14. Select the Override default LDAP port check box, and then type
> 3268 in the box next to it.
> 15. Click the Advanced tab.
> 16. In Public folders server, type https://ServerFQDN/public, where
> ServerFQDN is the fully qualified domain name of the server.
> 17. Select the Synchronize all items to server check box.
> 18. Select the DAV service requires secure connection (SSL) check
> box, and then click OK.
>
> To add the server to the proxy exclusion list
> ========================
> Note
> Skip this procedure if the server is not running Microsoft Internet
> Security and Acceleration Server (ISA) and the client computer is not
> configured to go through the ISA server for Web proxy.
>
> 1. From the Apple menu on the client computer, click System
> Preferences.
> 2. Click the Network icon.
> 3. Click Built-in Ethernet, and then click Configure.
> 4. Click the Proxies tab.
> 5. Verify that the Web Proxy (HTTP) and Secure Web Proxy (HTTPS)
> check boxes are selected, then in Bypass proxy settings for these Hosts &
> Domains, type the NetBIOS name and the fully qualified domain name of the
> server. Type each name on a separate line.
> 6. Click Apply Now.
>
> Please follow the steps above and see if you can now read emails in
> Entourage.
>
> I am appreciated your time and cooperation. If anything is unclear, please
> feel free to let me know. I am looking forward to hearing from you.
>
> Best regards,
>
> Nathan Liu (MSFT)
> Microsoft CSS Online Newsgroup Support
> Get Secure! - www.microsoft.com/security
> ================================================== ===
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> --------------------
> >Thread-Topic: Exchange problem
> >thread-index: AcWHK2Cjj7EbkrQDS02a5eA5FhFV0A==
> >X-WBNR-Posting-Host: 198.107.22.167
> >From: =?Utf-8?B?WXVraXJh?= <>
> >Subject: Exchange problem
> >Date: Tue, 12 Jul 2005 14:48:02 -0700
> >Lines: 27
> >Message-ID: <4AC39326-8CD8-4098-BC69->
> >MIME-Version: 1.0
> >Content-Type: text/plain;
> > charset="Utf-8"
> >Content-Transfer-Encoding: 7bit
> >X-Newsreader: Microsoft CDO for Windows 2000
> >Content-Class: urn:content-classes:message
> >Importance: normal
> >Priority: normal
> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> >Newsgroups: microsoft.public.windows.server.sbs
> >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
> >Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFT NGXA03.phx.gbl
> >Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:135168
> >X-Tomcat-NG: microsoft.public.windows.server.sbs
> >
> >We are currently running SBS 2003 in a mixed PC/Mac network. Initial
> setup
> >was in 2004 and all worked well. Mac users use Outlook 2001 to access
> >exchange mail, cal, etc. In summer of 2004 any new account that was setup
> >could only be accessed by a PC and not a Mac. They get a message that the
> >logon credentials cannot be accepted.
> >
> >Users can access their exchange account in Entourage by setting up an IMAP
> >account, but cannot access Exchange using Entourage 2004 LDAP/Web-DAV
> >account. This is not a good solution as those users cannot access shared
> >calendars. It I take an old user account that was setup prior to these
> >errors I can change the user name and that account can be access by using
> >Outlook 2001. Changing the user's password at the server level also
> causes
> >the account to no longer be accessed by Outlook 2001.
> >
> >Also cannot get OWA to work. It seems that somewhere along the line
> >something got corrupted with Exchange.
> >
> >Was on maternity leave and now back to work full-time and want to get
> this
> >resolved. Which would be the wisest course of action to take:
> >
> >a reinstall of SBS
> >Running Repair
> >Installing service packs and seeing if that fixes the problem.
> >
> >Any suggestions or advice would be appreciated. Thank you.
> >
> >Lianne
> >
>
>

Hi Lianne,

Thank you for your update!

Can you access the mailboxes through Outlook 2003 from Windows clients? If
you can, this should be the MAC issue and you'd better post in the
microsoft.public.outlook.mac newsgroup for help. As for the OWA issue,
could you tell us the exact symptoms when a Windows client fails to access
his mailbox through OWA?

Thank you for your time!

Sincerely,

Cliff Zhang
Microsoft Online Partner Support
MCSE 2000/2003


When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

================================================== ===

Business-Critical Phone Support (BCPS) provides you with technical phone
support at no charge during critical LAN outages or "business down"
situations. This benefit is available 24 hours a day, 7 days a week to all
Microsoft technology partners in the United States and Canada.


This and other support options are available here:

BCPS:
https://partner.microsoft.com/US/tec...rview/40010469

Others: https://partner.microsoft.com/US/tec...pportoverview/


If you are outside the United States, please visit our International
Support page:
http://support.microsoft.com/default...rnational.aspx.

================================================== ===

This posting is provided "AS IS" with no warranties, and confers no rights.

Cliff,

Thank you for your response. I'm not sure what I did but now OWA is working
on the PC's and some of the Macs using Netscape. Outlook is still not
working, but its progress. I will try posting to the Mac group about our
Outlook problem.

Lianne

""Cliff Zhang [MSFT]"" wrote:

> Hi Lianne,
>
> Thank you for your update!
>
> Can you access the mailboxes through Outlook 2003 from Windows clients? If
> you can, this should be the MAC issue and you'd better post in the
> microsoft.public.outlook.mac newsgroup for help. As for the OWA issue,
> could you tell us the exact symptoms when a Windows client fails to access
> his mailbox through OWA?
>
> Thank you for your time!
>
> Sincerely,
>
> Cliff Zhang
> Microsoft Online Partner Support
> MCSE 2000/2003
>
>
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
>
> ================================================== ===
>
> Business-Critical Phone Support (BCPS) provides you with technical phone
> support at no charge during critical LAN outages or "business down"
> situations. This benefit is available 24 hours a day, 7 days a week to all
> Microsoft technology partners in the United States and Canada.
>
>
> This and other support options are available here:
>
> BCPS:
> https://partner.microsoft.com/US/tec...rview/40010469
>
> Others: https://partner.microsoft.com/US/tec...pportoverview/
>
>
> If you are outside the United States, please visit our International
> Support page:
> http://support.microsoft.com/default...rnational.aspx.
>
> ================================================== ===
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
>
>

Hi Lianne,

Thank you for the update. Please also have a test on a Outlook 2003 client
and let us know whether the problem persists.

If there's any other update or questions, please feel free to post back.

Regards,

Bill Peng
MCSE 2000, MCDBA, CCNP, CCDA
Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security
================================================== ===
The SBS public newsgroup only focuses on SBS related technical issues, for
other Microsoft products, we recommend you to post to appropriate newsgroup
to get most qualified responses.
http://www.microsoft.com/communities...s/default.aspx

When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive notification. When responding to
posts via your newsreader, please "Reply to Group" so that others may learn
and benefit from your issue.

Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.

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

Any input or comments in this thread are highly appreciated.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
>Thread-Topic: Exchange problem
>thread-index: AcWJXAA3bnVuZvoUR7K/nSV8CsrP+w==
>X-WBNR-Posting-Host: 198.107.22.167
>From: =?Utf-8?B?eXVraXJh?= <>
>References: <4AC39326-8CD8-4098-BC69->
<Gk$>
<D2D06578-467D-4A19-95E1->
<>
>Subject: RE: Exchange problem
>Date: Fri, 15 Jul 2005 09:41:08 -0700
>Lines: 61
>Message-ID: <0696AF95-6FF6-4E4D-BF05->
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.windows.server.sbs
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:136121
>X-Tomcat-NG: microsoft.public.windows.server.sbs
>
>
>Cliff,
>
>Thank you for your response. I'm not sure what I did but now OWA is
working
>on the PC's and some of the Macs using Netscape. Outlook is still not
>working, but its progress. I will try posting to the Mac group about our
>Outlook problem.
>
>Lianne
>
>""Cliff Zhang [MSFT]"" wrote:
>
>> Hi Lianne,
>>
>> Thank you for your update!
>>
>> Can you access the mailboxes through Outlook 2003 from Windows clients?
If
>> you can, this should be the MAC issue and you'd better post in the
>> microsoft.public.outlook.mac newsgroup for help. As for the OWA issue,
>> could you tell us the exact symptoms when a Windows client fails to
access
>> his mailbox through OWA?
>>
>> Thank you for your time!
>>
>> Sincerely,
>>
>> Cliff Zhang
>> Microsoft Online Partner Support
>> MCSE 2000/2003
>>
>>
>> When responding to posts, please "Reply to Group" via your newsreader so
>> that others may learn and benefit from your issue.
>>
>> ================================================== ===
>>
>> Business-Critical Phone Support (BCPS) provides you with technical phone
>> support at no charge during critical LAN outages or "business down"
>> situations. This benefit is available 24 hours a day, 7 days a week to
all
>> Microsoft technology partners in the United States and Canada.
>>
>>
>> This and other support options are available here:
>>
>> BCPS:
>>
https://partner.microsoft.com/US/tec...rview/40010469
>>
>> Others:
https://partner.microsoft.com/US/tec...pportoverview/
>>
>>
>> If you are outside the United States, please visit our International
>> Support page:
>> http://support.microsoft.com/default...rnational.aspx.
>>
>> ================================================== ===
>>
>> This posting is provided "AS IS" with no warranties, and confers no
rights.
>>
>>
>>
>>
>