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



The i is sitting about 18" to my left.

Even though I'm not a network guy like you, Larry, Jim, I agree completely
about the location of the DNS. Every other place at which I have worked the
DNS was sitting on a PC server. Never had an issue. But I have no control
over this scenario (I am, though, now counting the days to retirement).

Pubwp.comcast.net is some server on Comcast's network.

Unfortunately, we do contract with a local network "guru" - the boss's son.
Which might explain why, even though I'm not allowed to make changes, I'm
the one that gets hammered when things like this happen. (One day
closer...)

Jerry C. Adams
IBM i Programmer/Analyst
There are two theories on hitting the knuckleball. Unfortunately, neither
of them works. -Charlie Lau
--
A&K Wholesale
Murfreesboro, TN
615-867-5070


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Monday, February 13, 2012 12:37 PM
To: Midrange Systems Technical Discussion
Subject: RE: Can't Connect

First of all, is your PC in the same location as your i? I ask that because
I think the address for your i begins with 173 and your PC begins with 192.
In NETSTAT *IFC the non 127 number should be your i's address.

You're having comcast perform all your DNS? That's questionable. You
should have a local dns. This can be either your i or some PC server.
Actually you should have multiple DNS servers in case one is down. You
don't have any listed except comcast. A local dns can then be set up to go
out to find outside addresses on comcast. For example if I lookup GDIHQ it
finds it in my local dns and when I look for nra.org the local dns says go
check my internet provider.

And, is the name of your i really pubwp.comcast.net? Because if it isn't,
you have some strange set up.

It looks like your pc isn't in your dns either.

Frankly, I'd contract with some local network guru to come in and take a
look. Your Statement Of Work should have him set up 2 DNS servers and have
them go through your internet provider for connection to outside addresses.
Then I'd have him ensure that all your PC's use these dns servers. (They
may also be your DHCP servers). Ask him for the IP addresses used by these
DNS servers and put them into CFGTCP, 12.


Rob Berendt
--
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: "Jerry C. Adams" <midrange@xxxxxxxx>
To: "'Midrange Systems Technical Discussion'"
<midrange-l@xxxxxxxxxxxx>,
Date: 02/13/2012 12:47 PM
Subject: RE: Can't Connect
Sent by: midrange-l-bounces@xxxxxxxxxxxx



1. PC PING to i by name:
Timed-out
2. nslookup on static IP address:
Server: wp.comcast.net
Address: 10.1.10.1
Name: pubwp.comcast.net
Address: 173.xxx.xx.xxx
3. pc IPCONFIG:
Address: 192.168.1.101
4. nslookup 192.168.1.101
Wp.comcast.net can't find 192.168.1.101: Non-existent
domain
5. PING '127.0.0.1'
Made the round trip
6. Change TCP/IP domain information
Domain name server
Internet addresses: *NONE
7. System i PING by name:
Verifying connection....
Cannot reach remote system

In the meantime got Comcast support on the line. The gentleman said that
addresses from xxxxxxx.xx1 - xxxxxxx.xx6 were configured on their modem (I
was unclear whether he had to add any of these or not), and he re-booted
the
modem. He told me that the xx1 address, which is the one that identifies
our System i was not showing as being connected to any device.

Jerry C. Adams
IBM i Programmer/Analyst
--
A&K Wholesale
Murfreesboro, TN
615-867-5070


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Monday, February 13, 2012 10:33 AM
To: Midrange Systems Technical Discussion
Subject: Re: Can't Connect

From your PC can you do a ping of your i by name?
C:\>ping gdihq
Pinging gdihq.dekko-1 [10.17.6.33] with 32 bytes of data:
Reply from 10.17.6.33: bytes=32 time=1ms TTL=58 If not, does it at
least
return the IP address?
Pinging gdihq.dekko-1 [10.17.6.33] with 32 bytes of data:
This tells us that your PC can look it up by name and either your DNS or
host table entry on your PC is working.
On your PC if you take that IP address and do this
C:\>nslookup 10.17.6.33
Server: gdsdns.dekko-1
Address: 10.10.4.250
Name: gdihq.dekko.com
Address: 10.17.6.33
do you get similar results? This will tell us that your DNS is working.
On your PC do this:
C:\>ipconfig
Record what you get for
IP Address. . : 10.10.8.237
Do a
C:\>nslookup 10.10.8.237
Server: gdsdns.dekko-1
Address: 10.10.4.250
Name: gdsl61.dekko-1
Address: 10.10.8.237
Record your pc's name, sample gdsl61.

From your i do this:
CFGTCP
CALL QCMD
PING '127.0.0.1'
This will tell us your TCPIP stack is working on your i.
From your i do this:
CFGTCP
12. Change TCP/IP domain information
Page down
Record the address(es) you show for Domain name server. Sample
10.10.1.240
CALL QCMD
PING '10.10.1.240'
Verifying connection to host system 10.10.1.240.
PING reply 1 from 10.10.1.240 took 4 ms. 256 bytes. TTL 59.
This will tell us if your i is communicating to your dns. If you press
enter on the CFGTCP,12 screen it will flush your dns cache. Probably a
good
thing to do.
Now do this:
CALL QCMD
PING GDSL61
Verifying connection to host system GDSL61.dekko-1 at address
10.10.8.237.
PING reply 1 from 10.10.8.237 took 10 ms. 256 bytes. TTL 123.
Does it at least get the
Verifying connection to host system GDSL61.dekko-1 at address
10.10.8.237.
This will tell us that your i can communicate to your dns and perform name
resolution. If instead of the "Verifying..." you get "Unknown host" your
i
may not be getting dns resolution. But checking your typing is a good
idea
also.
If dns resolution works but
PING reply 1 from 10.10.8.237 took 10 ms. 256 bytes. TTL 123.
doesn't that tells us that your dns resolution is working but it can't
communicate to your PC. Might be a router issue.
Keep us posted.

Rob Berendt
--
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: "Jerry C. Adams" <midrange@xxxxxxxx>
To: "Midrange-L" <midrange-l@xxxxxxxxxxxx>,
Date: 02/13/2012 10:22 AM
Subject: Can't Connect
Sent by: midrange-l-bounces@xxxxxxxxxxxx



On V5R1 and DNS sitting at Comcast.net.



All day Friday we lost internet connection. Web browsing and email were
not
existent; connections to the System i via iSeries Access for Windows were
down. Only twinax devices (displays and printers) worked.



This morning, when I came in there was an error message (CPA58EE - Line
Ethernet failed) to which I replied 'R'. iSeries Access could then
connect,
and I was working fine from my PC. Remote locations could signon.



Comcast came out this morning to work on it. Now browsing and email work,
but iSeries Access connections (local and remote) do not. In WRKCFGSTS
*LIN
the Ethernet is showing "Active".



I have since gotten the CPA58EE error three more times, and replied 'R';
once that failed but the next retry seemed to take



Obviously I'm missing something else, but what?



In Work with TCP Interfaces and Routes only the specific IP address (plus
the Loopback) are defined. For local connection could I add a 10.0.0.xxx
IP
address and change the iSeries Access connections to use that address
rather
than the 173.xx.xx.xx address? This would not help the remote locations,
of
course, so I'm still missing something.



Thanks.



Jerry C. Adams

IBM i Programmer/Analyst

--

A&K Wholesale

Murfreesboro, TN

615-867-5070




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.