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 [ 01 | March | 2004 ]

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


Date: Mon, 1 Mar 2004 15:36:46 PST8
From: "Steven Levine" <steve53@earthlink.net >
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: netstat -s radius ?

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

In <40437823.586@peterskye.com>, on 03/01/04
at 09:51 AM, Peter Skye said:

>When I ran netstat on the server and it identified a port as a radius
>port, I then looked in my _own_ services file but didn't find it. I
>should have looked at the services file on the server but I thought they
>were identical.

OK, that explains it. It was not clear on which machine you were running
netstat. As I mentioned before I expected netstat to use getservbyport()
API to grab the name for the port. You description of the situation made
it appear that the netstat on your FP10 box was doing something special.
I probably should have known better than to even consider this a
possibility.

>I suppose I should finally upgrade my Fixpak 10. These additional ports
>were likely added by a newer Fixpak.

Install a Warp FP would not change services. First installing a Warp FP
will not do anything to your TCP/IP setup, assuming the FP doesn't break
something. Even if you did install a TCP/IP FP, I would be rather
surprised and annoyed if it modified services. Services is data file.
After the base install it should never be updated by a FP. It would be
the equivalent of an FP replacing your OS2.INI.

Regards,

Steven

--
----------------------------------------------------------------------
"Steven Levine" MR2/ICE 2.41 #10183 Warp4/FP15/14.093c_W4
www.scoug.com irc.webbnet.info irc.fyrelizard.org #scoug (Wed 7pm PST)
----------------------------------------------------------------------

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

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 [ 01 | March | 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.