Exchange Server Forums

Forums | Register | Login | My Profile | Inbox | RSS RSS icon | My Subscription | My Forums | Address Book | Member List | Search | FAQ | Ticket List | Log Out

The remote server did not respond to a connection attempt & Unable to bind to the destination server

Users viewing this topic: none

Logged in as: Guest
  Printable Version
All Forums >> [Microsoft Exchange 2003] >> Exchange 2003 SBS >> The remote server did not respond to a connection attempt & Unable to bind to the destination server Page: [1]
Login
Message << Older Topic   Newer Topic >>
Limited time MSExchange.org offer! -- 1.Sep.2008 1:00:00 PM
TechGenix and SolarWinds have partnered to provide free copies of SolarWinds Exchange Monitor to all visitors who join the MSExchange.org Forums. SolarWinds Exchange Monitor is a handy desktop dashboard that continuously monitors Microsoft Exchange to deliver real-time insight into Exchange services, mail queue sizes, and host server health. Learn more about Exchange Monitor and the free offer!
The remote server did not respond to a connection attem... - 8.Jan.2007 2:51:25 AM   
jeevi

 

Posts: 3
Joined: 7.Jan.2007
Status: offline
 hi,
i am newbe to exchange and sba. in our server we got these errors while some of the messages are queued up for sending. i searched many forums and tried many ideas.
there are,
1. i can access some domains using nslookup and cannot connect using telnet.
2. some domains i can't access thru nslookup too.
3. we have reverse lookup zones, i think which was created by sbs by default
4. and some articles suggests to use 'smart host' address in a Connectors -> Interner mail SMTP Connectors -> Properties -> General Settings - select option forward through smart host and set the address, but I can not set this(?), bcz we are using internal server to send mail.(our fully-qualified domail name looks like servername.domain.local - is this normal?)
5. and no external DNS servers are added in a Protocols -> SMTP -> Default SMTP virtual server -> Properties -> Delivery -> Advanced -> Configure external DNS server - settings.

i am really confused, bcz some times it can send mail to particular address, but sometime not (even most common domains like yahoo,aol...). currently there are about 140 items in the queue. this is really strange to me.
any suggestions? any help would be greately appreciated!
Thanks.

< Message edited by jeevi -- 8.Jan.2007 3:05:08 AM >
Post #: 1
RE: The remote server did not respond to a connection a... - 8.Jan.2007 9:55:46 AM   
uemurad

 

Posts: 5489
Joined: 7.Jan.2004
From: California, USA
Status: offline
If you use NSLOOKUP and point it at your ISP's DNS server, can you resolve those other domain names?  Do you have this set up as a DNS forwarder?

When telnet fails, are you attempting to connect via name, or IP address?

_____________________________

Regards,

Dean T. Uemura
Microsoft MVP - Exchange
exchangeguy.blogspot.com
uemurad@yahoo.com

(in reply to jeevi)
Post #: 2
RE: The remote server did not respond to a connection a... - 8.Jan.2007 9:55:35 PM   
jeevi

 

Posts: 3
Joined: 7.Jan.2007
Status: offline
hi,
thank you for ur reply.
i am not quite understand the statement "point it at your ISP's DNS server", how to do that?
this is what i got when i tried to resolve address for yahoo.com
C:\Documents and Settings\Administrator>nslookup
Default Server:  myServerName.domain.local
Address:  192.168.10.1
> set timeout=30
> set type=mx
> yahoo.com
Server:  myServerName.domain.local
Address:  192.168.10.1
*** myServerName.domain.local
myServerName.domain.local can't find yahoo.com: Server failed
>

but, when i can resolve hotmail or someother addresses and also can connect via telnet. eg.
> hotmail.com
Server:  myServerName.domain.local
Address:  192.168.10.1
Non-authoritative answer:
hotmail.com     MX preference = 5, mail exchanger = mx3.hotmail.com
hotmail.com     MX preference = 5, mail exchanger = mx4.hotmail.com
:
hotmail.com     nameserver = ns1.msft.net
mx1.hotmail.com internet address = 65.54.245.8
:
:
>
and i received the replies while connecting via telnet.

is anyother way to check this?
Thank you again.

< Message edited by jeevi -- 8.Jan.2007 10:13:40 PM >

(in reply to uemurad)
Post #: 3
RE: The remote server did not respond to a connection a... - 9.Jan.2007 12:00:40 PM   
uemurad

 

Posts: 5489
Joined: 7.Jan.2004
From: California, USA
Status: offline
If you know the IP address of your ISP's DNS server, then within NSLOOKUP give it the command "server xxx.xxx.xxx.xxx".  By default NSLOOKUP uses the DNS server you see in IPCONFIG /ALL.

_____________________________

Regards,

Dean T. Uemura
Microsoft MVP - Exchange
exchangeguy.blogspot.com
uemurad@yahoo.com

(in reply to jeevi)
Post #: 4
RE: The remote server did not respond to a connection a... - 10.Jan.2007 1:28:55 AM   
jeevi

 

Posts: 3
Joined: 7.Jan.2007
Status: offline
         actually i dont know  my ISP's ip addr. i tried to get that using some dsn lookup websites and then used that ip in my "nslookup " . but no use.
       and, i am wondering, why sometime it's sending immediately, but sometime it queued up even for a day and then send it or not sending at all?.
thanks.

(in reply to uemurad)
Post #: 5

Page:   [1] << Older Topic    Newer Topic >>
All Forums >> [Microsoft Exchange 2003] >> Exchange 2003 SBS >> The remote server did not respond to a connection attempt & Unable to bind to the destination server Page: [1]
Jump to:

New Messages No New Messages
Hot Topic w/ New Messages Hot Topic w/o New Messages
Locked w/ New Messages Locked w/o New Messages
 Post New Thread
 Reply to Message
 Post New Poll
 Submit Vote
 Delete My Own Post
 Delete My Own Thread
 Rate Posts