SCOUG-HELP Mailing List Archives

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

Date:	Tue, 13 Feb 2001 09:44:32 PST
From:	sshapiro@ucsd.edu (Sandy Shapiro)
Reply-To:	scoug-help@scoug.com
To:	scoug-help@scoug.com
Subject:	SCOUG-Help: Re: DSL question

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

Something in my desktop OS/2 is broken.

I have exactly the same TCPIP settings in both my laptop and desktop, and
the same level of fixpack from the Aug. 2000 Warpup CD in both computers.

The laptop talks to the Linksys router fine -- no problems.

The desktop also talks to the Linksys router under Windows, but not under
OS/2.

I can't even ping the router from the desktop OS/2 (although I can under
Windows).

When I "enable interface automatically using DHCP" in TCPIP settings: it
works fine on the laptop, but on the desktop it gives an error on bootup:
"DHCP Start: DHCP client did not get parameters."

The Setup.cmd file is exactly the same in the two computers.
Both are at MPTS 5.5 level.

There must be some way to trouble shoot this.

Any suggestions are very much appreciated.

Sandy

>There may be an issue related to your OS/2 and TCP/IP fixpak levels. One
>of my PCs is Warp 4 FP12, and two others are MCP. They're all talking
>with no problems and all see the router/switch without entering anything
>in the the routing page (contrary to advice I saw somewhere else).
>However, you might try entering the LinkSys address (192,168.1.1) as the
>destination on the router page, with 255.25.255.0 as subnet mask. The
>DHCP monitor (in System Setup) shows the connections and details. A
>LinkSys representative at a recent SCOUG meeting was unable to establish
>a connection to a LinkSys router, and some suggested that this problem
>would be fixed by installing a fix to TCP/IP or MPTN, or upgrading the
>LinkSys program? If you can't load the LinkSys configuration pages by
>entering 192.168.1.1 in Netscape from one of your computers, but can from
>another somthing is probably (I have to hedge 'cause I really don't know)
>wrong in that PC.
>for Peer to peer you also need the netbios protocol, but if the two
>computers are communicating when connected with a cross over cable, net
>bios must be installed ok.

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

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 [ 13 | February | 2001 ]

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.