Hello Daryl.

23 Jan 16 12:58, you wrote to all:

 DS>   I have had this problem for several years, and have no idea what is
 DS> going on.

 DS>   While I can connect to other nodes via Internet Rex, they can NOT
 DS> connect to my system.



 DS>   Any assistance would be appreciated.

Well,if I do a ping and Traceroute of wx1der.dyndns.org which is the FQDN
associated with
1:19/33 I get the following:

Pinging wx1der.dyndns.org [71.238.220.235] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 71.238.220.235:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

A trace route to wx1der.dyndns.org [71.238.220.235] over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  65.103.38.174
  2     6 ms     7 ms    10 ms  stpl-dsl-gw12.stpl.qwest.net [207.109.2.12]
  3     7 ms    14 ms    11 ms  stpl-agw1.inet.qwest.net [207.109.3.89]
  4    11 ms    11 ms     *     chp-edge-01.inet.qwest.net [67.14.38.90]
  5    17 ms    11 ms    12 ms  216.207.8.190
  6    31 ms    30 ms    29 ms 
hu-0-2-0-7-cr02.350ecermak.il.ibone.comcast.net [68.86.83.161]
  7    11 ms    15 ms    14 ms  be-10405-cr02.chicago.il.ibone.comcast.net
[68.86.87.185]
  8    48 ms    48 ms    32 ms 
be-10414-cr02.56marietta.ga.ibone.comcast.net [68.86.86.246]
  9    28 ms    30 ms    28 ms 
be-7922-ar03.littlerock.ar.lrock.comcast.net [68.86.90.162]
 10    36 ms    35 ms    30 ms 
te-8-1-ur01.sshackleford.ar.lrock.comcast.net [68.87.223.166]
 11    33 ms    32 ms    33 ms 
te-1-0-0-ten01.sshackleford.ar.lrock.comcast.net [68.85.132.138]
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.

 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Trace complete.

So... I suspect that the connection problem isn't related to Irex


Jeff

--- GoldED+/W32-MINGW 1.1.5-b20070503