Configure POP3 server in Exchange 2003
We have 2 fron-end servers (Exchange 2003 SP2) in NLB cluster and 2 back-end servers (Exchange 2003 SP2) in Windows cluster. We are not able to configure
POP3 service in this environment. Is there a secret? Could you pls describe the procedure to compare what we're doing wrong?
POP3 service in this environment. Is there a secret? Could you pls describe the procedure to compare what we're doing wrong?
itcoza
You have checked that the service has been set to Start Automatically in your services MMC?
ASKER
Yes, sure ...
Can you provide a bit more information regarding the IP layot, Services plan and also any other relevent information we can use to help you?
ASKER
The configuration is as follows (for example):
front-end server: exfe1
IP1=192.168.100.24 (internal LAN)
IP2=192.168.100.22 (with Networl Load Balancing configured)
front-end server: exfe2
IP1=192.168.100.25 (internal LAN)
IP2=192.168.100.23 (with Networl Load Balancing configured)
NLB Cluster IP = 192.168.10.26
back-end server: exbe1 (passive role in windows cluster)
IP1=192.168.100.15
IP2=192.168.3.15
back-end server: exbe2 (active role in windows cluster)
IP1=192.168.100.16
IP2=192.168.3.16
Windows Cluster IP Address = 192.168.100.17
Cluster name = cluster
Virtual Exchange Server IP Address = 192.168.100.19
Virtual server name = EXSVR
Our actions are the following:
on exfe1,exfe2, exbe1, exbe2 Microsoft Exchange POP3 service has been set up to 'start automatically'.
on exbe2 (active) in windows cluster administrator there has been created a POP3 virtual server as a resource to Exchange Virtual Server (EXSVR) with appropriate instance and dependance.
Then we are bringing online this resource and windows cluster starts transferring all the virtual resources from one physical server to antother due to impossibility to start POP3 vurtual instance.
front-end server: exfe1
IP1=192.168.100.24 (internal LAN)
IP2=192.168.100.22 (with Networl Load Balancing configured)
front-end server: exfe2
IP1=192.168.100.25 (internal LAN)
IP2=192.168.100.23 (with Networl Load Balancing configured)
NLB Cluster IP = 192.168.10.26
back-end server: exbe1 (passive role in windows cluster)
IP1=192.168.100.15
IP2=192.168.3.15
back-end server: exbe2 (active role in windows cluster)
IP1=192.168.100.16
IP2=192.168.3.16
Windows Cluster IP Address = 192.168.100.17
Cluster name = cluster
Virtual Exchange Server IP Address = 192.168.100.19
Virtual server name = EXSVR
Our actions are the following:
on exfe1,exfe2, exbe1, exbe2 Microsoft Exchange POP3 service has been set up to 'start automatically'.
on exbe2 (active) in windows cluster administrator there has been created a POP3 virtual server as a resource to Exchange Virtual Server (EXSVR) with appropriate instance and dependance.
Then we are bringing online this resource and windows cluster starts transferring all the virtual resources from one physical server to antother due to impossibility to start POP3 vurtual instance.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hi,
Thanks I have already read all of these articles. Let's assume the ticket is closed.
Thanks I have already read all of these articles. Let's assume the ticket is closed.