Exchange 2016 on-prem.
Migration started in EAC still showing active half hour later. It's a large mailbox so I expect this.
Get-MoveRequest is not showing ANYTHING:
UPDATE:
This request failed because this mailbox was moved a few days ago and the request was deleted after completion in the GUI but apparently it wasn't really deleted because it still conflicts with this new move.
I've been having very intermittent issues with Outlook and have not been able to find a solution. Being so intermittent, it's difficult to troubleshoot since it goes up and down frequently on its own, I can't determine if any changes make a difference. Problem occurring on multiple computers and multiple AD accounts / mailboxes but NOT all of them, some work fine.
Outlook "Trying to connect" or "Disconnected" | Send/Receive Error: 0x80040115
I found and tried some generic suggestions that made no difference:
Problems will last a few minutes or hours then everything works fine for a bit before it returns to the same problem a few minutes or hours later. While it's unable to connect, OWA works just fine, so it's not a server down or ISP problem on either side.
I found some similar reports but Office 365 related so those solutions do not apply to my on-site Exchange 2016.
Error sometimes appears only when sending, other times when receiving.
Log requested below: https://drive.google.com/file/d/1u6Caav_ukzq9cK5ju_IHBHG8RMYXxQzY/view?usp=sharing
Screenshots: https://drive.google.com/drive/folders/1pd7qO1hVkQXz_axeNlX8WKoRhLuIlHy0?usp=sharing
I have ONE account that is not syncing on mobile devices, either Android or iPhone. Other accounts work fine on both devices. So by process of elimination, it is apparent that it's the specific account, not the app or the phones. Desktop OWA works just fine for this user. Server is onsite Exchange 2016. Mobile Outlook works for everyone else. Normally it doesn't throw any errors, just has empty inbox as if it was a brand new mailbox. Even when sending, it silently goes into the Sent folder but doesn't actually send.
A few days ago while troubleshooting, this error popped up: https://photos.app.goo.gl/m7UHbfMRsSkPWALi8
I tried to search for it but Google returns very limited results and they reference Office 365 login issues, which does not apply to me.
On the same phones where Outlook doesn't work for this user, a third party app Spark works just fine, sending and receiving.
If I don't find an easier way, I will recreate the account and mailbox, but that is a nuclear option I'm trying to avoid.
I followed the instructions I saw on a dozen pages. Installed [IP Address and Domain Restrictions], edited unspecified clients to Deny, added a single internal IP allow, iisreset. Yet I'm able to reach EAC from outside.
Same instructions on a dozen pages but here is a couple for reference:
I had a functioning Exchange 2016 server. Migration between databases was all fine. I installed another Exchange 2016 to replace the old one. Install went fine, all mailboxes were moved but I had to do it from powershell because the UI was throwing up error about System Attendant mailbox being inaccessible. After the migration was done and mail flow is functioning, I want to resolve this issue to prevent future problems. After reading forums and articles online, I noticed that "Microsoft Exchange System Attendant" service is not there at all, on either server. I don't know if it was there before but I experienced no issues with the old server. But the SA service is not there on either server now. I am stumped and can't find anything online about this. I only noticed it was missing after I changed the System Attendant HomeDB attribute in ADSI Edit and wanting to restart the service to make the change effective.
I have a 20 Mbps symmetrical pipe. Upload speed to AWS S3 tops out at 2.3 Mbps. Tried the multipart upload but even with 10 concurrent threads, the total speed remains the same, just gets split between all threads ~20 KB/s.
Immediately after login into EAC/ECP I'm presented with 503 error. However, simply refreshing the page brings up EAC as expected and it works fine after that. Until I log out and attempt to log in again after a while, the story repeats itself.
Even ID 1003 from MSExchange Front End HTTP Proxy and 1309 from ASP.NET 4
I tried using both the self-gen and a CA issued cert on the back-end site, makes no difference. Just did that to cover bases others were on but I didn't think this would be it since it's such a temporary issue, simply refreshing the page brings it up, which a cert problem would not present.
Similarly, opening the EMS on the server initially throws up pages of red errors but when closed and opened again, it start fine.
So something seems to be pausing/stopping and needs a few seconds to start back up.
I've had Exchange 2010 for a long time. Got a new Exchange 2016 server recently and have a working coexistence as I'm learning the new version. One thing I've had trouble understanding, as many people have and there are tons of articles out there, is the receive connectors. On 2010, I had multiple connectors. For example, a connector on port 25 for external SMTP servers, a separate connector on port 25 for internal SMTP machines, and yet another separate connector on port 25 for internal Exchange servers. All of these connectors are for different purposes and are configured differently with incoming IPs and authentication methods. I tried doing something like this on the 2016 server and ran into issues. It appears that only one connector can exist for port 25. Whether it's for external SMTP or internal SMTP, or internal Exchange servers. All has to be combined into ONE connector?
Cisco ASA 5510 running Version 8.0(5) Two routers on separate ports. One works as it should, the other is being finnicky for a completely unknown reason.
ping PORT1 8.8.8.8
Sending 5, 100-byte ICMP Echos to 8.8.8.8, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 10/10/10 ms
ping PORT2 8.8.8.8
Sending 5, 100-byte ICMP Echos to 8.8.8.8, timeout is 2 seconds:
??!!! / ?!!!? / !!!??
Success rate is 60 percent (3/5), round-trip min/avg/max = 20/30/50 ms
It’s always 3/5 but different patterns as shown above. So I figure one of two things could be happening. Either the router behind PORT2 is bad or the cable is bad. So I hooked up a laptop using the same cable and gave it the same IP. It works just fine. No drops, latencies, or anything else.
Could it possibly be the actual port on the ASA? Should I try a different port? Haven’t tried that yet because I find that unlikely. Or could it be the config? Not sure what config sections to post, so please let me know. Both ports are configured exactly the same and I’m not aware of a config that would only let 3 out of 5 packets through. The MTU is the same on both at 1500.
I have a working config but just acquired a secondary (backup/redundant) ISP so I have to configure it. I found the article that describes doing that, including tracking and SLA: http://www.cisco.com/c/en/us/support/docs/security/asa-5500-x-series-next-generation-firewalls/118962-configure-asa-00.html
The problem I'm having is that this is a very basic config whereas I have dynamic and static NAT, numerous internal interfaces (inside, dmz, voip) that each get a different public IP to be NAT-ed to. I have several "global" commands like this:
global (outside) 1 100.200.300.401
global (outside) 2 100.200.300.402
global (outside) 3 100.200.300.403
Along with matching NAT:
nat (inside) 1 0.0.0.0 0.0.0.0
nat (dmz) 2 0.0.0.0 0.0.0.0
nat (voip) 3 0.0.0.0 0.0.0.0
And that's just dynamic. I also have a number of static (inside,outside) for various servers.
It seems that with the redundant ISPs, the "global" command is no longer and is somehow substituted with object network? This is new to me and I never used it before. It seems a bit tricky. Do I have to assign subnet to the objects to match the networks the interfaces are assigned?
Anyway, I know this is complex so even just a pointing to a page showing examples would help. I can't really expect detailed configs here, I know this.
Running guest Windows Server 2012 R2 with Exchange 2016 in an ESXi 6.0 host. The issue I'm experiencing is a long time it takes for the server to start responding after each reboot. The guest will reboot, come up, allow me to log in and interact with it. However, it will takes several minutes (~10) past that before the server starts responding to external clients, even an RDP login. The built-in soft firewall is disabled on the domain network since I have a hardware firewall at the gateway.
When I log into the console right after a reboot but before the server is responsive on the network, any network-relate features such as the "Network and Sharing Center" or "Windows Firewall" don't come up. Blank windows just sit there for a few minutes in a "loading" phase and then they come up simultaneously to the server becoming responsive on the network.
I have another 2012 Server on the SAME esxi host and that one works fine! It's just this one with Exchange on it.
Guest: 2 x QuadCore Intel Xeons 2.266GHz / 32 GB RAM / 500 GB Storage
Adding results of Jetstress here as opposed to "comment" since those cannot be formatted, even with newlines:
Test Summary
Overall Test Result Pass
Total I/O Performance
I/O Database Reads/sec ~ 40.011
I/O Database Writes/sec ~ 21.361
I/O Database Reads Average Bytes ~ 84678.508
I/O Database Writes Average Bytes ~ 36612.187
I/O Log Reads/sec ~ 0.047
I/O Log Writes/sec ~ 5.632
I/O Log Reads Average Bytes ~ 2893.820
I/O Log Writes Average Bytes ~ 11454.790
There is a problem with the proxy server's security certificate.
The name on the security certificate is invalid or does not match the name of the target site mail.mydomain.com.
Outlook is unable to connect to the proxy server. (Error Code 0)
This just started happening this morning out of the blue but only to ONE user. Everyone else is fine. I tried this problematic user on different computers, same thing. The user can get into OWA just fine, it's only Outlook being problematic. And again, the biggest thing is that it only affects ONE user. I found a bunch of generic solutions about actual certificate issues but none of that applies.
I have a problem with filtering on my Exchange 2010 server. This used to work fine but I am aware of no changes that would make it stop. But it did. It accepts everything now. Blocking messages addressed to "non-existent" addresses does not work. In troubleshooting this, I even specified an address to block but it's not getting blocked.
SETTINGS
(Powershell commands taken from: https://technet.microsoft.com/en-us/library/bb125187.aspx)
Get-RecipientFilterConfig | Format-List Enabled
Enabled : True
Get-RecipientFilterConfig | Format-List ExternalMailEnabled
ExternalMailEnabled : True
Get-RecipientFilterConfig | Format-List InternalMailEnabled
InternalMailEnabled : True
Get-RecipientFilterConfig | Format-List BlockListEnabled
BlockListEnabled : True
Get-RecipientFilterConfig | Format-List BlockedRecipients
BlockedRecipients : {[email protected]}
Get-RecipientFilterConfig | Format-List RecipientValidationEnabled
RecipientValidationEnabled : True
TELNET RESULTS
220 EXCH1 Microsoft ESMTP MAIL Service ready at Tue, 31 Jan 2017 12:13:31 -08
00
helo test1
250 EXCH1 Hello [192.168.30.107]
mail from: [email protected]
250 2.1.0 Sender OK
rcpt to: [email protected]
250 2.1.5 Recipient OK
data
354 Start mail input; end with <CRLF>.<CRLF>
text
.
250 2.6.0 <[email protected]> [InternalId=342753] Queued mail for delivery
What am I missing or not checking?
I followed this guide verbatim:
http://www.postfix.org/STANDARD_CONFIGURATION_README.html#firewall
However, it results in local mail to root going to [email protected].
If I change that line in /etc/postfix/virtual to: root [email protected]
then it gets to me, so problem solved?
The problem is that anyone from outside can also send to root and it gets to me. I've been trying to figure out how to have locally posted mail to root go to [email protected] while preventing outside connections from doing so.
I've always used the ifcfg-eth0:1 alias files to create additional addresses. However, in recent rhel documentation, it states that:
As the ip command of the iproute package now supports assigning multiple address to the same interface it is no longer necessary to use this method of binding multiple addresses to the same interface.
Furthermore, numerous answers and comments on this site mention that ifconfig is deprecated and that "ip" should be used instead. I'm fine using it for live changes, but how do I persist the changes across reboots without using the alias files?
Getting the following in /var/log/messages:
Sep 17 10:38:53 server1 kernel: end_request: I/O error, dev sde, sector 0
Sep 17 10:38:53 server1 kernel: end_request: I/O error, dev sde, sector 63
Sep 17 10:38:53 server1 kernel: end_request: I/O error, dev sde, sector 208845
In addition, any time an lvm utility runs, before the results are returned (properly), the following is shown:
/dev/sde: read failed after 0 of 4096 at 0: Input/output error
/dev/sde1: read failed after 0 of 2048 at 0: Input/output error
/dev/sde2: read failed after 0 of 2048 at 0: Input/output error
fdisk -l does not show such a device and returns no errors. Also nothing in mount or fstab. I can't find anything about this device, other than its listing in /dev and the errors show above. This is a live server, I would rather not have to resort to a reboot if it can be avoided.
CentOS 5.5 , LSI hardware SAS RAID , dual quad-core Xeon, 16GB RAM
When I run a read-only fsck on the mounted root partition of a CentOS 5 server, it finds a number of errors. However, running a forced check upon next boot does not find any!
Here are the results of the mounted read-only check:
# fsck -nCf /
fsck 1.39 (29-May-2006)
e2fsck 1.39 (29-May-2006)
Warning! /dev/sda3 is mounted.
Warning: skipping journal recovery because doing a read-only filesystem check.
Pass 1: Checking inodes, blocks, and sizes
Deleted inode 232259589 has zero dtime. Fix? no
Inodes that were part of a corrupted orphan linked list found. Fix? no
Inode 232259593 was part of the orphaned inode list. IGNORED.
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences: -32194676 -(32235995--32235998) -(32236209--32236210) -(32238978--32238981) -(32239590--32239593) -(32239924--32239926) -(32241448--32241457) -(32245306--32245313) -32867401 -(36754088--36754097) +(143647672--143648620) -(143653816--143654764)
Fix? no
Free blocks count wrong for group #982 (1277, counted=1276).
Fix? no
Free blocks count wrong for group #983 (810, counted=777).
Fix? no
Free blocks count wrong for group #984 (19647, counted=19637).
Fix? no
Free blocks count wrong for group #1003 (28042, counted=28041).
Fix? no
Free blocks count wrong for group #1121 (11611, counted=11598).
Fix? no
Free blocks count wrong (227428348, counted=227427933).
Fix? no
Inode bitmap differences: -232259589 -232259593
Fix? no
Free inodes count wrong (243391778, counted=243391739).
Fix? no
/: ********** WARNING: Filesystem still has errors **********
/: 205534/243597312 files (3.7% non-contiguous), 16161230/243589578 blocks
The way I run a forced check is by:
touch /forcefsck
echo -n "-y" > /fsckoptions
This does force fsck to run upon next boot and the "-y" option should autofix all errors, but the check doesn't find any during bootup. However, once the file system is mounted and I run the read-only check again, it finds all the same errors.
Thanks for your time,
PRL