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

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


Date: Sat, 7 Jun 2003 12:52:59 PDT7
From: waynec@linkline.com
Reply-To: scoug-help@scoug.com
To: "Harry Motin" <hmotin@sbcglobal.net >
Subject: SCOUG-Help: LinkSys Router (settings)

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

That's interesting, Harry, your tcpcfg is even sparser than mine, and it
uses the router address as the dns address, which is interesting and may
make sense. Question is which is right.... or does it even matter!!!

Wayne

*************************************************************************

Harry Motin writes:

> On Sat, 7 Jun 2003 03:39:54 PDT7, waynec@linkline.com wrote:
>
>>If I could see how others have configured tcpcfg, it might give me a clue.I
>>think I may have changed my tcpcfg, and I have not changed the LinkSys.
>
>
>
> Wayne,
>
> I have a connection problem, too and I also think it's my tcpcfg.exe setup. I have not
> had the time to research it. On my system my browser and/or E-Mail client sometime
> take a lonnnnnng time to respond. This happens about 50% of the time. Eventually,
> however, the browser or E-Mail client responds. After the first response everything
> thereafter is quick, unless I sit there for a couple of minutes and don't do anything.
>
> The other 50% of the time the response to my first request is quick.
>
>
> With that in mind and my thinking that it's my tcpcfg.exe, here (for what it's worth) is my
> tcpcfg.exe setup:
>
> Network Tab: Enable interface checked; Automatically, using DHCP
>
> Routing Tab: No entries
>
> Hostname: Hostname: I have a hostname defined
> Local domain: pop.sbcglobal.yahoo.com
> Nameserver address: 192.168.0.1
>
> The 192.168.0.1 address is the inside (LAN-side) address of my router/firewall. The
> router is attached to the DSL modem, which in turn connects me to the Internet via my
> ISP. The router feeds all the machines. On this one machine that I use I also have an
> Injoy Pro Firewall
>
> I REALLY would be interested in helping you with your problem, and also getting rid of
> mine. Perhaps inputs from others??????
>
> HCM
>

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

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 [ 07 | 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.