We are attempting to load balance and Cluster the Mail Enable services.
We have SQL server and the POstoffices on a NAS.
The IME_ADMIN can't connect to the database because it's not on a local server.
How do we fix this? We don't want to have the DB on one of the servers, because if that went down there would be no reason to have two servers.
HELP!!! Clustered Server 2008 x64 Bit setup
-
MailEnable
- Site Admin
- Posts: 4441
- Joined: Tue Jun 25, 2002 3:03 am
- Location: Melbourne, Victoria Australia
You have two choices.
1. If you wish to use NTLM/Integrated auth with SQL Server then you need to create a user called IME_ADMIN on your DB server with the same password as your other mailenable nodes. That user needs to be granted dbo/full control of the mailenable database (which you can do with the sql server enterprise manager/management console).
2. You can either configure SQL Server to use "standalone" or "mixed" authentication and specify the mailenable DSN to use that user as dbo to the MailEnable database. ie: the old fassioned uid=sa pwd=password way.
The second option is probably simplest if you do not have a common windows authentication domain accross all your servers... because otherwise, you will need to make sure the password of IME_ADMIN on all servers is kept in sync.
1. If you wish to use NTLM/Integrated auth with SQL Server then you need to create a user called IME_ADMIN on your DB server with the same password as your other mailenable nodes. That user needs to be granted dbo/full control of the mailenable database (which you can do with the sql server enterprise manager/management console).
2. You can either configure SQL Server to use "standalone" or "mixed" authentication and specify the mailenable DSN to use that user as dbo to the MailEnable database. ie: the old fassioned uid=sa pwd=password way.
The second option is probably simplest if you do not have a common windows authentication domain accross all your servers... because otherwise, you will need to make sure the password of IME_ADMIN on all servers is kept in sync.
Regards, Andrew
