CarmeldanIT
asked on
Sending from Exchange 2003
We have been wrestling with a move of MS Exchange to another server. Because of many glitches it has been decided to move it back, but having done that, the email is failing to send from any workstation.
Is there a check list of things that might need setting?
I can Telnet out from the server and the internet is connecting fine. We have not had any incoming emails either, so maybe both have been affected, I've just been concentrating on the outgoing.
Thanks for your help
Is there a check list of things that might need setting?
I can Telnet out from the server and the internet is connecting fine. We have not had any incoming emails either, so maybe both have been affected, I've just been concentrating on the outgoing.
Thanks for your help
We have been wrestling with a move of MS Exchange to another server. Because of many glitches it has been decided to move it back, but having done that, the email is failing to send from any workstation.
Hi CarmeldanIT,
What process were you using to move the mail? Was it a new server? Were you P2V it into a virtual environment? Were you upgrading to a newer version of Exchange? Need more info to adequately answer.
ASKER
Hi, Thanks for your replies.
We were trying to keep it simple!!!
The same version SBS 2003 was on both servers and planning to use the preconfigured server instead of re-installing because of software issues. The transfer method was using PST file backup on workstations and then restoring to the new Exchange server. This went though in both directions.
To keep the NAT settings on the router the same, we changed the IP addresses of the servers so the routing would happen without changing the router.
I have received two NDRs from the server to a couple of test emails I sent from my office PC, so the Exchange server can send, but appears not to be processing emails internally.
When trying to send from a user, the internal bounce back message says: -
'phil-smith@inet-synergy.c
message could not be sent. Try sending the message again later, or
contact your network administrator. Error is
[0x80004005-00000000-00000
It seems to refer to synchronisation issues, but I cannot see any way of dealing with this.
I have changed the profile on the workstation, but as all emails are affected for all workstations suspect the problem is at the server end.
We were trying to keep it simple!!!
The same version SBS 2003 was on both servers and planning to use the preconfigured server instead of re-installing because of software issues. The transfer method was using PST file backup on workstations and then restoring to the new Exchange server. This went though in both directions.
To keep the NAT settings on the router the same, we changed the IP addresses of the servers so the routing would happen without changing the router.
I have received two NDRs from the server to a couple of test emails I sent from my office PC, so the Exchange server can send, but appears not to be processing emails internally.
When trying to send from a user, the internal bounce back message says: -
'phil-smith@inet-synergy.c
message could not be sent. Try sending the message again later, or
contact your network administrator. Error is
[0x80004005-00000000-00000
It seems to refer to synchronisation issues, but I cannot see any way of dealing with this.
I have changed the profile on the workstation, but as all emails are affected for all workstations suspect the problem is at the server end.
The same version SBS 2003 was on both servers and planning to use the preconfigured server instead of re-installing because of software issues. The transfer method was using PST file backup on workstations and then restoring to the new Exchange server. This went though in both directions.
So you created a brand new forest and domain? Or, did you follow the article of moving SBS to new hardware and kept the existing domain and forest?
Migrating SBS 2003 to New Hardware.
http://technet.microsoft.com/en-us/library/cc747454(v=ws.10).aspx
ASKER
No we used the existing domain.
THe point now is to make the Exchange work on the server it was working on before. The reason for mentioning the other server was to explain what had happened.
We now want to make the email work on the old server as it was working, but for some reason Outlook and OWA users cannot access it. The send receive says it is completing the task but nothing is received and send items are bounced back to the user within seconds.
I am seeing events relating to Activesync and Bad pages, so wondering if this is the reason and whether I need to run a repair. The Isinteg option doesn't run successfully so looking for alternatives?
THe point now is to make the Exchange work on the server it was working on before. The reason for mentioning the other server was to explain what had happened.
We now want to make the email work on the old server as it was working, but for some reason Outlook and OWA users cannot access it. The send receive says it is completing the task but nothing is received and send items are bounced back to the user within seconds.
I am seeing events relating to Activesync and Bad pages, so wondering if this is the reason and whether I need to run a repair. The Isinteg option doesn't run successfully so looking for alternatives?
Can you confirm if all Exchange Services are started? Including the SMTP service and the WWW service?
When was the last time you rebooted the original server? Let's reboot it. Record Event Logs as soon as the server restarts. Likely the first few events post reboot are the key to all the failures.
What do you see when you try to browse to Outlook Web App from the server itself? (http://localhost/owa)
You mentioned you changed IPs. I assume the server name itself did not change? Sounds like no DNS changes were made externally as you made no firewall changes.
When was the last time you rebooted the original server? Let's reboot it. Record Event Logs as soon as the server restarts. Likely the first few events post reboot are the key to all the failures.
What do you see when you try to browse to Outlook Web App from the server itself? (http://localhost/owa)
You mentioned you changed IPs. I assume the server name itself did not change? Sounds like no DNS changes were made externally as you made no firewall changes.
ASKER
Hi Gareth,
All the Exchange services are started. There is no SMTP or www service in the services list. Is this in 2003 or just when you move to 2007 and later? When I load OWA (http://192.168.112.5/Exchange) I am able to log in and see the OWA pages, but cannot see new emails or send an email.
The server has been restarted about an hour ago, but I can restart it again.
No DNS changes were made externally. The server names were not changed.
The Event log is showing an error: -
Information Store (800) First Storage Group: A bad page link (error
-338) has been detected in a B-Tree (ObjectId: 68, PgnoRoot: 2333) of
database G:\ExchDB1\priv1.edb (17768530 => 17795137, 17795140).
Do you think this is the cause of the whole issue? Why it has suddenly happened is another question.
Suggested solution for this is to run the repair utility "isinteg" or restore from backup The backup was one of the reasons for change the server so that is not an option. Running isinteg is not working at present so we are getting deeper into the mire.
All the Exchange services are started. There is no SMTP or www service in the services list. Is this in 2003 or just when you move to 2007 and later? When I load OWA (http://192.168.112.5/Exchange) I am able to log in and see the OWA pages, but cannot see new emails or send an email.
The server has been restarted about an hour ago, but I can restart it again.
No DNS changes were made externally. The server names were not changed.
The Event log is showing an error: -
Information Store (800) First Storage Group: A bad page link (error
-338) has been detected in a B-Tree (ObjectId: 68, PgnoRoot: 2333) of
database G:\ExchDB1\priv1.edb (17768530 => 17795137, 17795140).
Do you think this is the cause of the whole issue? Why it has suddenly happened is another question.
Suggested solution for this is to run the repair utility "isinteg" or restore from backup The backup was one of the reasons for change the server so that is not an option. Running isinteg is not working at present so we are getting deeper into the mire.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
if you moved mail server "back", have you reconfigured firewall/ nat, so that email will bi directed to mail server?