Managing Active Directory does not always have to be complicated. If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why
Solved
mailrouting from scanners to internal and external
Posted on 2014-01-10
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???
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
-
8
5
14 Comments
Active 1 day ago
You shouldn't be pointing the scanners to your MBX servers though, they should be pointing to your CAS array.
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.
Active 5 days ago
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.
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
Active 5 days ago
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.
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.
Active 5 days ago
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.
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.
Active 5 days ago
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.
Active 5 days ago
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.
Featured Post
Blockchain is a technology that underpins the success of Bitcoin and other digital currencies, but it has uses far beyond finance. Learn how blockchain works and why it is proving disruptive to other areas of IT.
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
New style of hardware planning for Microsoft Exchange server.
Are you an Exchange administrator employed with an organization? And, have you encountered a corrupt Exchange database due to which you are not able to open its EDB file. This article will explain all the steps to repair corrupt Exchange database.
The viewer will learn how to use the =DISCRINV command to create a discrete random variable, use this command to model a set of probabilities and outcomes in a Monte Carlo simulation, and learn how to find the standard deviation of a set of probabil…
The viewer will learn how to create two correlated normally distributed random variables in Excel, use a normal distribution to simulate the return on different levels of investment in each of the two funds over a period of ten years, and, create a …
Suggested Courses
Course of the Month7 days, 10 hours left to enroll
715 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.