We have a s/390 queue manager communicating with a manager on a Win NT server. The sender channel on s/390 points to the IP address and uses the default 1414 port. Everything works fine. On the NT side another manager was added with a listener on port 1515. On the s/390 side, we added another sender channel pointing to the same IP address with the new port. When attempting to start the channel, it goes to 'bind' status, then fails. The messages in the s/390 channel initiator indicate the listener is not available. Our NT support says everything is okay on their side. I can telnet to both ports on NT. I cannot see anything in the doc that shows our setup will not work and when we change the new channel to the old port, it works. Is there something we are missing ? I am a mainframe person and the s/390 to NT is something new to me.
__________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
