|
Possibly but I'd like the test with TELNET or FTP to the specific
address (do not use the host name) to discover how that reacts.
So TELNET xxx.xxx.xxx.xxx and see how that reacts. You might try FTP too.
If they work the problem is most likely a simple one in the host table
and/or Relational Database Directory Entry. If they do not work it's
likely the router/firewall is the issue.
--
Jim Oberholtzer
Agile Technology Architects
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Rob Dixon
Sent: Tuesday, April 26, 2016 8:28 AM
To: Midrange Systems Technical Discussion
Subject: Re: FTP problem
Jim,
Many thanks.
As I said, I can ping the internal adress. Could it be a port problem
blocked by the router?
Rob
<
https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_c
ampai
gn=sig-email&utm_content=webmail>
Virus-free.
www.avast.com
<
https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_c
ampai
gn=sig-email&utm_content=webmail>
<#DDB4FAA8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
On 26 April 2016 at 14:14, Jim Oberholtzer
<midrangel@xxxxxxxxxxxxxxxxx>
wrote:
Another thing to consider. Ping uses UDP not TCP. If there was arouter/firewall.
router/firewall change, is it blocking or not routing the TCP and
allowing the UDP through?
For grins try TELNET (or FTP for that matter) to the specific
address, not to the host name. If that works it's not the
http://archive.midrange.com/midrange-l.
--
Jim Oberholtzer
Agile Technology Architects
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf
Of Glenn Gundermann
Sent: Tuesday, April 26, 2016 8:11 AM
To: Midrange Systems Technical Discussion
Subject: Re: FTP problem
I wish I knew more in this area but here goes ...
The Change TCP/IP Domain (CHGTCPDMN) shows the IP address of your
domain name server.
Is this still correct?
If it is correct and you can reach the domain name server, does the
domain name server know about 'myhostname'?
Yours truly,
Glenn Gundermann
Email: glenn.gundermann@xxxxxxxxx
Work: (416) 675-9200 ext. 89224
Cell: (416) 317-3144
On 26 April 2016 at 09:05, Rob Dixon <robertsdixon@xxxxxxxxx> wrote:
I recently had to change a router and this has caused a variety of--
problems.
I changed the RDB entries on a V5R1 server to reflect a new
internal IP address for a V5R2 server on the same network, but
when I execute the command STRTCPFTP on the V5R1 server and enter
the RDB name for the V5R2 server, I get
TCP101A - cannot find 'myhostname'.
Yet I can ping the internal address stored in the RDB definition
for the
V5R2 server without problem, both from Windows and using the ping
command on the V5R1 machine.
I wonder (ignorantly!) if the problem is with the router
configuration (which I didn't set up).
All help gratefully received.
many thanks
Rob Dixon
--
Rob Dixon
www.erros.co.uk
www.boarstall.com
<
https://www.avast.com/sig-email?utm_medium=email&utm_source=link&u
tm _c ampaign=sig-email&utm_content=webmail
Virus-free.
www.avast.com
<
https://www.avast.com/sig-email?utm_medium=email&utm_source=link&u
tm _c ampaign=sig-email&utm_content=webmail
<#DDB4FAA8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
--
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.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
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
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
--
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.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
--
Rob Dixon
www.erros.co.uk
www.boarstall.com
--
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.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
--
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.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
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
