× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. March 2015

RE: TCP Port question

Really all they need to do is reset the service listening on port 77, not
the whole box.

--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of John
R. Smith, Jr.
Sent: Thursday, March 12, 2015 12:49 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: TCP Port question

They know what the server and it is actively talking to other clients on
other ports. It seems to be 100% iSeries or port 77 unless something burped
on the server and it won't talk on port 77 but will talk on the rest. I'll
see if they can get a clean window to reboot it but I will probably have the
new logging in place before a reboot happens.

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jim
Oberholtzer
Sent: Thursday, March 12, 2015 1:34 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: TCP Port question

Ohhh...

That's a horse of a different color; the server on the remote side is not
responding so therefore it needs to be reset. Unfortunately unless it's
documented somewhere about what server it is you might have some interesting
moments trying to find it.

Can you ping the IP address? If so add the -a parm to the ping so it will
report its name. That might help narrow it down.

--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of John
R. Smith, Jr.
Sent: Thursday, March 12, 2015 12:07 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: TCP Port question

I'm afraid my wording confused things. The "server" is a unix or Windows
server (not sure of their config) that is listening/waiting for the iSeries
to connection on port 77. When they execute the program on the iSeries for
the client to start talking on port 77, it returns an error saying that it
can't connect to the server on port 77. The client program on the iSeries
is a manual call and not part of the IPL startup.

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jim
Oberholtzer
Sent: Thursday, March 12, 2015 12:54 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: TCP Port question

Then you are looking for a program that is not running and either A) failed
in the startup program, or B) was not there to start with.

I'd look at the job log for the startup program and the history log. Look
at the jobs ending as the IPL started and you might catch the job that
actually was listening on that port.

--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of John
R. Smith, Jr.
Sent: Thursday, March 12, 2015 11:42 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: TCP Port question

The port number is 77. Both the client and the server programs are
completely custom.

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jim
Oberholtzer
Sent: Thursday, March 12, 2015 11:37 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: TCP Port question

Gary's correct, check to be sure the host servers started, but I suspect
there is a different server you need started.

What port are you looking for? Is it a well-known port or a custom port?

If it's a custom port you might start by looking to see if all of the WAS,
PHP and/or Apache instances started properly. Check the /www directory for
any apache instances that listen on a custom port.

Should the IWS start?

--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Gary
Thompson
Sent: Thursday, March 12, 2015 10:32 AM
To: Midrange Systems Technical Discussion
Subject: RE: TCP Port question

Are TCP services running on the re-started iSeries ?

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of John
R. Smith, Jr.
Sent: Thursday, March 12, 2015 9:30 AM
To: midrange-l@xxxxxxxxxxxx
Subject: TCP Port question

I have a client that is running a client server system where the iSeries is
a client. When they try to start the job on the iSeries, they are getting a
failure trying to access the specified port. It is my understanding that
the package previously worked and when they did an IPL, it stopped working.
There were supposedly no other configuration changes to the iSeries or the
network. That sounds really strange to me. Unfortunately, at this time I
only have a message that the connection failed. I don't know if it was the
open or the bind or something else that it didn't like. We are adding some
additional logging to the program to try to be a better message than
"connection failed".



In the meantime, I had them do a NETSTAT option 3 and F14 to see the ports
and they said the port in question does not show anything using it. Is
there anything else that anyone can suggest to look at that might show me
what is causing the failure?





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


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


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



As an Amazon Associate we earn from qualifying purchases.

This thread ...
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.