Hi I am using Exchange 2007 and have just installed a new edge server and when I try to send external e-mails they get stuck in the queue (with the above error) on the hub transport server and never seem to make it to the edge server. The only thing I can think of is that we have something misconfigured on the edge server because it has a dns suffix with .co.uk and the local server is .local Also Edge synch works, pinging between the servers, telnet. so general general conectivity is fine. For now the firewall is also turned off until this is resolved so that's not in the way. Thanks
Can you lookup the MX record of the faulty domain using NSLOOKUP from the Edge serverr? -- Richard Rodgers M3 PostMasters M3PostMasters@nospam.m3tg.com M3 Technology Group www.m3tg.com "Jared" wrote in message news:7E7D99A3-CA9B-485C-B748-0A1DDF1938A6@microsoft.com... > Hi I am using Exchange 2007 and have just installed a new edge server and > when I try to send external e-mails they get stuck in the queue (with the > above error) on the hub transport server and never seem to make it to the > edge server. The only thing I can think of is that we have something > misconfigured on the edge server because it has a dns suffix with .co.uk > and > the local server is .local > Also Edge synch works, pinging between the servers, telnet. so general > general conectivity is fine. For now the firewall is also turned off until > this is resolved so that's not in the way. > Thanks
I turns out it was a very stupid mistake. I was trying to add the .co.uk edge server to my .local dns site once I created a .co.uk site in dns and added my server like I should have from the start it all started working. Thanks anyway "M3 PostMasters" wrote: > Can you lookup the MX record of the faulty domain using NSLOOKUP from the > Edge serverr? > > -- > Richard Rodgers > M3 PostMasters > M3PostMasters@nospam.m3tg.com > M3 Technology Group > www.m3tg.com > > > > "Jared" wrote in message > news:7E7D99A3-CA9B-485C-B748-0A1DDF1938A6@microsoft.com... > > Hi I am using Exchange 2007 and have just installed a new edge server and > > when I try to send external e-mails they get stuck in the queue (with the > > above error) on the hub transport server and never seem to make it to the > > edge server. The only thing I can think of is that we have something > > misconfigured on the edge server because it has a dns suffix with .co.uk > > and > > the local server is .local > > Also Edge synch works, pinging between the servers, telnet. so general > > general conectivity is fine. For now the firewall is also turned off until > > this is resolved so that's not in the way. > > Thanks > > >
Glad it worked out for out ;o) -- Richard Rodgers M3 PostMasters M3PostMasters@nospam.m3tg.com M3 Technology Group www.m3tg.com "Jared" wrote in message news:DDF12B49-07D8-48D0-9319-3B76FEC4DCDF@microsoft.com... >I turns out it was a very stupid mistake. I was trying to add the .co.uk >edge > server to my .local dns site once I created a .co.uk site in dns and added > my > server like I should have from the start it all started working. > Thanks anyway > > "M3 PostMasters" wrote: > >> Can you lookup the MX record of the faulty domain using NSLOOKUP from the >> Edge serverr? >> >> -- >> Richard Rodgers >> M3 PostMasters >> M3PostMasters@nospam.m3tg.com >> M3 Technology Group >> www.m3tg.com >> >> >> >> "Jared" wrote in message >> news:7E7D99A3-CA9B-485C-B748-0A1DDF1938A6@microsoft.com... >> > Hi I am using Exchange 2007 and have just installed a new edge server >> > and >> > when I try to send external e-mails they get stuck in the queue (with >> > the >> > above error) on the hub transport server and never seem to make it to >> > the >> > edge server. The only thing I can think of is that we have something >> > misconfigured on the edge server because it has a dns suffix with >> > .co.uk >> > and >> > the local server is .local >> > Also Edge synch works, pinging between the servers, telnet. so general >> > general conectivity is fine. For now the firewall is also turned off >> > until >> > this is resolved so that's not in the way. >> > Thanks >> >> >>
