Found and I'm stunned as to the pig trail ..

Allan wrote:
> On Sat, 23 Aug 2008 13:03:54 UTC, Mike Luther wrote:
>
>> Cable modem goes to router. Router provides internal IP addresses on connected
>> PC's through DHCP only in this case. For other physical and space reasons in
>> this case, although the router can handle more than one PC, I can't use but one
>> at a time on it. I can fire up either of the two test boxes connected
>> alternately through the same CAT 5 LAN jack alternately, one at a time. Since
>> both are configured for DHCP addressing, they both get different local address
>> numbers as connected. Actually, one is being assigned .106; the other .107 and
>> ping time tests from each one outbound are the same.
>
> The router can usually only be setup to forward all incoming traffic to 1 single IP.
> It looks like your router is setup to route all to .106 - which makes .107 see nothing.
>
> I would try to setup the bad box with fixed IP .106 instead of DHCP, or setup
> the bad box to use the same MAC address as the good box - the the router
> will think it is the same box, and give it same IP.
>
>> And there is no setup issue with the router to block anything different between
>> any computer plugged into it.
>
> It can only send incoming traffic to 1 PC - and it has to know which one.
>
>

It WAS related to the other error in which I was chasing a strange OLE error on
this same bad boy box for SmartSuite update and Lotus 123 applications! If you
read the thread on the OLE error solution, you'll see I finally tracked that
one down to a 'zero' length SOMD database file in \OS2\ETC\DSOM. That was
years ago produced by users at the facility who insisted on working with Lotus
123 on files that were actually on a PEERLAN OS/2 server. They would edit or
work with a file, that was actually at times tried to be worked by two separate
workstations at once, as well as people who would go do this, then walk off
from the bench and just leave the application and file open for even DAYS at a
time. Hard lock country big time.

They'd just flip the power switch multiple times and scream when things didn't
work according to my tech records. Sigh ....

Well, turns out from the research, that even with totally correct SOM.IR files,
it seems that if the SOM operation during the boot run gets hit with a zero
length database file, it can't even update it no matter what! And THAT was the
cause of the whole SmartSuite OLE error mess. As well, memory or thread
errors, whatever, can hurt the TCP/IP game as well, strangely.

Plus, even though UNIMAINT didn't see it, there was huge .INI file corruption
that CHECKINI saw, and in half a dozen passes fixed, except for one curious
OpenDoc error it couldn't fix. Yes. OpenDoc was a SOM based application too
and I have no idea how this one got back into this mess. Which I hand smunched
with UNIMAINT. POOF, back working SmartSuite.

Now this is the crazy part! I took another look at the whole TCP/IP and MPTS
setup game, chose to redo it. Guess what?

Working HHOST application on the Linksys WRT54GL router. Which was set for
routing the port 23 application to the local address it needed to be. But
somehow in all this mess, the box just couldn't see fed to it.

Wow ..

I have another PEER LAN question next. But new thread please.

Thanks to everyone who contributed here. I hope this also can help others.


--


--> Sleep well; OS2's still awake!

Mike Luther