stives1974
asked on
POP3 failed logins Exchange 2010
Hello Experts Exchange
I have an issue with pop3 logins in an Exchange 2010 DAG environment. WE have two servers holding the Mailbox Server role and one holding the CAS and Hub Transport roles. The passive Mailbox server is in another site, there is no firewall in between.
Everything works fine when mailboxes are on the active mailbox database but were failing recently. Upon logging into the Exchange Management Console we noticed that the Exchange server had failed over to the copy mailbox server. Once we moved the active copy back the the original server pop3 logins worked again.
To test I have created a single instance database and mailbox on the passive copy server and pop3 logins fail with the error "-ERR Login Failure. Unknown Username or password"
Help much appreciated.
I have an issue with pop3 logins in an Exchange 2010 DAG environment. WE have two servers holding the Mailbox Server role and one holding the CAS and Hub Transport roles. The passive Mailbox server is in another site, there is no firewall in between.
Everything works fine when mailboxes are on the active mailbox database but were failing recently. Upon logging into the Exchange Management Console we noticed that the Exchange server had failed over to the copy mailbox server. Once we moved the active copy back the the original server pop3 logins worked again.
To test I have created a single instance database and mailbox on the passive copy server and pop3 logins fail with the error "-ERR Login Failure. Unknown Username or password"
Help much appreciated.
Do we have a GC on the other site ?
Ideally its said that any Active site should have the CAS for login
Also ensure if from the Second site you can telnet with port for POP3 to the CAS server
- Rancy
Ideally its said that any Active site should have the CAS for login
Also ensure if from the Second site you can telnet with port for POP3 to the CAS server
- Rancy
ASKER
Thanks for the responses.
I can telnet to the cas server on port 110 from the secondary site and get the banner
+OK The Microsoft Exchange POP3 service is ready.
Webmail still works.
The mailbox and cas server are in different subnets.
There is a GC in both sites.
I can telnet to the cas server on port 110 from the secondary site and get the banner
+OK The Microsoft Exchange POP3 service is ready.
Webmail still works.
The mailbox and cas server are in different subnets.
There is a GC in both sites.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
They are in different AD sites. Is this a requirement for pop3? Normal mapi email works ok for the mailbox on the secondary site.
Yes. "every site with a Exchange server with mailbox server role installed needs a CAS, period."
Check this link:
http://www.petri.co.il/forums/showthread.php?t=44521
Check this link:
http://www.petri.co.il/forums/showthread.php?t=44521
ASKER
Many thanks, installing a local CAS box fixed the issue.
I do not understand the complaint from Rancy.
My post 38750996 is the first post to question there being a second AD site, and to state the requirement for a CAS server.
The post from Rancy included two questions that were not relevant to the issue, however "Ideally its said" is not stating a requirement.
I would suggest 3) keeping the answer as is.
My post 38750996 is the first post to question there being a second AD site, and to state the requirement for a CAS server.
The post from Rancy included two questions that were not relevant to the issue, however "Ideally its said" is not stating a requirement.
I would suggest 3) keeping the answer as is.
ID: 38750486
Ideally its said that any Active site should have the CAS for login
- Rancy
Ideally its said that any Active site should have the CAS for login
- Rancy
@Rancy
The part you have highlighted does not say Active Directory, I do not disagree that it could be implied, but from the original post it was just physical sites that had been mentioned.
You said Ideally this would indicate a "nice to have" rather than a "must have" which is the case.
The part you have highlighted does not say Active Directory, I do not disagree that it could be implied, but from the original post it was just physical sites that had been mentioned.
You said Ideally this would indicate a "nice to have" rather than a "must have" which is the case.
Did OWA continue to work ?