SCOUG Logo


Next Meeting: Sat, TBD
Meeting Directions


Be a Member
Join SCOUG

Navigation:


Help with Searching

20 Most Recent Documents
Search Archives
Index by date, title, author, category.


Features:

Mr. Know-It-All
Ink
Download!










SCOUG:

Home

Email Lists

SIGs (Internet, General Interest, Programming, Network, more..)

Online Chats

Business

Past Presentations

Credits

Submissions

Contact SCOUG

Copyright SCOUG



warp expowest
Pictures from Sept. 1999

The views expressed in articles on this site are those of their authors.

warptech
SCOUG was there!


Copyright 1998-2024, 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.

The Southern California OS/2 User Group
USA

SCOUG-HELP Mailing List Archives

Return to [ 08 | May | 2004 ]

>> Next Message >>


Date: Sat, 8 May 2004 00:39:30 PDT7
From: Steve Schiffman <schiffman@attglobal.net >
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: Peer Network Problems...

Content Type: text/plain

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

Gary Granat wrote:
>
> I did as suggested -- in fact, had determined that I would do so before your
> note arrived -- and I now have a functioning peer network running OS/2.

Good. Now we can work on figuring out why the Linksys PCcard is not working.

> According to their information, a failure to autosense can be caused by a cable
> that doesn't conform to the 568B cabling standard. I'm pursuing that line of
> inquiry and my try ordering a better cable, although the one I am using was
> purchased new just a couple of days ago. According to the package, it is a "7'
> 350MHz CAT5e UTP CABLE".

Your lan cable is probably not the problem. You have the latest and
greatest, and if it was sold as a lan cable, it is has the correct
standard, particularly since it lists the cable as CAT5e. But just in case
the new cable has a bad connector termination, try using the previous lan
cable you were using. The previous cable should work just fine.

I just re-read your post (first paragraph above) and unless you changed
the lan cable from the new cable to the previous one when you re-installed
the EtherJet PC card, the new cable is just fine.

Steve Schiffman

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

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

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


>> Next Message >>

Return to [ 08 | May | 2004 ]



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.