What prevents port 1352 from receiving calls?
Hi. Last week one of our Domino servers stop receiving calls from other Domino servers in the same domain, as well as Notes clients. We discover that port 1352 was not working properly, while port 80 worked pretty well all the time. Just for testing, we changed the "broken" port to 1353 and it worked. So far, we do not know what prevents port 1352 from receiving calls. Have you ever heard something like this?
Gee, that's a good one. I don't have an exact answer, but I think it is a configuration issue, rather than anything actually broken. Keep in mind that IP ports are not really hardware ports at all, but software addresses within a communication protocol. So there is nothing to "break" (as far as I know) at one port versus another.



Download: IT Certifications 101
Inside this exclusive essential guide, our independent experts break down which IT certifications are worth your time and effort, and how to get started obtaining them to further your career— including specific certifications that any cloud or desktop pro should seriously consider.
By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.
You also agree that your personal information may be transferred and processed in the United States, and that you have read and agree to the Terms of Use and the Privacy Policy.
You might try switching the port back to 1352 and see if it works now. Maybe it was not really the problem, but something else was going wrong with replication.
You might also try looking at Domino R5 Admin Help / Index / Port. There are lots of entries there about setting up port addresses, so you might find something there that applies to your setup.
Dig Deeper on Domino Resources - Part 6
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.
Meet all of our Domino experts
View all Domino questions and answers
Start the conversation
0 comments