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 [ 21 | November | 2005 ]

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


Date: Mon, 21 Nov 2005 14:40:20 PST8
From: "Michael Rakijas" <mrakijas@adelphia.net >
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: Weird ... incompatibility

Well,

Here's the current status: I did a fresh install on a (fundamentally) new
machine and was having difficulty with what I thought was the network card. I
couldn't access my network in any way, including get an IP address from my
router using DHCP. I thought the driver wasn't really loading because it
seemed so dead. Although the machine could ping itself, this doesn't really
mean much. For those of you who were at the meeting Sat., you saw me bring
that machine it, and it worked fine on the network in the meeting room. Okay,
so that seemed to indicate a physical problem of some sort local to my home
network (although none of the other many machines on this network has this
problem in any way).

So, I went to the end of the cable to which this machine usually connects and
connected my Win (work issued) notebook box and it had no problems (DHCP
address pick up, browsing, etc.). Since the other end of this wire is normally
plugged into a switch which is then plugged into the router that issues IP
addresses on the LAN side of my network (the router has 4 ports and I needed
more), I thought I'd bypass the intermediary (although no other machine seems
to need this) and plug it directly into the router, and there was no change in
behavior.

Now, I'm stumped. I suppose there are a couple of possible alternatives but
I'd like to fix it without having to incur to much in the way of expense. I
suppose, from cheapest to most expensive would be to disable the MB Ethernet
port and install an aftermarket card, or get another router but the latter
solution seems like overkill for one machine on the network.

Any suggestions?

Thanks.

-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
"postmaster@scoug.com".

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


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

Return to [ 21 | November | 2005 ]



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.