The IMAP service does use IOCompletion ports for scalability - although this can be turned off, and is best practice and should not have anything to do with netBIOS. The server binds and listens for connections from IMAP and MAPI clients (just as any other windows socket service does). MailEnable's MAPI protocol operates as an extension of IMAP (typically port 143). I'd welcome comments from ME about this issue. Needless to say, I'm not happy with the security implications of having these or any other unecessary ports open on an internet-facing server and will probably block them again fairly shortly. I don't know for sure but I do wonder what other "hidden" port/protocol dependencies there may be in the MAPI services. The general stability and speed of MAPI services - as experienced by users - improved as a consequence. We're currently running the latest beta MAPI connector: the users are geographically distributed on a wide variety of ISPs, connecting to a cloud-based ME server which is running on a high performance backbone however the performance of the MAPI connector on several of the users' machines has varied from entirely unusable to more or less OK.īecause the ME server is not a domain or DC server, and is for all practical purposes only handling email, it requires no WIndows-level user authentication of logins etc, so we had seen no need to enable NetBios capabilities on the server or in free-standing mobile laptops etc.Īfter doing some reading in the Technet KB I tried an experiment and enabled netbios over TCP at the NIC and opened up the firewall on TCP ports 137-139 and then reset some of the client machines systems to use NetBios over TCP as well.
0 Comments
Leave a Reply. |