SCOUG-HELP Mailing List Archives

<< Previous Message << >> Next Message >>

Date:	Sun, 30 Jun 2002 16:40:07 PST7
From:	"Steven Levine" <steve53@earthlink.net >
Reply-To:	scoug-help@scoug.com
To:	scoug-help@scoug.com
Subject:	SCOUG-Help: eComStationary Network

=====================================================
If you are responding to someone asking for help who
may not be a member of this list, be sure to use the
REPLY TO ALL feature of your email program.
=====================================================

In <200206281356201.SM01204@66-81-28-174-modem.o1.com>, on 06/28/02
at 12:56 PM, Michael Rakijas said:

>I will try to do that shortly but I have a hard time believing it to be
>InJoy related. Considering that every other computer in the house is

You may be right. I'm just making suggestions.

>One thing I've been focusing on is the TCP settings. I used the other
>OS/2 machines on the network as the model for the setting on the eCS
>machine. Unfortunately, the eCS Java I/F settings dialog doesn't allow me
>to quite get the settings to look identical to the native TCP/IP config
>box of the OS/2 machines.

Did you make sure that protocol and resources got installed to \mptn\etc.
This is a known and documented eCS install defect. However, I don't think
that this will cause Netscape to fail, because it is non-standand in that
it ignores these files.

>Generically, the settings for the machines on the network should be like
>the eCS settings of the target box below (only pertinent values are
>included, non mentioned ones are blank):

>However, all the OS/2 boxes have a net mask in the "net" route of
>255.255.255.0 (setting number 2 in routes). The eCS box doesn't allow
>such a setting. If you add a "net" route manually, it expects a 4 number
>IP address (most likely 192.168.1.1) compared to the 3 number set
>(192.168.1) of the OS/2 boxes. If you create the "net" route

This is just a user interface change. 192.168.1 and 192.168.1.0 are
different ways of entering the same name.

If you continue to have troubles with this, let me see:

setup.cmd
protocol.ini
lantran.log

>Do you have any other ideas? Otherwise, I guess I have to do IP tracing
>on the InJoy gateway machine and I'm not sure what I'll be looking at -

You are looking for packets coming from the eCS machine. You will verify
that Injoy sends them out and that Injoy passes the return packets back to
the eCS machines. Some of this you can do with iptrace. Some of this you
will have to do with Injoy because Injoy does not define the ppp
interface, so iptrace does not know how to trace it. netstat -n will show
you the name of interface the Injoy defines. You could try:

iptrace xxx

where xxx is the Injoy interface. It might work. I don't know.

Steven

--
---------------------------------------------------------------------
"Steven Levine" MR2/ICE 2.31a #10183 Warp4/FP15/14.085_W4
www.scoug.com irc.webbnet.org #scoug (Wed 7pm PST)
---------------------------------------------------------------------

=====================================================

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".

=====================================================

Return to [ 30 | June | 2002 ]

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.