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