| NowSms and Exchange 2007 problem |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through April 12, 2010 ⬆ |
◄ ► |
| Author | Message | |||
| motasim New member Username: Motasim_mah Post Number: 1 Registered: 02-2010 |
Hi I have nowsms 2006, and i have a problem with sending sms through email. Already configuer nowsms in my DNS as shown in the picture:  When trying to send email from my outlook to mobilenumber@nowsms.local, i receive a failure notification:  Is there any specific configuration to do in MS Exchange Server 2007??? Note: when send SMS through a site, it will send it successfully. | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1805 Registered: 08-2008 |
Are you sure that your Exchange Server is configured to only use that internal DNS server (and not use any other external DNS server as a secondary)? I have zero experience configuring Exchange Server, however I believe it uses the standard DNS settings configured in Windows. If you run NSLOOKUP on the Exchange Server, does it resolve that domain ok? NSLOOKUP set type=MX nowsms.local. Can NSLOOKUP resolve nowsms.local using the above commands on the Exchange Server machine? -- Des NowSMS Support | |||
| motasim New member Username: Motasim_mah Post Number: 2 Registered: 02-2010 |
yes it can. When run nslookup in the exchange server, it resolve the sms gateway:  | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1807 Registered: 08-2008 |
Unfortunately, I don't know enough about how Exchange Server works to answer your question. However, I've done a little research, and instead of using a local DNS server like you are doing here, it is possible to configure a relay host for a specific domain directly in Exchange Server. For Exchange 2003, I found a good example here: http://www.amset.info/exchange/smtp-connector.asp Exchange 2007 is similar, so it's worth reading through the above example, but the configuration settings are a little different. The following article comes close to explaining it: http://www.msexchange.org/tutorials/Exchange-Server-2007-Email-Routing-Part2.htm l Skip down to the part of the above article that has the header "Configuring Outbound E-Mail Transport", as everything above that is unrelated to what you're trying to do. 1.) Create a new SMTP send connector in the organization configuration tab. Give it a name matching your local NowSMS domain "nowsms.local". The intended use is "Custom". 2.) For the address space, you will need to "Add" your local NowSMS domain "nowsms.local". 3.) For the network settings, you do not want to use DNS. You want to route mail through a smart host. Specify the IP address of the NowSMS server as a smart host by putting "[]" around the IP address, such as [10.1.1.11] 4.) The source servers are your local Exchange Servers that are allowed to use this route. Once you have the above SMTP connector defined in Exchange Server 2007, then I believe it will do what you want. If possible, I'd appreciate it if you would share your experience (and screen captures) in setting this up, as I'm sure it would help others. -- Des NowSMS Support | |||
| motasim New member Username: Motasim_mah Post Number: 3 Registered: 02-2010 |
Unfortunately its not working, and give me the same error message. And i take a screen captuers, and maybe you can tell me where is my wrong? 1- From Exchange Managment Console, expand organization configuration, then select Hub Transport, Then from right windows select Send Connector, the Right Click "New SMTP Connector".  2- Write the name for new connector"Now SMS".  3- Add the domain name "nowsms.local".  4- Add the IP address for sms gate way "[10.1.1.11]".  5- Add the Exchange Serve.  6- New Connector Summery.  7- Complete the steps successfully.  Is there any wrong with my steps??Bescuse its not working. | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1810 Registered: 08-2008 |
I don't think *.nowsms.local is valid. (It might match x.nowsms.local, but not nowsms.local.) I think it needs to just be nowsms.local. | |||
| motasim New member Username: Motasim_mah Post Number: 4 Registered: 02-2010 |
Its automatically become like this,i just enter "nowsms.local", and i tried "@nowsms.local", but also its not accepted. | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1811 Registered: 08-2008 |
Ok, I assume that it converted it to *.nowsms.local because you checked "Include all subdomains". That part should be ok. I have little experience with Exchange Server, but based upon all available resources, it seems to me that this should work properly. Are you seeing the same exact error in the reject messages, or is it different? Specifically, has this error message changed: Bad destination host 'DNS Hard Error looking up nowsms.local (MX): NXDomain' After defining this SMTP send connector, Exchange should NOT be performing a DNS MX record lookup when routing mail addressed to a user @nowsms.local. Perhaps the error message that you are getting has changed and we need to look at a different issue now? | |||
| motasim New member Username: Motasim_mah Post Number: 5 Registered: 02-2010 |
I get the same Error message: "'DNS Hard Error looking up nowsms.local (MX): NXDomain". And are you suggest remove Check box "Include all subdomains"??? | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1816 Registered: 08-2008 |
I would try removing the checkbox "Include all subdomains". In all of the similar examples that I can find, this box is never checked, and "*." does not appear in front of the domain name. I don't see anything else that looks different. | |||
| motasim New member Username: Motasim_mah Post Number: 6 Registered: 02-2010 |
Now, i removed the check box "Include all subdomains". and its working......But..... some time its work and some times give me the same error message.... I give nowsms.local cost=1 and already have another SMTP Connector for "*" and the cost=2 Do you have any idea abnout that? Why some times it send SMS and some times its not???? | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1827 Registered: 08-2008 |
Setting the cost is a good idea. Exchange is supposed to look for a best match if the cost is the same, but setting a lower cost is better because it is more explicit. Check the spelling carefully in the failed messages, and make sure they are not because of a typo. I would suggest scheduling a restart of the Exchange Server, in case some routing information is stuck somewhere in a cache. Also, make sure the error message is the same "DNS Hard Error" message, and not some other error. | |||
