asked on i have problem with my exhcange 2013 when i open the queu i get WinRM service error and the email in outlook web app stayes in the draft and outlook anywhere in the exchange queu
i have problem with my exhcange 2013 when i open the queu i get WinRM service error and the email in outlook web app stayes in the draft and outlook anywhere in the exchange queu
Email ServersServer SoftwareMicrosoft Server OS
Last Comment
mohammed-khalaf
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
ASKER
i have this error in the queu
Try restarting the exchange mailbox submission service. If that doesn't do anything you could try running a test-servicehealth from the EMS which may indicate any potential problems.
ASKER
ASKER
and one more thing ,,, we have change the public IP address and the internal IP address from class C to A i dont know if this caused the problem
ASKER
ASKER
ASKER
my ram consumption is 90% dose this stops exchange submission process??
High RAM consumption is a common occurrence on Exchange and 90% is typical - Exchange uses as much RAM as possible and releases it as and when applications require it (or that's the theory anyway).
I suspect changing the IP/Subnet may have caused the issues you are experiencing (especially if this was done after exchange was installed) as many of the settings in Exchange are setup on the original IP/network structure. If you can't change the network back then it may be possible to manually go through every setting in Exchange (pay close attention to DC settings, DNS, connectors, etc) and change them accordingly but it may be easier to backup the database and do a reinstall.
I suspect changing the IP/Subnet may have caused the issues you are experiencing (especially if this was done after exchange was installed) as many of the settings in Exchange are setup on the original IP/network structure. If you can't change the network back then it may be possible to manually go through every setting in Exchange (pay close attention to DC settings, DNS, connectors, etc) and change them accordingly but it may be easier to backup the database and do a reinstall.
ASKER
( 441 4.4.1 Error encountered with primary target IP ) i got this error in the Queu
Sounds like it may be dns related - I would check the server dns settings and run tests to ensure that is working correctly.
ASKER
ASKER
my dns is resolving ip Names properly simple and recursive query is working
Going on the error one possibility could be faulty send connector. Try removing and re-creating the send connector then see if the problem persists.
ASKER
i did already
ASKER
is there a proper steps to change the Internal ip address for exchange 2013 ???
ASKER
i returned the old ip adress and it worked properly and immediately
That has certainly shown the IP address change caused the problem.
I'm not sure on steps myself as never had to change the IP address of a working exchange server.
The main areas I'm aware of to look for that will/may reference IP addresses are:
DNS settings (both on exchange and the network's dns records themselves, Receive Connectors, Send Connectors, Domain Controller details. Ensure that any firewall rules for exchange are changed as well (both incoming and outgoing).
I'm not sure on steps myself as never had to change the IP address of a working exchange server.
The main areas I'm aware of to look for that will/may reference IP addresses are:
DNS settings (both on exchange and the network's dns records themselves, Receive Connectors, Send Connectors, Domain Controller details. Ensure that any firewall rules for exchange are changed as well (both incoming and outgoing).
ASKER
thanks