Hello All,
This is a strange one. I have 10 server in the same NNN which route mail to each other through one hub server just fine except for one serverA which will not route to ServerB. The funny thing is when I do a trace command I receive the error The server is not responding. The server may be down or you may be experiencing network problems. Contact your system administrator if this problem persists. But the server is up! I could ping the server from Windows I could tracert to the server from windows. I could even open up databases from ServerA using the administrator to serverB.
All messages to ServerB are in the mailbox just waiting while other messages route fine to the other servers. I have entered the IP of ServerB in the hostfile and have checked the NAB for incorect IP address on connection documents.
From Serverb I can trace just fine and it sends messages to ServerA without a problem. Does anyone have any Ideas?
Thanks in advance.
M
Subject: Strange! Mail not routing to server in same NNN
Sounds like a DNS issue or Active Directory issue. Any changes to either of those environments lately? Most likely, the name resolution is invalid. try coding the optional ip address on the connection docs.
Hope this helps?
Subject: RE: Strange! Mail not routing to server in same NNN
Tks for the response T. Actually there has been a change in the enviorment, unfortunatly that a diffrent dept. I will check w/ them and see what has been done.
When you say try coding the ip addree on the connection docs do you mean enter the ip? Sorry if I am misunderstanding you. I will update the status.
Tks again
Subject: RE: Strange! Mail not routing to server in same NNN
There is an “optional network address” on the connection doc that you are trying to connect to. Might help Domino resolve the address.
Subject: Could be exactly the opposite.
I recommend never hard-coding an IP address in any Notes/Domino document if it can at all be avoided; it introduces problems just like this. In fact, it’s possible that the whole problem is that while the server’s new IP addy has been correctly updated in DNS, somebody previously entered it into the server doc, so other Domino servers are still using the old one.
(It could also be the Optional network address field on a connection doc, but since the original post explicitly stated that this was network routing, and not connection doc routing, that wouldn’t be it.)