I have posted previous messages about problems concerning the Agent.RunOnServer() method. I think this issue may be a routing issue through our firewall.
I’m not sure if anyone can help, in this matter, but I’ll throw this out as a general question.
We have had problems trying to get an agent to talk to our Mainframe DB2 DB when calling it via the RunOnServer method. The agent runs fine if it is scheduled, or called via the web. But if it is called from an internal Notes client, it hangs.
The Domino server is protected from the internet via a firewall, and there is a “DMZ” positioned between Domino and our Mainframe system. If I open up a web browser, and point it at our Domino server, the admin can see inbound traffic coming in through the firewall in port 80. And, if I call the agent in question, he can see outbound traffic going to the DB2 server on our mainframe via a specified port in the DMZ. If we schedule the agent, the admin can again see the outbound DB2 traffic going through the DMZ.
However, if I open up the Notes client and access the Domino server, the admin does not see any inbound traffic coming through the firewall, and when I execute the agent as RunOnServer() there is no outbond traffic going from Domino to the DMZ.
The admin can see port traffic in the firewall on port 1352, but that is going to our Domino Mail server inside our organization.
I’m thinking that when I come in via the client, I’m coming in on some unknown port, the Domino server does not know how to route traffic from this port through the DMZ to DB2.
Does this sound plausible? What other ports should we be looking at, or is this totally up to our network admin? Is there possibly another issue at work here? Has anyone had a similar experience?
Thank you for your input.
Previous Posts: