Problem with Exchange server

Hi,
I've finished the steps to set up both Send connector and Receive connector. Both Send connector and Receive connector have been enabled (shown in Fig 1).

But I don't get any Emails at all after I've sent mails using

https://localhost/owa

within this Exchange server.
t547.png
LVL 12
HuaMin ChenProblem resolverAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Seth SimmonsSr. Systems AdministratorCommented:
have you looked at the exchange queue (toolbox in the exchange management console) to see what is happening?
0
HuaMin ChenProblem resolverAuthor Commented:
Thanks.
Yes, I can see the mail I tried to send yesterday, within "Sent Item" folder.
Where is the log file to check any errors of the Exchange server?
0
HuaMin ChenProblem resolverAuthor Commented:
Where is the log file to check any errors of the Exchange server?
0
10 Tips to Protect Your Business from Ransomware

Did you know that ransomware is the most widespread, destructive malware in the world today? It accounts for 39% of all security breaches, with ransomware gangsters projected to make $11.5B in profits from online extortion by 2019.

HuaMin ChenProblem resolverAuthor Commented:
Any help?
0
Seth SimmonsSr. Systems AdministratorCommented:
have you looked at the application log for any exchange warnings or errors?
are you receiving any mail at all to your server?
0
HuaMin ChenProblem resolverAuthor Commented:
How to locate any errors in the log within Exchange server?
0
Seth SimmonsSr. Systems AdministratorCommented:
control panel -> administrative tools -> event viewer
look at the application log for any exchange-related warnings and errors
0
HuaMin ChenProblem resolverAuthor Commented:
Sorry, where to find out more details for the error highlighted in Fig 2?
t569.png
0
Seth SimmonsSr. Systems AdministratorCommented:
that's a problem...is that domain controller functioning properly?  are any domain controllers available?
0
HuaMin ChenProblem resolverAuthor Commented:
What to check concerning domain controller?
0
Seth SimmonsSr. Systems AdministratorCommented:
is it working? are there any errors in the event logs? can the exchange server ping and do dns queries to the domain controller?  there is a communication problem between the exchange server and domain controller
0
HuaMin ChenProblem resolverAuthor Commented:
What commands to check for these? thanks
0
Seth SimmonsSr. Systems AdministratorCommented:
look in the event viewer the same way you did on the other server
specifically the directory services log
how many domain controllers are there?
0
HuaMin ChenProblem resolverAuthor Commented:
Where is directory services log located at? thanks
0
Seth SimmonsSr. Systems AdministratorCommented:
in event viewer, expand custom views, server roles then active directory domain services
0
HuaMin ChenProblem resolverAuthor Commented:
Sorry, I do not see any error in that (in Fig 3)
t570.png
0
Seth SimmonsSr. Systems AdministratorCommented:
can you ping the domain controller from the exchange server?
does anything resolve with nslookup?
0
HuaMin ChenProblem resolverAuthor Commented:
Yes, I am able to ping that like

C:\Users\Administrator>ping WIN-BVDIC8GIAHI.win08.huamin.com

Pinging WIN-BVDIC8GIAHI.win08.huamin.com [fe80::200:5efe:?.?.248.250%15] wit
h 32 bytes of data:
Reply from fe80::200:5efe:?.?.248.250%15: time<1ms
Reply from fe80::200:5efe:?.?.248.250%15: time<1ms
Reply from fe80::200:5efe:?.?.248.250%15: time<1ms
Reply from fe80::200:5efe:?.?.248.250%15: time<1ms

Ping statistics for fe80::200:5efe:?.?.248.250%15:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

Open in new window

Here are what I get with nslookup

C:\Users\Administrator>nslookup WIN-BVDIC8GIAHI.win08.huamin.com
Server:  rbsdns31.net-yan.com
Address:  210.0.128.241

Non-authoritative answer:
Name:    qiye.g2.org
Address:  204.74.211.183
Aliases:  WIN-BVDIC8GIAHI.win08.huamin.com.win08.huamin.com

Open in new window

Here is the error got
¿¿¿¿¿¿: WIN-BVDIC8GIAHI.win08.huamin.com
huamin_chen@ymail.com
#550 4.4.7 QUEUE.Expired; message expired ##
¿¿¿¿¿¿:
Received: from WIN-BVDIC8GIAHI.win08.huamin.com
 ([fe80::200:5efe:113.255.242.14]) by WIN-BVDIC8GIAHI.win08.huamin.com
 ([fe80::200:5efe:113.255.242.14%15]) with mapi id 14.01.0218.012; Fri, 27 Sep
 2013 16:27:04 +0800
From: Administrator <Administrator@win08.huamin.com>
To: "huamin_chen@ymail.com" <huamin_chen@ymail.com>
Subject: test 3
Thread-Topic: test 3
Thread-Index: Ac67W1g3FeMtsQN2QdaTPs6g5I5sVg==
Date: Fri, 27 Sep 2013 08:27:03 +0000
Message-ID: <E2D9158F36698249BF9E7C06D165E088E4A70B9E@WIN-BVDIC8GIAHI.win08.huamin.com>
Accept-Language: zh-HK, en-US
Content-Language: zh-HK
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: multipart/alternative;
      boundary="_000_E2D9158F36698249BF9E7C06D165E088E4A70B9EWINBVDIC8GIAHIw_"
MIME-Version: 1.0

Open in new window


when trying to send the mail using

https://localhost/owa

Open in new window

0
Seth SimmonsSr. Systems AdministratorCommented:
i'm concerned with the name resolution here
do you have a private ip address space?
i would expect the exchange server to resolve with private address, not the public internet address which could be the reason why exchange can't talk to the domain controller because it's resolving the wrong ip address
0
HuaMin ChenProblem resolverAuthor Commented:
The server is now having 2 IPs. One is private like
192.168...

the other is pingable like
?.?.248.250

do you think I can disable the 2nd connection to see if it is fine?
0
Seth SimmonsSr. Systems AdministratorCommented:
the server has both a private and public ip address?  you are not using NAT through your firewall?

if your exchange server is trying to communicate using the public address, the firewall might be blocking that traffic in the public network

i don't know your topology so can't say whether disabling the second interface will break anything
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
HuaMin ChenProblem resolverAuthor Commented:
Thanks. the server is being runnning as a VM, with Adapter 1 having "Internal network" and having IP like "192.168...", while adapter 2 is a Bridged adapter that is having the IP allocated by the ISP. hOW to detect/avoid any traffic issue concerning the firewall in this?
0
HuaMin ChenProblem resolverAuthor Commented:
Hi,
Here is what I get now

C:\Users\Administrator>nslookup
Default Server:  localhost
Address:  ::1

>

what to adjust?
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.