Re: Connect to remote system DRDA port

[Charles Wilt <charles.wilt@xxxxxxxxx>]

I'd be willing to be there is a firewall somewhere along the line....

But you could always start a comm trace on the i to prove that yes, indeed
the packets to port 446 aren't getting there and thus there is a firewall
blocking port 446 somewhere...

Charles


On Fri, Nov 9, 2012 at 9:29 AM, Jeff Young <jyoung0950@xxxxxxxxx> wrote:

> All,
>  I have a remote IBM i system that I connect to via Client Access 5250
> emulation.
> There is no VPN or firewall on the remote system.
>
> All Host Servers are started at the client.
> NETSTAT shows:
> Remote           Remote     Local
> Address          Port          Port          Idle Time      State
>     *                     *           446          124:20:46     Listen
>     *                     *           drda         124:20:46     Listen
>
>     *                     *           ddm         124:20:46     Listen
>     *                     *           447          124:20:46     Listen
>
>
> In i Nav, verify connection, I receive the following error:
> CWBCO1022 - Remote Port 446 will be used
> CWBCO1003 - Sockets error, function connect() returned 10060
> CWBCO1048 - A timeout occured attemtpting to connect to the iseries.
>
> The remote site is running R7.1.
> DRDA server (port 446) is active on the remote site.
>
> Why can I not connect?
> There is no firewall and no vpn.
>
> I use Client Access (whatever the latest nom du jur is) to connect directly
> to the client.
> I am using a public IP address: 124.xxx.xxx.xxx to connect.
>
> I can transfer files from the remote system to my PC using client access
> file transfer.
>
>  I want to be able to use RDP at the remote site, but need the DRDA server
> connection.
>
> Thanks,
>
> Jeff Young
> Sr. Programmer Analyst
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.