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