said:
[...snip...]
>>the only eCS machine of the bunch. All machines on the network use my
>>one main machine as an Internet gateway. The gateway machine has InJoy
>>running on it which provides NAT services to all others via dialup.
>
>To further refresh folks memory, the core problem appears to be that when
>the responses come back from the server, they are discarded either by the
>gateway machine or the eCS box. This is hard to say for sure which one
>until we run parallel iptraces on both machines and compare the outs and
>ins.
True. And this is the direction in which I was going, setting up a separate eCS machine as an experimental control.
[...snip...]
>pings are fun, but they are not a definitive test of connectivity. Many
>sites do not respond to pings these days. You can thank hackers for this.
>If you get a response to ping, that's fine. If not, you have to fall back
>to tracerte or telnet to really know if the site is responsing.
I guess I kind figured that as the only possible explanation. It's unfortunate because it's a useful quickie debug tool.
>>[C:\]nslookup yahoo.com
>>Server: ns1.oco.net*** Can't allocate memory
>> 216.171.167.11
>
>This is an ISP problem.
>
>>Exception = c0000005 occurred at EIP = 1f02a60b.
>>SYS1808:
>>The process has stopped. The software diagnostic
>>code (exception code) is 0005.
>
>This is a TCP/IP software problem. You probably need to apply a MPTS or
>TCP/IP FP.
>
>> I went to another Warp 4 machine and the nslookup behaved there
>>similarly. I seem to remember that something in an update (TCPIP? MPTS?)
>>trashed my nslookup. Since I configure all my machines similarly, it's
>>probably trashed everywhere except the eCS machine. What nslookup should
>>I be using? Where can I find it? Should I use the one from eCS? Thanks.
>
>Use any nslookup to works. What's inetver say on the boxes with the
>failing nslookup.
>
>I forget. Did you ever apply the MPTS and TCP/IP fixes from
>www.ecomstation.com to eCS?
The nslookup that failed was on the gateway machine and another similarly configured Warp 4 machine with MPTS WR8610 and WR8621 and TCP/IP fix UN0980. The gateway machine also had stack fix IC27255 to fix the redial trap for InJoy. nslookup works properly on the eCS machine but that machine has had no fixes applied to it yet. Where do I get a working nslookup and what support files are needed, if any?
As a further debug step, last night, I had finally gotten the added eCS machine up and running. It's too early to say completely because I haven't much of a shakedown with it yet, but it looks to be a full network participant on my home network with none of the ailments plaguing the objective machine. It might take a few days to get back to it again but the indication seems to be that it is a configuration problem with the objective machine. More to come...
>Steven
-Rocky
________________________________________________________________
Sent via Orange County Online's WebMail System at oco.net
=====================================================
To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".
For problems, contact the list owner at
"rollin@scoug.com".
=====================================================
<< Previous Message <<
>> Next Message >>
Return to [ 13 |
January |
2003 ]
The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA
Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS
RESERVED.
SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group.
OS/2, Workplace Shell, and IBM are registered trademarks of International
Business Machines Corporation.
All other trademarks remain the property of their respective owners.