@JasGot Yes. It populates even when I don't log into ecp. Just visiting /ecp seems to make /owa work.

@pirho99 Thanks. I’m not able to get as far as logging in, but I’ll still give this a read and check my current CU version.

So we have two exchange servers set up now, the newest being Exchange 2016.

I did my best to mimic all of the DNS entries of the previously configured Exchange 2013 server, but when I go to Exchange2016serv.contoso.com/owa to access the web app, it’s a white screen.

Here’s the funky part: when you instead type in Exchang2016serv.contoso.com/ecp, you get the ecp like you are supposed to, but If you THEN change it to /owa, it works!

Of note: there seems to be a longer than usual redirect url at this point though.

I check IIS>Bindings to double check certs for default and exchange backend, but everything looks fine. I feel like this is DNS issue, but haven’t been able to pinpoint exactly what. Any ideas?

@Dashrender Yea, it worked.

@jt1001001 currently using a single NIC, but I think I got it. I’ll know tomorrow when I’m at work and can physically work with the xerox machines. Appreciate the reply.

Eh, I figured it out.

Had to select FrontEnd Transport, and leave the all available IP instead of changing it to the EXCHANGESERV NIC.

Trying to setup scan to email on some new xerox machines we got.

Got everything working right, but it won't send to outside email addresses such as gmail.

Did a little research and found that I need to setup a new receive connector to allow this.

So I try making one with like so:

• Name: Scan2email
• Server: EXCHANGESERV.contoso.com
• Role: Hub Transport
• Type: Custom
• Network Adapter Bindings: IP of EXCHANGESERV NIC
• Port: 25
• Remote Network Settings: IP of Xerox Machine on network

I get the error message:
"The Values that you specified for the Bindings and RemoteIPRanges parameters conflict with the settings on Receive connector "EXCHANGESERV\Default Frontend EXCHANGESERV". Receive connectors assigned to different Transport roles on a single server must listen on unique local IP address & port bindings."

So is it saying that I need to use a different port for each connector?

The "Default Frontend EXCHANGESERV" receive connector is inclusive of all IP ranges, as it was set that way from the guy we paid to do it. I'm wondering how to move forward.

Given that the problem exists over a span of time with multiple machines I'd have a look at whatever she's been plugging into each of these machines. Thumb-drives, externals, etc. Forgive me if this has already been mentioned, skimmed over the thread a bit and didn't see it.

I also agree that moving rooms might be a good option, or at least running power from another one.

Did you check her work laptop out? Maybe she's passing files back and forth via RDP...

Anyway, sounds crazy, hope you get it figured out. Please let us know as I'm super interested.

@Obsolesce Good point. Never really thought of it that way.

@Obsolesce Please elaborate. What was it that turned you away?