SCOUG-HELP Mailing List Archives
Return to [ 01 |
March |
2004 ]
<< Previous Message <<
>> Next Message >>
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.
=====================================================
Steven Levine wrote:
>
> >WSeB:
> > 3-23-99 8:55a 217538 0 services
> >My W4FP10:
> > 8-06-00 9:57p 42737 0 services
>
> The dates are irrelevant, since it is perfectly
> legal to edit the services file.
>
> There is a TCP/IP API call to convert a port
> number to an service name, and that is what
> I would expect netstat to use.
Let me go backwards a couple of thoughts because I've been confusing
myself.
I didn't realize that _my_ services file was different from everyone
else's services file.
The server's services file _does_ list a radius port. My W4FP10
services file does not.
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.
I suppose I should finally upgrade my Fixpak 10. These additional ports
were likely added by a newer Fixpak.
Apologies for my confusion.
- Peter
=====================================================
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.
|