[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1359
  • Last Modified:

EdgeSync problem

Can somebody please help me i'm breaking my head over this. I have my edge server working and my hub. The suync is also working when i accept new domain. But al the messages that are in the message queue won go to my hub server. I dont know where to look, My firewall is disabled im not running ISA or something. the edge server is not in a DMZ.
0
Noeger
Asked:
Noeger
  • 42
  • 23
  • 7
1 Solution
 
Glen KnightCommented:
Check the permissions tab of your receive connectors in the hub transport/mailbox serve does it have Exchange Servers checked?
0
 
Narayan_singhCommented:
where have you created accepted domain ...need to create create in HUB server and then start edgesync and make sure that is reflected in you r edge server.

On the Edege server on the send connector (edeg to Hub) specify your hub server's IP as a smart host.

Also check on the send connect (Edge to Hub) what are the domain specified . it should be "--" without qoutes.
0
 
NoegerAuthor Commented:
I now see that i cant resolve the name of my edge server when i do a nsloopup on my hub server???!
0
Problems using Powershell and Active Directory?

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

 
Glen KnightCommented:
Can you ping the server?

Do you have an entry for the servers in your internal DNS server?
0
 
NoegerAuthor Commented:
I edited the hosts files but is there something i have to change on my dns server??
0
 
NoegerAuthor Commented:
I will take a look
0
 
Glen KnightCommented:
Can both servers ping each other by name and IP?
0
 
NoegerAuthor Commented:
when i ping only the first hop works
0
 
NoegerAuthor Commented:
from the hub to edge
0
 
Glen KnightCommented:
You need to be able to ping and get a response from both servers to the other.

If you cannot then this is your problem.  Check your router and ensure its configured correctly.
0
 
NoegerAuthor Commented:
oke on the edge server i used the dmc.exe then when i ping the FQDN of the hub server i get the request could not find...... but when i ping the ip it works
0
 
NoegerAuthor Commented:
*cmd
0
 
NoegerAuthor Commented:
if i ping ip adresses everything works i guess thats not the problem than
0
 
NoegerAuthor Commented:
When i do a test-Edge subscription i see everything skipped but when i start the sync i get an succes but why do the messages dont go to my hub server? the ping works, i know i messed something up!
0
 
Glen KnightCommented:
It needs to be able to communicate by name so if you cannot ping by name you need to sort that out.
0
 
NoegerAuthor Commented:
Ok I can Ping the names, i think i typed something wrong
0
 
NoegerAuthor Commented:
@Narayan do you mean the adress space tab on the connector, the type is smtp, and the adress is -- ???
0
 
Narayan_singhCommented:
What about the smarthost do you have HUB's Ip or FQDN in the smart host ?
0
 
NoegerAuthor Commented:
No i just entered the Hubs ip as smart host but when i want to change the adress space tab i get a warning should i change anything there??
0
 
NoegerAuthor Commented:
should i enter anything by: Specify the FQDN this connector response HELO orHELO??
0
 
Narayan_singhCommented:
thats alright just need to mention the IP of hub server in the send connector and in the domain field.
In domain field you should have "--" no qoutes and you need to modify these settings from hub and then do edgesync.

need to modify this on the send connector for sending mail from edge to hub
0
 
NoegerAuthor Commented:
Oke i typed the ip adress of the hub and i changended the edge server to hub server in the source server tab still nothing works the mails are still in the queue
hub1.jpg
hub2.jpg
hub3.jpg
hub4.jpg
0
 
NoegerAuthor Commented:
this wone i changed the edge server to hub server
hub5.jpg
0
 
Narayan_singhCommented:
in address spec instaled of IP mention "--" no qoutes change the settings from HUB ad then edgesync and then restart transport on Edge
0
 
Narayan_singhCommented:
Sorry for typo that was "address space"
the first screen shot need to modify that rest is fine.
0
 
NoegerAuthor Commented:
Oke now i get an ip in the queue list but they are still hanging there????
hub6.jpg
0
 
NoegerAuthor Commented:
I had to change this one back ore else i could put the "--" so now its the edge server again
hub5.jpg
0
 
Narayan_singhCommented:
Did you restart tranport service in Edge and what abou the address space you can also replace those "--" with accepted domain
like contoso.com and cost 1
0
 
Narayan_singhCommented:
?
0
 
NoegerAuthor Commented:
no the problem is still not fixed :( i did the steps i was told!
0
 
Glen KnightCommented:
Can you check the properties of the Receive Connector on the internal server.
Check the permissions tab and make sure Exchange Servers is in there.
0
 
NoegerAuthor Commented:
it was already checked
0
 
NoegerAuthor Commented:
are the send receive connetors the only problems i have, or could there be somthing else>?
0
 
NoegerAuthor Commented:
this error am i getting now: 451 4. 4.0 primary target ip address responded with: "451 5.7.3 Cannot achieve Exchange server authentication." Attempted failover to alternate host, but that did not succeed. Either there are no alternate hosts, or dilevery failed to all alternate hosts
0
 
Glen KnightCommented:
as I suspected it's down to authentication on the receive connectors, can you post screenshots of all tabs on both receive connectors.
0
 
NoegerAuthor Commented:
i think it was because i removed the server authentication there
receive1.jpg
receive2.jpg
receive3.jpg
receive4.jpg
receive5.jpg
0
 
Glen KnightCommented:
Can you uncheck TLS
I see you have also disabled IPv6?  You should not do this with Exchange 2010 and it will stop the transport service from working.
0
 
Glen KnightCommented:
Sorry the receive connector I was after was the one on your internal server.
0
 
NoegerAuthor Commented:
IPv6 on both my network adapters on the edge server were checked!
0
 
Glen KnightCommented:
OK, can you screenshot the connectors on the receiving server please?
0
 
NoegerAuthor Commented:
the dhcp on my dc says its enabled?????
dc.jpg
0
 
NoegerAuthor Commented:
give me a minute
0
 
Glen KnightCommented:
Yes but is it enabled on the servers.
That just means it will give out IPv6 DHCP addresses.
0
 
NoegerAuthor Commented:
this is from the client connector
client1.jpg
client2.jpg
client3.jpg
client4.jpg
receive7.jpg
0
 
Glen KnightCommented:
The send connector on your edge server is using port 25 so you need the properties of the Default MX01 please.
0
 
NoegerAuthor Commented:
0
 
Glen KnightCommented:
Can you uncheck TLS and restart the Microsoft Exchange Transport service?

From your Edge Server can you telnet to the server on port 25?
0
 
NoegerAuthor Commented:
oke the tellnet works and i restarted the service
0
 
Glen KnightCommented:
so what is happening now with mailflow?
0
 
NoegerAuthor Commented:
This is really sick, still only outgoing and the others are waiting in line ......   :(:(
0
 
Glen KnightCommented:
Can you check "Integrated Windows Authentication" on your receive connectors on the other server?
0
 
NoegerAuthor Commented:
sorry where can i find this IIS?
0
 
Glen KnightCommented:
No, on the Authentication tab of your receive connectors.
0
 
NoegerAuthor Commented:
dont you do things like teamviewer ore something?
0
 
Glen KnightCommented:
We are not allowed to offer remote assistance, some experts offer this service via their profile.

Have you changed the authentication setting?
0
 
NoegerAuthor Commented:
yes but when i send email now from my gmail i get this messages, i did not get this before : We recommend contacting the other email provider for further information about the cause of this error. The error that the other server returned was: 530 530 5.7.1 Client was not authenticated (state 13
0
 
Glen KnightCommented:
That setting should be on the internal server not the Edge transport server
0
 
NoegerAuthor Commented:
oke when a enabled the TLS again i received the message in my queue
0
 
Glen KnightCommented:
So mailflow is now working?
0
 
NoegerAuthor Commented:
oke the message is now stadinig there with the status ready, can there be anther reason why it cant go the the mailbox, AD LDS, something else
0
 
NoegerAuthor Commented:
before the message didnt say ready
0
 
NoegerAuthor Commented:
it sayed retry
0
 
Glen KnightCommented:
if it says Ready then it should deliver the messages, did you restart all the services after making the authentication change?
On both servers
0
 
Glen KnightCommented:
have you got all the required ports open: http://technet.microsoft.com/en-us/library/aa996562(EXCHG.80).aspx
0
 
NoegerAuthor Commented:
this doesnt have anything to do with it right?
0
 
NoegerAuthor Commented:
i will take a look
0
 
NoegerAuthor Commented:
do i have something here, the sync works but still do i get the skipped why?
skip.jpg
0
 
Glen KnightCommented:
Sorry where do you see this?
0
 
Glen KnightCommented:
Have you made the changes on the Hub Transport receive connector?
Are you now receiving mail?
0
 
NoegerAuthor Commented:
the screenshot was from the HUB, i dont think the problem lies with the connectors! ive changed that already
0
 
NoegerAuthor Commented:
YESSS, i needed to check the exchange server authentication box en Put the FQDN on the default receive connector! THNX SO MUCH
0
 
NoegerAuthor Commented:
I was pointed in the right direction
0

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 42
  • 23
  • 7
Tackle projects and never again get stuck behind a technical roadblock.
Join Now