MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » November 2012

Re: Connect to remote system DRDA port



fixed

Thanks Dan.
The telent did fail.
The customer does indeed have the i on a private network but is using a
public ip address.

Now that I know what the issue is, I can look for a solution.

My thanks to all who responded.


On Tue, Nov 20, 2012 at 1:41 PM, Dan Kimmel <dkimmel@xxxxxxxxxxxxxxx> wrote:

Jeff,

You say there's no firewall between you and the system, but something is
definitly blocking port 446 on that i.

Port 446 is often blocked in the router that connects a private network to
the public internet as it is a common target for DOS attacks. It may be
blocked by the internet service provider.

If you have XP on your PC, try running telnet from a command line as
follows:

telnet 124.xxx.xxx.xxx 446

It'll either connect or it won't.

Dan Kimmel

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:
midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jeff Young
Sent: Tuesday, November 20, 2012 11:58 AM
To: Midrange Systems Technical Discussion
Subject: Re: Connect to remote system DRDA port

I have tried deleting the connection in RDP and creating it again with the
same results.
When I create the connection in iAccess and use the Verify Connection
function, it fails on the DRDA server connection.

As I said, I am not connecting between i systems, only using RDP, iAccess
Emulator and Quantum Plugin.

Everything except RPD connects just fine.
RDP errors out with required host server not started.

As I indicated in my first post, all of the host servers are started and
show as listening in Netstat.


On Tue, Nov 20, 2012 at 12:10 PM, Monnier, Gary <Gary.Monnier@xxxxxxxxx
wrote:

Can you connect to another i system using STRSQL from the one in
question or does the connection fail?

Have you tried deleting the remote system connection and recreating it?

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:
midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jeff Young
Sent: Tuesday, November 20, 2012 6:50 AM
To: Midrange Systems Technical Discussion
Subject: Re: Connect to remote system DRDA port

Yes.
I have no problem connecting from my pc with anything other than RDP
which appears to need the DRDA port.

I am not attempting to connect from another i system.

On Mon, Nov 19, 2012 at 5:58 PM, Monnier, Gary <Gary.Monnier@xxxxxxxxx
wrote:

Ok. One more thing to check...

Is there a host table entry for the i in question (CFGTCP opt 10)?

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:
midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jeff Young
Sent: Monday, November 19, 2012 12:55 PM
To: Midrange Systems Technical Discussion
Subject: Re: Connect to remote system DRDA port

I can connect from my PC using the Quantum Plugin for RDP with no
problems.
The only problem I have is that since (for whatever reason) Verify
Connection say the it timed out trying to connect to the DRDA server
and since it does not see the DRDA server, RDP will not let me
access the system.


On Mon, Nov 19, 2012 at 3:38 PM, Monnier, Gary
<Gary.Monnier@xxxxxxxxx
wrote:

Can you use STRSQL from the system in question to connect to a
different system and vise versa?

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:
midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jeff Young
Sent: Friday, November 09, 2012 9:20 AM
To: Midrange Systems Technical Discussion
Subject: Re: Connect to remote system DRDA port

Other systems at different clients.
Some at V5R4, Some at V6R1, Some at V7R1.

Problem is at this specific client only.

On Fri, Nov 9, 2012 at 9:45 AM, Jack Kingsley
<iseriesflorida@xxxxxxxxx
wrote:

Are the other systems on 7.1?? Are they local to the same
system that won't connect. Did it ever work before.

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

Remote system on V7R1. Not sure of PTF level.
Local PC running Windows XP Pro latest service pack.

When connecting to other systems using VPN and running release
5.4 to
7.1 I
have no problem.




On Fri, Nov 9, 2012 at 9:38 AM, Jack Kingsley
<iseriesflorida@xxxxxxxxx
wrote:

Are you current on INAV ptf's, windows7??

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.


--
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.




--
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.


--
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.




--
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.

--
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.




--
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.

--
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.




--
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.

--
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.




--
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.



--
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.









Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot COM and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available here. If you have questions about this, please contact