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 [ 10 | June | 2003 ]

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


Date: Tue, 10 Jun 2003 11:01:57 PDT7
From: Ray Davison <raydav@charter.net >
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: LinkSys Router (settings), tcpcfg

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

waynec@linkline.com wrote:
>
> Ray Davison writes:
>
>> I have had a Linksys BEFSX41 router and BEFCMU10 modem for a while
>> now. Until this thread I don't believe I had ever entered a URL for
>> either unit. I apparently never had any need to and adjusting
>> security settings was something I never got around to.
>> Is there a data file associated with tcpcfg? You refer to entries.
>> All I can find is TCPCFG.EXE & ICO.
>> Am I missing something?
>
>
> I see now, after looking it up, that the BEFCMU10 is a dsl modem.
DSL/Cable actually, I have cable

> Perhaps it's the rest of us that are trying to configure something that
> doesn't need configuring, Ray.
> Try running tcpcfg.exe and tell us what information is entered on the
> various tabs....

OK, I do know what that TCPCFG is. I didn't recognize it because I have
only selected it from system setup. Basically it is empty. The only
entry I made is to select DHCP, ans I didn't do it there, I selected it
during networking install. I never had to identify my ISP, it found it
on it's own. I have four machines running, have done many installs, and
they always find the ISP.

> If you're curious about the router settings, you can enter "192,168.1.1"
> in the url address field for your browser (where you normally enter
> "http:// www. etc") and you will get a sign-on screen... enter "admin"
> for the sign-on and password, and you'll get a router setup screen from
> the BEFSX41; there you enter info about your ISP (IP address, gateway
> address, dns servers, etc). I suspect you did do that when you installed
> the router.

I know how, I don't think I ever bothered because I didn't need to. I
think "obtain IP automatically" is the default. So, it's just plug it
in, turn it on, and maybe boot it once in a while.

Ray

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

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 | June | 2003 ]



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.