Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

Newest users can not connect to SBS 2008 / Exchange 2007 via Entourage

Posted on 2010-04-28
18
Medium Priority
?
870 Views
Last Modified: 2012-05-09
I am having a strange issue. My first 24 user accounts are unaffected by this issue. The problem started with account 25.

All new users can not connect via Entourage to the server. We get Error -170 in the verify. They can connect via Outlook and OWA. I have tried to connect to the same account from multiple clients. From all those clients I can add accounts for any of the first 24 users, but not users 25, 26 or 27.

SBS 2008 SR 8.  Entourage 2k4 several levels.

The same email settings work for accounts 1-24. Nothing works for 25, 26 or 27.
0
Comment
Question by:cdeblois
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 10
  • 8
18 Comments
 
LVL 14

Expert Comment

by:btdownloads7
ID: 32337282
How many licenses do you ahve for your SBS2008 server? I'm guessing 25, which is why you are havong a problem -- Admin + 24 users is hitting your limit. You can check the event log on the server, and you should see a bunch of messages about this.
0
 

Author Comment

by:cdeblois
ID: 32337326
Additional:

All users created w/ SBS wizard and unmodified.

Only the new users see this error when connecting (img 1)

All users use the following config (img 2)

All users show the permissions shown from Exchange Mgmt Console (img 3)
a-Client-Settings.png
a-Setup-Asst.png
a-Exchange-settings.png
0
 

Author Comment

by:cdeblois
ID: 32337361
btdownloads7,

Thank you for the reply.

We have 25 CALS + 5 original.  However, it is my understanding that SBS 2008 does not register CALS.  It works on the "honor" system.  Keep the CALS on file.  There is no licensing component and I never added the additional 25 CALS via any mechnism.

Thanks.
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
LVL 14

Expert Comment

by:btdownloads7
ID: 32337380
OK, but you should still check the event viewer + exchange logs to see exactly what's happening when the users get bounced.
0
 
LVL 14

Expert Comment

by:btdownloads7
ID: 32337456
Are you configuring the Entourage users manually or letting it try automatically?
What server address is it using? Is it in the following format:
https://exchange.companyname.com/exchange/user@comany.com
0
 

Author Comment

by:cdeblois
ID: 32337463
Sorry, correct img 2
a-Client-Settings.png
0
 

Author Comment

by:cdeblois
ID: 32337568
btwdownloads7,

Thanks.  There are no errors in the server side logs.  (At least Application and System.)  I have not ramped up the Exchange logging, because I have not yet figured out which of the long list of logs I should increase the logging level of.
0
 
LVL 14

Expert Comment

by:btdownloads7
ID: 32337629
try changing the server to the format I suggested earlier. Here's an MS KB about it:
http://support.microsoft.com/kb/931350
0
 

Author Comment

by:cdeblois
ID: 32337817
btdownloads7,

Sorry missed that.  However, it doesn't matter how the server name is configured you get the same error.

Possible options for that box that have been tried (and suggested by other fora):

https://fqdn/owa
https://fqdn/exchange/user@domain
fqdn/owa
fqdn/exchange/user@domain

and all of the above permutations using the local name of the server.  We have our DNS server configured to provide the internal IP on requests for mail.actorsplayhouse.org because this avoids the annoying dialog to confirm the identity of the server when Entourage starts.

Thanks, again.  However, I believe that I have covered all the "simple" solutions.  I have even cleared the plists on the clients, created new identities, created new Mac accounts.  All to no avail.

The settings shown in img2 work for all accounts from 1-24, just not these new accounts...  That is what led me to post in the server arena rather than the Entourage area.  Although I did cross post at Mactopia's Entourage forum.
0
 
LVL 14

Expert Comment

by:btdownloads7
ID: 32337875
OK, try one moe thing for diagnostics purposes, please. On one of the computers that work fine, change the account settings to use the new "bad" user accounts and see if they work. If you start getting an error, then the problem is with the user account, and has to be dealt with on the server. If you don't get an error, then the problem is on the computer itself, and something is wrong with the account config,
0
 

Author Comment

by:cdeblois
ID: 32337949
btdownloads7,

We have.  We can on ANY working client connect to one or more of the existing (1-24) mailboxes.  However, on any of those clients we get the above errors when trying to connect to accounts 25-27.  Or to rephrase:

All clients can connect to any account 1-24 via Entourage.  All clients can connect to multiple accounts 1-24.

No client can connect to accounts 25-27. (Even with new identities, or new Mac logon accounts).

Outlook and OWA connect to all accounts 1-27.

THAT is what leads me to believe I have an issue on the server.
0
 
LVL 14

Expert Comment

by:btdownloads7
ID: 32338457
OK, that's pretty weird. Are you sure that all users have been set up identically on the server? Do you use a user template, or do you manually select all the options? Are all the new users members of exactly the same groups as the old users?
0
 

Author Comment

by:cdeblois
ID: 32339224
All users are created using the SBS console "Add User" wizard.  Nothing is configured individually (OK we add the security groups for our file share, but that is it.)

No options are selected manually.  The working users were created when the server was built.  The new users some 4 weeks later.  Not even an update was run in between.

Yes very weird and I have many hours into this already.
0
 
LVL 14

Expert Comment

by:btdownloads7
ID: 32339425
Just in case, please check that all the new users are actually members of the exact same groups.

Also, try creating a completely new user, but not from SBS wizard, but form the Exchange Management console. (Under Recepient Configuration -- > Mailbox --> New Mailbox). It'll alow you to create a new user as well, but may be doing something "extra" to make it work properly. If this works, you'll need to delete the existing bad users and re-add them using this method.
0
 

Author Comment

by:cdeblois
ID: 32339849
Good thought.  No change.  Still error 170.
0
 
LVL 14

Expert Comment

by:btdownloads7
ID: 32339982
Wow, OK, I think that puts me out of ideas.

There is one last thing you can try, but it's pretty drastic. I'm still going back to the number of licenses, even though it's supposed to be honor based, but I know that SBS 2008 FE edition, for example, only supports a maximum of 15 CALs. To test my theory, what you could try is delete one of the "good" users (after backing up any of their filoes on the server plus their mailbox in Exchange), then reboot the server and see if one of the new users can now use Entourage. I just want to see if its an issue with the total number of users that are being supported.
0
 

Author Comment

by:cdeblois
ID: 32340665
Yep, that is drastic.  but I might just have an account that wouldn't be missed (to paraphrase Ko-Ko).  I might just try that.

Thanks again for your help.
0
 

Accepted Solution

by:
cdeblois earned 0 total points
ID: 32810191
All right.  Finally called MS.  The server group looked at the server for 2 seconds, had a bunch of discussion in the back ground and finally said,  "You will have to talk to the Entourage Group, goodbye."

We Entourage (who were able to actually create a live meeting session to a mac, unlike the server group) took at look at it and said, "OK, try this..."

For the new users we entered the server as:  computer.domain.local/exchange/user@emaildomain.org

And it worked!  We had tried this before (btw).  But the laying on of hands is a powerful thing.

Case closed.   Apparently you have to use a different server name every now and then...  Ain't Entourage sweet.
0

Featured Post

Office 365 Training for Admins - 7 Day Trial

Learn how to provision tenants, synchronize on-premise Active Directory, implement Single Sign-On, customize Office deployment, and protect your organization with eDiscovery and DLP policies.  Only from Platform Scholar.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

After seeing many questions for JRNL_WRAP_ERROR for replication failure, I thought it would be useful to write this article.
On September 18, Experts Exchange launched the first installment of the Help Bell, a new feature for Premium Members, Team Accounts, and Qualified Experts. The Help Bell will serve as an additional tool to help teams increase question visibility.
This tutorial will walk an individual through configuring a drive on a Windows Server 2008 to perform shadow copies in order to quickly recover deleted files and folders. Click on Start and then select Computer to view the available drives on the se…
how to add IIS SMTP to handle application/Scanner relays into office 365.
Suggested Courses

721 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question