Good summary, Bill. I played around again tonight and just can't figure it out. I agree with you at this point . . . some sort of DXB and NIU configuration quirk that prohibits the logon process to complete sucessfully. The problem is you can not see a trace of the DXB logon process to see what is going on and where it is failing. It was a good try by all.
Jim, W3BG ----- Original Message ----- From: "FireBrick" <[EMAIL PROTECTED]> To: "DXBase List" <[email protected]> Sent: Wednesday, June 12, 2002 1:14 PM Subject: [DXBase] W9NIU node failure info > I appreciate all the members who have helped and made suggestions. > In an attempt to summarize all that we have tried, I'm posting this clues. > Somewhere is the clue to unravel this. > It's something simple I'm sure. > But I've just about exhausted my ideas. > I've tried the following formats, all created with DXB's Modify Hosts File > feature. > Please note there are two different addresses. > 132 is the Old Node, 135 is the CLX node > > 131.156.2.132 W9NIU #Pav > connects me to the OLD Pavilion version of W9NIU > If the address is 131.156.2.132 # W9NIU, I can NOT connect. I must remove > the # character. > > 131.156.2.135:41112 w9niu > 131.156.2.135:41112#w9niu > 131.156.2.135:41112 #w9niu > 131.156.2.135:41112 # w9niu > 131.156.2.135:41112 W9NIU > 131.156.2.135:41112#W9NIU > 131.156.2.135:41112 #W9NIU > 131.156.2.135:41112 # W9NIU > All the above get the two error messages, "could not connect" & "Packet Comm > Mgr init failed" > > 131.156.2.135 41112 > The above does NOT get any error messages and a inet packet window appears > but there is no connection or activity which is reasonable as there was no > login request for DXB to act upon. > > Neither W9NIU IP numbers have 'Literal' DNS names as they are not > 'registered'. > So only a IP number can be used. > > k3nc.no-ip.com:41112 # K3NC works instantly. So the port does not appear to > be the issue. > > If I use DXTelnet to connect to the new W9NIU CLX cluster, I get instant > connection. So I must assume it's not my computer nor internet connection. > If I use Windows XP applet HyperTerminal, I get instant connection. > > So in summary > DXB and/or Packet Com Mngr seem to have an issue with the NIU IP numbers or > format as evidenced by the necessity to remove the # character for the > Pavilion version. > As one IP will work with the Pavilion node and the other IP will not work > with the CLX node, I'm guessing it has nothing to do with the > nonregistration of the two IP numbers. They don't need a Literal address. > DXB and/or Packet Com Mngr seem to have an issue with the NIU IP numbers > when a port number is included. But the K3NC node does not have a problem. > The DXB login system works correctly for other nodes whether CLX, Spider, > ARC, or Pavilion. > Can this be an issue with the font used? > > I'm thoroughly stumped after spending quite a few hours investigating this > every way I can think of. > > ------------------------------------------------------------ > All things are possible except skiing through a revolving door. > ------------------------------------------------------------ > > Bill H. in Chicagoland > [EMAIL PROTECTED] > > > > _______________________________________________ > DXBase Reflector - Please visit us on the web at www.dxbase.com > - - - - - - - - - - - - - - - - - - - - - - - > To UNSUBSCRIBE please visit: > http://mailman.qth.net/mailman/listinfo/dxbase
