jgutierr76
asked on
mailrouting from scanners to internal and external
Need a bit of assistance as MS is running me in circles. Were in the middle of Exch 2013 Migration.
We have a bunch of In-house copiers/Scanners. Our users scan info to users inside the firm
and to outside clients.
All roles are separated 2 x Cas Servers in NLB and two backend MBX/HUB in a DAG.
When I point all scanners to either MBX all is well they can scan to internal and external email addresses.
When I point all scanners to the NLB on the Cas boxes only Internal scanning works, scanning to external is dead.
I would like some redundancy, if MBX that the scanners are pointing to goes down Dag will kick off DB to 2nd box but then all scanners will be offline. MS has already told me that NO NLB on the DAG boxes so I said ok NP. What is the solution here am I just stuck pointing them to one MBX Server have everything work but no redundancy. There must be something that can be done???
We have a bunch of In-house copiers/Scanners. Our users scan info to users inside the firm
and to outside clients.
All roles are separated 2 x Cas Servers in NLB and two backend MBX/HUB in a DAG.
When I point all scanners to either MBX all is well they can scan to internal and external email addresses.
When I point all scanners to the NLB on the Cas boxes only Internal scanning works, scanning to external is dead.
I would like some redundancy, if MBX that the scanners are pointing to goes down Dag will kick off DB to 2nd box but then all scanners will be offline. MS has already told me that NO NLB on the DAG boxes so I said ok NP. What is the solution here am I just stuck pointing them to one MBX Server have everything work but no redundancy. There must be something that can be done???
Alex
You shouldn't be pointing the scanners to your MBX servers though, they should be pointing to your CAS array.
ASKER
Exchange 2013 doesn't have a cas array.
ASKER
When I point Scanners to NLB on CAS only internal scanning works, so what am I missing that wont allow CAS to send the scanned PDF to external email address?
ALL hub rules are on the MBX/HUB servers.
ALL hub rules are on the MBX/HUB servers.
You say NLB, are you talking about the trash that is Windows Network Load Balancing?
You need to enable logging on the receive connectors so you can see how Exchange is seeing the traffic. It could be that Exchange doesn't see the traffic correctly so doesn't allow relaying. Internal recipients aren't relaying,
Simon.
You need to enable logging on the receive connectors so you can see how Exchange is seeing the traffic. It could be that Exchange doesn't see the traffic correctly so doesn't allow relaying. Internal recipients aren't relaying,
Simon.
ASKER
So MS Suggested that I create a Connector on both CAS if pointing scanner to the NLB nIC which I did. I set logs to verbose and they show nothing from scanners but I was also running a wireshark and saw the traffic so it is getting there. see pic.
Scanner-external.jpg
Scanner-external.jpg
WNLB is a piece of junk, therefore the first thing you should do is bypass it. Attempt to send email directly to one of the server. If that works then it is WNLB that is the cause of the problem.
Simon.
Simon.
ASKER
Same deal I pointed to one of the NICs not in the NLB and I still only send internal.
Ms is looking into it but I think I need next level support at this point.
Ms is looking into it but I think I need next level support at this point.
I would start by removing WNLB then - that causes nothing but hassle and isn't recommended by the Exchange product team for use with Exchange.
Simon.
Simon.
ASKER
@ Simon do you have a link where I can read that.
ASKER
This is direct from the official Course material from MS that I took to prep for this Migration. SO why would they say Yay to NLB if they don't recommend...
Look at the last bullet point.
Options for Client Access Server Deployment
The Client Access server role performs a critical function in your Exchange Server
organization. The following options are available when you deploy the Client Access
server role:
• You can deploy the Client Access server role on the same computer where the
Mailbox server role resides. Installing all server roles on a single server does not
provide additional availability, and offers only limited scalability.
• You can deploy the Client Access server role on a dedicated server. This
deployment provides additional scalability and performance benefits.
• You can deploy multiple servers running the Client Access server role. To provide
high availability for Client Access servers, you can deploy Windows Network Load
Balancing (NLB) or a hardware network load balancer to manage connections to
the Client Access servers.
Look at the last bullet point.
Options for Client Access Server Deployment
The Client Access server role performs a critical function in your Exchange Server
organization. The following options are available when you deploy the Client Access
server role:
• You can deploy the Client Access server role on the same computer where the
Mailbox server role resides. Installing all server roles on a single server does not
provide additional availability, and offers only limited scalability.
• You can deploy the Client Access server role on a dedicated server. This
deployment provides additional scalability and performance benefits.
• You can deploy multiple servers running the Client Access server role. To provide
high availability for Client Access servers, you can deploy Windows Network Load
Balancing (NLB) or a hardware network load balancer to manage connections to
the Client Access servers.
The advice did change. Read this blog posting by fellow Exchange MVP Steve Goodman.
http://www.stevieg.org/2010/11/exchange-team-no-longer-recommend-windows-nlb-for-client-access-server-load-balancing/
The training material is often written at RTM and then not touched again except for new features, so errors are not unusual.
Simon.
http://www.stevieg.org/2010/11/exchange-team-no-longer-recommend-windows-nlb-for-client-access-server-load-balancing/
The training material is often written at RTM and then not touched again except for new features, so errors are not unusual.
Simon.
Even so, when WNLB is involved and there are problems with something it is involved in, the first thing to try is to remove WNLB because it is very troublesome. Otherwise you have too many variables.
Simon.
Simon.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Setting anonymous login on the connector via Shell fixed it, which is confusing as I set this on the connector via GUI.