Exchange Comms issue\ Front to Back end

[shakamon]

Help, I am in deep water here:

Troubleshooting done so far...any tips to further find out what is wrong would be awesome. The back end exchange server is working fine. Internal Mail is fine. This server however send and recieves thru the front end server to the outside world. The FE is Nattd to a public IP and 389, ICMP, all ports oare open at this point to the back end server.

1. The system attendant wont start
2. I have MSexchange DSAccess errors filling up my app log
3. It is a front end server,
4. It cannot find the proper site name
5. MSExchangeSA error states no site name is available for this machine.
6. net diag serves up this.

Redir and Browser test . . . . . . : Failed
List of NetBt transports currently bound to the Redir
NetBT_Tcpip_{DFD4B017-6DDC-4637-8264-131FC52CE3B6}
The redir is bound to 1 NetBt transport.

List of NetBt transports currently bound to the browser
NetBT_Tcpip_{DFD4B017-6DDC-4637-8264-131FC52CE3B6}
The browser is bound to 1 NetBt transport.
[FATAL] Cannot send mailslot message to '\\NEC-INC*\MAILSLOT\NET\NETLOGON' v
ia redir. [ERROR_BAD_NETPATH]





"Only the dead fish follow the stream"

 

[BenChristian]

Hi shakamon,

You menioned that you opened ports on the firewall between the internal and perimeters networks so that "389, ICMP, all ports are open at this point to the back end server." Do you have ports openned between the FE server and a global catalog server? The FE server needs to be able to communicate with a global catalog server.



Ben Christian
MCSE, MCSA:Messaging

http://www.benchristian.com

 

[geranimo666]

Hi shakamon..

I'm facing the same issue and think you nailed it by stating whether the GC's communication port was opened.. what port should I open.. thanks for any support at all

geranimo

 

[BenChristian]

This article covers which ports need to be open between the FE and BE servers and the FE and GC servers:

http://www.microsoft.com/technet/pr...b9f-172e-4d4e-81a6-f9e04066817a.mspx?mfr=true

Ben Christian
MCSE, MCSA:Messaging

http://www.benchristian.com

 

[shakamon]

Update on this: This was the key error:
MSExchangeSA error states no site name is available for this machine (this is on the front end server after doing a dcdiag, netdiag, I forget)

If you change the default settings for sites and services and create new sites other than the defaultfirst-site link...

Make sure you have the correct subnet in AD sites and services for each and every site. This is what burned me.

This includes where the backend server is and where the front end server is. If you skip this, your backend server (like mine) will have issues talking to the DC's and the backend exchange server.

I rebooted the DC, then the backend, then the front end and all the issues cleared....

Also of Use to me: that exchange baseline analizer, that can help root out issues too.

I hope this helps
Shaka

"Only the dead fish follow the stream"