|
The Windows firewall is not running, but the AVG firewall is. I'mutility.
still waiting for word from the network guy to get back to me about it
- good luck on that.
There are exit points registered, but these look like system programs
(QTVADDP and QTVRMVP in QSYS); both were created by user *IBM on 7
December
2000 (Pearl Harbor Day; is that ominous?).
I reset the system values, but there was no love. Neither QHST nor
the job logs showed any entries for the period.
Jerry C. Adams
IBM i Programmer/Analyst
I don't feel we did wrong in taking this great country away from [the
Indians]. There were great numbers of people who needed new land and
the Indians were selfishly trying to keep it for themselves. - John
Wayne
--
A&K Wholesale
Murfreesboro, TN
615-867-5070
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jim Franz
Sent: Friday, March 09, 2012 2:48 PM
To: Midrange Systems Technical Discussion
Subject: Re: Remote Site Cannot Connect
Since this seems to be the only pc having the problem, check these (if
you have not already) 1. the firewall/router at the remote site (you
have said the other sites ok, so your local firewall most likely ok
unless only handling certain ports from that remote site. An earlier
post had the list of ports.
2. is Win firewall on in this pc?
after verifying 1& 2& still issue
3. turn on autocfg& #virt +1 just for a moment to see if it scratches
your device& re-creates.
4. if still an issue - what qhst entries created during the attempt
(dsplog qhst for time frame) we are assuming since not previously
mention - no telnet exit pgm (wrkreginf ).
Also check joblog info in qtvdevice and qtvtelnet jobs
keep us posted
Jim Franz
----- Original Message -----
From: "Charles Wilt"<charles.wilt@xxxxxxxxx>
To: "Midrange Systems Technical Discussion"<midrange-l@xxxxxxxxxxxx>
Sent: Friday, March 09, 2012 3:18 PM
Subject: Re: Remote Site Cannot Connect
Have you checked to make sure that there isn't a currently active
session with the ID of the session you're trying to connect with?
Perhaps the user didn't signoff before closing the session.
Also, I assume you checked that the session ID being used it still
what you expect.
Either case would prevent just the emulator from connecting....though
I think you should have seen a different error than the one you
originally mentioned.
Charles
On Fri, Mar 9, 2012 at 10:10 AM, Jerry C. Adams<midrange@xxxxxxxx> wrote:
I just got off of the site (VNC) and brought up iSeries Navigator (V5R4).
Ran the Verify Connection... and everything, including Telnet verified.
Still get the same error when trying to start the PC5250 process.
Re-installing is an option. Still waiting for the network guy to see
what he can do, if anything. I'll check the SP level.
An additional note: Until a couple of weeks ago all of our remote
connections were connecting through system-generated session ids. I
re-configured (and tested!) all sessions (local and remote) to have
specific ids. I set the QAUTOCFG value to '0' (Off) and QAUTOVRT to
'0' (zilch). I re-tested all remote sessions after that; they all
worked.
Jerry C. Adams
IBM i Programmer/Analyst
More people are kicked to death by donkeys than die in aircraft
accidents. - Encyclopedia of Useless Information (Personally I don't
find this useless at all; just another reason to avoid jackasses.)
--
A&K Wholesale
Murfreesboro, TN
615-867-5070
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of John Jones
Sent: Thursday, March 08, 2012 2:28 PM
To: Midrange Systems Technical Discussion
Subject: Re: Remote Site Cannot Connect
You said data transfer works. Do other aspects of Client/iSeries
Access like iNav work, i.e. everything but PC5250?
Have you considered uninstalling/reinstalling iSeries Access and
making sure the latest SP is installed?
On Thu, Mar 8, 2012 at 12:16 PM, Gary Thompson
<gthompson@xxxxxxxxxxx>wrote:
He wants a double latte with whipped cream?
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:
midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jerry C. Adams
Sent: Thursday, March 08, 2012 11:14 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Remote Site Cannot Connect
I have verified the connection from the client using the cwbping
means.Everything, including Telnet, verifies. I have connected to ourtelnet port (23).
system from the client using Telnet from within the DOS command
window; I get a signon panel.
They can run the Data Transfer process. The only difference
(port-wise) is that it uses the database port (8471) rather than the
I re-booted the PC; still no love.
I asked the network guy to check out the firewall and anything else
he could think of. He'll get around to it when he can - whatever that
http://archive.midrange.com/midrange-l.
Jerry C. Adams
IBM i Programmer/Analyst
I'd like to be a pitcher. You have four days off to play golf.
That's a dream job. -Tiger Woods
--
A&K Wholesale
Murfreesboro, TN
615-867-5070
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Chris Bipes
Sent: Thursday, March 08, 2012 11:29 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Remote Site Cannot Connect
Have you run a NETSTAT *CNN to see if the remote site is connecting?
If you see the telnet connection but they never get a sign on
screen, it is on the client side or the network in between. If the
telnet connections never hits, then it is one of the other servers
that they are not reaching. Have you verified your connection
settings as far as when to look up the IP address and/or port?
--
Chris Bipes
Director of Information Services
CrossCheck, Inc.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jerry C. Adams
Sent: Thursday, March 08, 2012 8:57 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Remote Site Cannot Connect
Kirk,
I think something was lost in either the thread or in my thoughts.
The user cannot signon at the remote site because they cannot get
the
PC5250 session to connect to our system. I.e., no signon panel. So,
unless I'm losing it (another distinct possibility), the job
description is not germane.
--
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.
--
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.
--
John Jones, CISSP
--
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
--
--
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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.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 on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
