Exchange 2003 sending out high https traffic to Blackberry servers

We have 10-15 Blackberry users setup with BIS, using OWA to send/receive work emails.
I see large amounts of https traffic being sent out from the Exchange server to Blackberry servers, (35-40 GB during the past month), these 10-15 users would not receive that much email or send that much in a month
Are there any known issues or workarounds for this type of issue?

Similar Messages

Exchange 2010 - Send Connector High Availability

Hi All,
I performed a successful migration a few years back from a single node Exchange 2003 server to a two node Exchange 2010 organisation with a DAG and Kemp load balanced CAS array. The solution works well and when we simulate a site failure
I am able to get the second node to handle all mail functions.
The one problem I have though is that I have to manually disable the send connector on the primary server in order for the one on the secondary server to be in use. I should explain that I have two send connectors as I do not want the secondary server
to be used unless the primary server is down or the route is unavailable. I realise that Exchange 2010 does not know whether the SMTP route is down or not so will just continue trying to use the send connector from the primary server (until I tell it
not to by disabling it).
My question is how do I get this to happen automatically? Does anyone else have an example of how this could be done or use a PowerShell script to achieve this? I guess a script could check the route and disable the send connector on the primary
server if necessary, but how would one do this?
Any help greatly appreciated.
Rob

Hi,
According to your description, your secondary send connector cannot be automatically used when the first one is down. If I misunderstand your meaning, please feel free to let me know.
If yes, I’d like to confirm if the settings of the secondary one is same with the first one and we can check the connectivity logs including diagnostic information for Healthy Server Selector.
For more information, you can refer to the following article:
http://technet.microsoft.com/en-us/library/ff634392(v=exchg.141).aspx
Thanks,
Angela Shi
TechNet Community Support

How to force J2ME to send out HTTP 1.0 request

How does one force a J2ME client to send out an HTTP 1.0 request instead of an HTTP 1.1 request ?
I'd like to do this because handling 100-Continue return codes is becoming quite a chore. If the request is from a 1.0 client, the server won't send the 100-continue.
Thanks
BigAl

Hi,
From tool kit WTK2.0 you can do this by setting the preferences.
Click Edit>preferece
In Network Configuration tab you can select Http/1.0
But on real device it is implementation dependent.You can'nt choose the HTTP1.0 or HTTP1.1.
If the underlaying is a WAP stack which provides HTTP1.1 functionality then there is no way you can switch to HTTP1.0
Doesn't have idea about other bearers imode/sms etc etc
HTH
phani

My MBP has started to send out TCP packets larger than the MTU on the NIC - is there any place that this can be overriden?

Got a very weird issue here and wondering if anyone has any other ideas. Basically over the wired NIC only, my Mac has started to send out large HTTP/HTTPS packets from the browser (> 1500 bytes) Captures show packet sizes from 2000 all the way to 4000 sometimes. This happens in Firefox and Chrome so doesn't appear to be application related.
This causes fragmentation issues and traffic drops which basically causes most of my websites and tools to crash and burn (and I get all sorts of SSL errors from applications, etc).
It appears to be limited to just TCP packets as pings with the DF bit set will not send any larger than 1500 bytes.
However if I switch to wireless, everything works fine and captures show the correct maximum packet size of 1500 for all packets leaving my client.
The MTU on the en0 interface is 1500 as per ifconfig and I made sure that it was set to 1500 in Network config panel (because there is an option for jumbo frames there which bumps up the MTU).
A packet capture also shows that during the three way handshake the TCP MSS is successfully sent and negotiated as 1480, but then it appears to ignore that when sending packets later in the TCP stream.
I've rebooted, upgraded to 10.7.4, checked the "sysctl" outputs and matched against a Mac not having the issue.
This is the newest MBP 15 inch model.
Any other ideas on things to check?

Have you used any sort of "tuner" software? You are obviously an advanced user. Sometimes we hack things up and forget about it later. If you are sure you didn't do that, maybe poke around with IPv6 settings. Supposedly people are trying to enable that and it is going to be a disaster.

Relay issue from Unix across Exchange 2003 OWA server in Exchange 2010 environment

Hi,
I'm trying to resolve an issue. We have one Exchange 2003 server left in our environment. The rest is now Exchange 2010. We are working to decommission this server. Monitoring the SMTP logs, I am working with the various groups to get the traffic
off this server and onto the Exchange 2010 environment.
The issue we are finding is with a work flow. This Java app for eBis sends email to users. This is done correctly through Exchange 2010 and gets delivered from our HUB/CAS servers to the target user mailbox. This email has several links the user must click
for approving or rejecting requests. Upon clicking Approve, a new email window opens (we use Outlook 2010). The TO address is in the format of [email protected] Upon clicking Send, our Exchange 2010 HUB/CAS servers accept the
email, because one of our send connectors has, as address space, *.domain.corp. However, the email address being used it not an alias on any Exchange 2010 mailbox, so it appears Exchange 2010 is sending this email on to the Exchange 2003 server, which
also is an SMTP server. I *think* this server is looking at the address after @ to determine where to send it (ebisserver.domain.corp, which is valid in our DNS), and sends it on to that server, where the java "listener" program intercepts
the mail, processes it and then saves it to a file somewhere.
We are at a loss as to how to get Exchange 2010 to do this instead of Exchange 2003... once this traffic is eliminted from Exchange 2003, I can proceed with decommission of this server. Any help troubleshooting this issue is appreciated.

The only reason the Exchange 2010 server would route outbound mail through an Exchange 2003 server is that you have an SMTP Connector defined on the Exchange 2003 server that has a more specific domain than you have on the Exchange 2010 server. You
should be able to see all your Send Connectors (an SMTP Connector on Exchange 2003 looks like a Send Connector in Exchange 2010) by running Get-SendConnector.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

What is the best way to get activesync to work on Exchange 2010 with co-existing Exchange 2003?

I currently have all my mailboxes on my Exchange 2003 server and I introduced my first Exchange 2010 server into the same environment so they are running co-existent. The mailflow is functioning properly so now I need to test out the activesync. From
what I've read, you have to create a SSL certificate with SAN on the Exchange 2010 server and create a legacy.domain.com name to point to the Exchange 2003 server. Then replace out the existing SSL certificate on the Exchange 2003 server with the
new one that was created for the Exchange 2010 server. However, my question is that if this does not work could I easily revert back to the original settings where Exchange 2003 server is doing the activesync instead of Exchange 2010? That way
I would not disrupt activesync from working.

The legacy url is not important for activesync, but:
Enable Integrated Windows authentication on the Microsoft-Server-ActiveSync virtual directory on the
Exchange 2003 back-end server
http://technet.microsoft.com/en-us/library/ee332348(EXCHG.140).aspx
once you point your external url for active sync at your 2010 it should proxy the 2003 active sync

Redirect / Block non https traffic

I have a quick question. Today I setup teaming 2.0 on SLES10.
After customizing the SuSE firewall per the instructions everything is perfect. I then cut off non-secure port 80 traffic. Looked OK. I found that the email that teaming sends out is http://server, since I killed http traffic it's now broken. I tried changing the firewall rule to FW_REDIRECT="0/0,10.0.100.100,tcp,80,8443 to see if it would just redirect the port 80 traffic to 8443 on the server - but that did not work. Is their a place I can simply change the email to link to https://server?
Any other thoughts?
Cool product by the way!
Tha
Dennis

Dennis,
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Visit http://support.novell.com and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)
Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.novell.com/faq.php
If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Product Support Forums Team
http://support.novell.com/forums/

Message looping between Exchange 2003 & Exchange 2010 after domain type changed to internal relay

Hi
We have a coexistence environment where we are currently migrating from Exchange 2003 to 2010 and have 80% of the users already on the Exchange 2010 platform. This is all within the same AD forest, let's call it FOREST1.AD.
The problem I'm seeking help about is a message routing problem we had this morning where messages bound for the Exchange 2003 users started looping between Exchange 2003 and Exchange 2010. The problem started as a result of changing the accepted domain
type to 'internal relay domain' for the purposes of establishing SMTP namespace sharing with an external Exchange environment (different forest, let's call it FOREST2.AD). The expectation was that after changing the domain type from authoritative to 'internal
relay domain', Exchange 2010 would route messages for unknown recipients to the external environment and that would be the only effect of the change. The message routing to the external environment worked completely OK. However, later we noticed that Exchange
2003 stopped delivering messages to its local users and started routing them to Exchange 2010 which would route the messages back to Exchange 2003 as that's where the recipients existed, only to have Exchange 2003 send them back to Exchange 2010 again.
The Send connector to route the messages, for the shared namespace, to the external environment used the Exchange 2010 server as the source server. It makes sense and is expected that Exchange 2003 would send messages for any unknown recipients to Exchange
2010 for onward delivery via the Send connector. But it is not expected for Exchange 2003 to not deliver messages to its own users using the store driver and instead routing them on to Exchange 2010.
We fixed the problem by reversing the change and not only changed the domain type back to authoritative but also removed the Send connector for the specified shared namespace. However, we do need to understand why this problem happened and how to stop it
from happening.
We did test the shared SMTP namespace configuration using a test domain before applying the change to the domain that is used for production email traffic. Test users on Exchange 2003 with email addresses on the test domain did not experience this looping
problem. This has been tested again after the production domain experienced the problem and there is no looping for the test domain. The only difference I noticed between the configuration for the test domain and the production domain is that while both domains
existed as accepted domains of type 'internal relay domain' in Exchange 2010, there was a difference in configuration in Exchange 2003 where the test domain was not present on the recipient policy at all and the production domain was present there.
This also makes me wonder if Exchange 2003 and Exchange 2010 in the same organization keep a separate configuration to determine which domain they are authoritative for. When you install Exchange 2010, it does add all the domains on the recipient policies
to the accepted domains configuration but any new domains you add in accepted domains in Exchange 2010 are not added to the legacy recipient policy object.
Can someone please help clarify these grey areas and explain why the message looping was created and how to avoid it. I'm happy to provide any further information.
Thanks
Nauman.

Hello,
Why do you want to use the 'internal relay domain' authentication?
Thanks,
Simon Wu
TechNet Community Support

Exchange 2003 SMTP resolves to incorrect MX record for Outbound emails

Starting October 2007, we have encountered numerous incidents where users complaint that they can not send emails to randomly with Relayed Denied error.
First we thought the problem is with the receipient servers, but after reviewing the SMTP log intensively, I have noticed that the SMTP service on Exchange Server 2003 SP2 tries to send out emails to wrong IP Addresses (instead of sending out to listed IP of MX record, it tries to send to primary domain IP address).
To test further, we have changed the DNS server of the Exchange Server to public DNS service provided by the ISPs and still received same result.
If the user tries to send the email again (from the bounced back message), it some times goes through.
Has anyone know what the problem is?
Have checked the server configuration, DNS configuration, ran all updates, and yet still same result. Is one of the Microsoft Updates causing this issue?

Here is the official explanation i got from MS, sounds like it is doing what they expect it to do.
Problem Description
When Exchange 2003 sends e-mail to the Internet using DNS to resolve external domain names a DNS query is done for the remote domain's MX records. In the event that the initial MX query returns a "server failure", Exchange 2003 will fall back to a DNS A record query. If this query is, in turn, successful and there is an A record for the domain in question that happens to be listening on port 25, Exchange will make a connection to that server. However, if this server does not relay, or accept e-mail for the intended domain a NDR will be generated with a 5.7.1, or
5.5.0 error message.
There are several domains that have A records that point to IP addresses that accept connections on port 25, but do not relay for the same name space:
Eg: Mindspring.com; Earthlink.net
Resolution
Resolve the DNS resolution problems that are causing occasional MX record failures.
Examples:
1. The Exchange server has multiple default gateways set on a multi-homed server.
This is not a recommended configuration and can cause a number of unexpected network problems. If the internal DNS server the internal NIC points to cannot resolve external DNS queries, this problem can occur.
Action: remove the default gateway from one of the NICs.
This doesn’t applies to us, as we don’t use Internal DNS
2. If the Exchange server points to multiple DNS servers on TCP/IP properties, or on the SMTP Virtual Server properties, verify that each of these DNS servers will return MX records properly. If one of the DNS servers does not return DNS records consistently, rectify this problem.
Action: remove this DNS server from the external DNS tab.
Workaround:
Bypass DNS by creating a SMTP connector with address space of <domain.com> and forward to smart host as the IP address the MX/A points to.
Exchange Query Explained
1. If Exchange finds the MX record(s) for a remote domain (through DNS query) it will not fall back to an A record query in the event the MX record (more precisely, the A record the MX record points to) is temporarily not responding on port 25. Instead, Exchange will try another MX record if one exists. If no other MX records exist and none are responding on port 25, the queue will go into a retry state for this remote domain. When that retry state has expired, Exchange will again attempt to resolve MX records for this domain, and so on.
2. Exchange will fall back to an A record query for the remote domain in the event that no MX record can be found. This is not to say that the MX record does not exist - only that when Exchange issued a DNS query for the remote domain the DNS response was "server failure", which basically means no MX was found. So, the MX record may indeed exist, but Exchange simply could not find it through DNS resolution.
3. Exchange then queries the A record and this happens to return a result. If the A record is listening on port 25, but does not accept mail for <domain.com> then we will get the NDR with 550 5.7.1 unable to relay (or some variation of this NDR error code) when Exchange connects and attempts to send the e-mail.
So, the intermittent nature of the problem is caused by a failure to find the MX record and a success in finding A record. This can happen for a variety of reasons, but it boils down to flakey DNS resolution.
For example:
a. A bad DNS server listed as a forwader on the DNS server.
b. A bad DNS server on the TCP/IP properties.
c. A bad DNS server on the SMTP VS (external DNS servers)
d. Multiple default gateways on Exchange (ie. multiple NICs on different networks, each NIC having a default GW)
A netmon on Exchange will show the failed MX lookup and successful A record lookup; however, it may not be conclusive unless the "bad" DNS server is listed in the netmon trace. For example, if Exchange points to internal DNS server(s) for name resolution and these DNS servers service these DNS queries by Exchange, you may need a netmon on the DNS server(s) as well to determine which DNS server/Forwarder/etc is at fault.
Regards,
Shahul Hameed Dasthagir
Support Engineer | Enterprise Communications Support

Outlook 2013 won't start with Exchange 2003 on the network

Hello All,
I have outlined my problem below, If someone could please help me that would be great!
Environment
==========
SBS 2003 Server Running AD and Exchange 2003
Clients are Windows 7 with Office 2013 and Outlook 2007 (to connect to existing 2003 Server)
Issue
=====
I am in the process of Migrating off of SBS 2003 to Office 365. The situation is that my customer needs to keep the SBS 2003 server until end of life where they will at that time determine a upgrade path. They however do not want to use Exchange
anymore. I have migrated their mailboxes successfully to Office 365.
The problem that I am running into is with Outlook 2013. Because Exchange 2003 server still exists in the network I am unable to launch Outlook 2013. I get a Message
"The Resource that you are trying to use is located on an unsupported version of Microsoft Exchange Contact your e-mail administrator for assistance"
I have tried to create a new Outlook profile. However since the exchange server exists still it auto discovers the server for the account.
Questions
========
1. What is the best workaround for this situation? My customer still needs to keep their SBS sever for their domain and plans on retiring the server before Server 2003 End of Life this coming server. (Upgrade is not an option, nor is getting
rid of the Domain, they are a small company).
2. If I disabled the Exchange services on the server would this work? Would outlook 2013 not detect Exchange
2003 on the network?
Basically I need to force Outlook 2013 to look at Office 365.
3. Configuring Outlook 2013 to manually connect to Office 365? The problem here is that how do I locate the server name for the manually connection? I have found some blogs that say to use Remote Connectivity Analyzer https://testconnectivity.microsoft.com/
but I cant seem to get that to work.
Any ideas?
Thanks!

Hi,
Please refer to the following article to check your migration steps from Exchange 2003 to Office 365:
http://blogs.technet.com/b/canitpro/archive/2013/05/31/step-by-step-migration-of-exchange-2003-server-to-office-365.aspx
If all mailboxes are moved to Office 365, Outlook 2013 would use Autodiscover service to connect to your Office 365. Please make sure your Autodiscover service is configured correctly in Office 365. Also
verify that all the DNS records and Public Folder are updated and pointed towards Office 365 services. If there is any question about migration to Office 365,
we can ask a question in Exchange Online forum for more suggestion:
https://social.technet.microsoft.com/Forums/msonline/en-US/home?forum=onlineservicesexchange
Regards,
Winnie Liang
TechNet Community Support

Remove exchange 2003 error

good day ,
I start to remove Exchange2003 after success migration to Exchange2010 SP3 I delete the connector
w2k3-w2k10
w2k10-w2k3
I followed this link step by step:
http://technet.microsoft.com/en-us/library/gg576862%28v=exchg.141%29.aspx
I have two exchange2003 one w2k3frontend and w2k3exch
for w2k3frontend from add/Remove program is not working I did it with ADSIEdit
but for w2k3exch I get this message:
This server is the master routing routing group first routing group that contains other serveurs.Impossible uninstalling this server without first select a new master routing for this routing group or delete all servers in that group routing .
This server is the server update recipients for the domain. you can uninstall only after selecting another server update of recipients for this area.
so if this still master routing and the server update recipients for the domain so no problem if I delete from ADSIEdit .
can you please help me
Regards
e

Zikorai,
From what you are telling us, you won't be able to remove Exchange from that system using the setup program - go ahead and remove it manually, both from the server (if necessary) and from the directory (which will definitely be necessary) using the links
we have provided. Here are some good ones:
Removing Exchange 2003 from the Server:
This one is only necessary if you need to remove Exchange but still have the server operational for other purposes - for instance, if it is also a domain controller - http://blogs.msmvps.com/bradley/2011/01/28/manually-removing-exchange-2003-from-the-migration-process/
If the server isn't required for any other purposes, rebuild the operating system on it
Removing Exchange 2003 from the Directory:
Go to the "Remove the Exchange Server 2003 server from Active Directory" section of this link for how to remove Exchange 2003 from the directory:
http://support2.microsoft.com/kb/833396/en-us
One note from Ed Crowley, Exchange MVP - "Do not remove the Exchagne 2003 administrative groups unless you want free-busy problems, leave them there forever."
This should leave you with a system that has no Exchange 2003 and Exchange 2010 is running smoothly with no issues.

Exchange 2003 to Exchange 2013

Instead of going from Exchange 2003 to 2010 to 2013. I have decided to remove Exchange 2003 from the organization and install 2013 since I don't have too many users.
I have removed Exchange 2003 from the Organization (http://tutorial.programming4.us/windows_server/Removing-an-Exchange-Server-2003-Server-from-an-Organization.aspx).
When I install Exchange 2013, it doesn't ask me for the organization name. Is it using the data that was left in Active Directory from Exchange 2003? I ran the setup to uninstall Exchange 2003, doesn't that remove the Exchange 2003 data in Active Directory
as well?
Thanks

So, have you migrated all the data from exchange 2003 to 2013 before it has been removed ?
If not, I am really wondering how you have removed exchange 2003 without installing 2013 and migrating users mailboxes data from previous one.
By the way, please walk through this well described blog that seems to be helpful in your circumstance and provides step-wise instruction for the same : http://www.msexchange.org/articles-tutorials/exchange-server-2013/migration-deployment/planning-and-migrating-small-organization-exchange-2003-exchange-2013-part1.html
If you wish to achieve this goal automatically, you may also consider on this automated application (http://www.exchangemigrationtool.com/) that could be an appropriate solution to migrate mailboxes directly from exchange 2003 to 2013 by skipping intermediate
version.

Any1 know how to reformat se vivaz?my mobile cnt send out message

why my msg cnt be send out?

http://dl-www.sonyericsson.com/cws/download/1/743/578/1271830498/U5i__UG_EN_1232-6052_2.pdf See page 77 of the manual on how to reset the phone.

Exchange Server 2003 :: ActiveSync :: Unable to send out attachments

Hi All,
I am facing a weird issue with SBS 2003 (windows server 2003 sp2 with microsoft exchange 2003 sp2) Microsoft Exchange ActiveSync. ActiveSync users are able to configure the devices just fine, send and receive email fine as well but when they try to send
any attachment the email will stay in the outbox.
So far i have tried the following fixes
made sure the permissions on the exchange vdirs and activesync vdir are correct
c:\windows\temp and %temp% location has read/write access to authenticated users
uploadreadaheadsize (thru adsutil.vbs) and messagesizelimit for oma reg key are bumped up (20MB each)
testremoteexchange connectivity analyzer shows all green
Now, if i make user the member of administrators group and try to send an email with attachment (i am sending a screenshot of 2.3mb) it goes out fine.
IIS logs shows HttpServerStatusError 500used logparserstudio to parse the iis file
cs-username
cs-uri-stem
HTTPstatus
w3-status-details
domain\testas
/Microsoft-Server-ActiveSync
500
HttpStatusServerError
any pointers how this issue can be dealt with and resolved, will be appreciated.
Regards,
Nav
Regards, Navdeep [a.k.a v-2nas]

any ninjas out there to crack this problem........
Regards, Navdeep [a.k.a v-2nas]

Outlook 2010 RPC over HTTP to Exchange 2003 users remain disconnected after login

Greetings Guys,
I am unable to find a solution, Windows 2003 DC, Exchange 2003, all user were working great, RPC over HTTP, until Tuesday at about the same time perhaps before the MS update KB3002657
all remote users using outlook 2010 did not have authentication popups as was noted from this KB. But instead all login successfully, ( looking at the security logs in the exchange) , but all are remaining disconnected, immediately after login.
The users had already been configured with the registry DefConnectOpts RPC key, so I doubt their Outlook profiles are the problem.
I suspect the DC's ( we have 2 ) or the exchange have picked up an issue. I am out of ideas.
Any help would be awesome
Barry

Hi,
According to your description, I understand that Outlook(Outlook Anywhere) client display disconnected after install MS update KB3002657.
If I misunderstand your concern, please do not hesitate to let me know.
KB3002657 is a security update to prevent attacker logging on to a domain-joined system and being able to monitor network traffic. More details about this update, please refer to:
https://technet.microsoft.com/library/security/ms15-027
For your question, please try to reconfigure a Outlook profile for testing.
If it works, you can try to below steps to pop sign in page in Outlook client:
1. Open Outlook---> File and click “Account setting”, then select account name and click “Change”.
2. Click “More settings”, switch “Security” and check “Always Prompt for logon credentials”。
3. Restart Outlook to login your account.
Once this done, you can uncheck this setting for convenience.
Besides, I find an similar thread about your question, for your reference:
https://social.technet.microsoft.com/Forums/exchange/en-US/7199811f-ee41-4b81-aafe-698bdb5a0b49/recently-outlook-cannot-auth-username-and-password?forum=exchangesvrclients
Thanks
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Allen Wang
TechNet Community Support

Exchange 2003 sending out high https traffic to Blackberry servers

Similar Messages

Maybe you are looking for