said:
Bad news, good news and a little more bad news - bad news first. I don't think
I'm going to be delving too much more into iptrace and netstat -n for the time
being because I think I'm closing in on the problem. That's the good news -
I've been able to improve things considerably by futzing with the setup.cmd
file. That leaves a little bit of a problem - I don't think it's completely
fixed (the little more bad news). Read on.
> A couple of comments. setup.cmd contains:
>
> route add default 192.168.1.1 -hopcount 1
> route add -net 192.168.1 192.168.1.1 -hopcount 1
>
> The second one is redundant and should be deleted. You are already
> sending packets with an otherwise unknown routing to 192.168.1.1
Based on my experience and what I have done to this point, I had trouble with
this idea. These are the two paths for the IP traffic that are added as
directed by InJoy. Since I have a number of machines that already work as
configured with InJoy in mind, I decided to look at another one as a model. Two
similar paths are defined on it except with the following syntax:
route add default 192.168.1.1 1 > null
route add net 192.168.1 192.168.1.1 1 netmask 255.255.255.0 > null
I realize the redirection simply dumps into the bottomless bit bucket but the
difference is interesting. I don't know what the dash is in front of net (-net)
on the problem machine is. I assume the 1's are the non-argument-enumerated way
of specifying hopcounts. The added netmask shows what I was asking about the
absence of a netmask earlier (and how I couldn't get it with the TCPIP notebook
on eCS). Just to double check that it wasn't redundant, I REM'ed out the second
line and the behavior didn't change. Then, I added the corrected line (the one
with the netmask) to the eCS machine. Yahoo, Google and other web sites came
right up. I'm not sure it's fully fixed yet because a while later, the kids
complained that it stopped working. Yahoo wouldn't come up anymore and the old
behavior was exhibited again. Since I was on the 'Net on the gateway machine, I
couldn't reboot it but no matter how often I booted the client, it wouldn't come
up anymore (Yahoo came up fine on the gateway machine so it wasn't due to
anything else).
I've replaced both lines now on the eCS machine to the known good syntax but
since it was Bedtime for Bonzos, I won't be able to fully test it for a bit. I
feel a bit uneasy though. Why would the TCP/IP config notebook have gotten
wrong? Is it, in fact, wrong the way it was and the change really fix it? Does
this really explain the difficulty or did a quark go through the system (i.e., a
one time event) that allowed it to work the once I saw it?
Anyway, I've probably got some more experimenting to do. As usual, I would
welcome any recommendations on how to narrow the experimentation tree. Thanks.
> Steven
-Rocky
=====================================================
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 [ 10 |
July |
2002 ]
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.
