|
Steve -- I'm sure you know this (from WRKSRVTBLE) but the ports are as follows: 139 - Netbios (Network Neighborhood/NetServer) 449 - Server mapper 8470 - Central server 8473 - File server I've already mentioned the File server. The central server is used for license management and ASCII<->EBCDIC conversion so I'm pretty comfortable that we have an errant Client Access Express issue here. You can filter out all traffic from the offending IP address using Operations Navigator as described here: http://publib.boulder.ibm.com/pubs/html/as400/v4r5/ic2924/info/RZAJBRZAJBX1CREATINGNEWRULESSD.HTM#HDRRZAJBX1-CREATING_NEW_RULES_SD Then, just wait for a call in the morning from someone complaining that they can't connect to the 400. Gary srichter wrote: > > Jeffrey, > > The branch/site that is the source of the trouble only has win95 pc's. Only >1 pc shows up with activity in NetStat right now. NetStat shows the local port >as 139, 449, 8470 and 8473. Mostly 449 ( as-svrmap ). The remote port keeps on >incrementing by 2 within the range of 1500 to 4000. > > Steve Richter
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
