Dec 082017
| Novell Wide area network utility for monitoring servers. | |||
|---|---|---|---|
| File Name | File Size | Zip Size | Zip Type |
| LANBEEP.CFG | 594 | 362 | deflated |
| LANBEEP.COM | 18168 | 6335 | deflated |
| LANBEEP.DOC | 55950 | 12794 | deflated |
| LANBEEP.ORD | 4213 | 604 | deflated |
| LBSCAN.COM | 1383 | 843 | deflated |
| READ.ME | 4454 | 1643 | deflated |
| README | 944 | 367 | deflated |
Download File LANBP23.ZIP Here
Contents of the READ.ME file
LanBeep v2.3 Documentation Update
LanBeep v2.3 now supports COM3 and COM4 by using 'PORT=COM3' or 'PORT=COM4' in
LANBEEP.CFG. LanBeep v2.3 also supports definable servers. Instead of using
the keyword 'FSNAME=', you now use the more generic keyword 'SERVERNAME='
followed by the name of the server that you wish LanBeep to monitor. The type
of server that SERVERNAME represents is defined by using the new keyword
'OBJECTTYPE=' followed by the 1-4 digit hex value that is recognized by the
network's bindery. OBJECTTYPE is used in the configuration file and any
servers named after this statement will use this object type as its definition
(until another 'OBJECTTYPE=' statement is found). The default OBJECTTYPE is
0004 (file server), so if no 'OBJECTTYPE=' statement is found, all server names
specified on 'SERVERNAME=' statements will be scanned as file servers.
Some of the known server types are:
0004 File Server 002E Archive Server
0005 Job Server 0045 DI3270 Gateway
0006 Gateway 0047 Advertising Print Server
0009 Archive Server 004B Btrieve Server
0021 NAS/SNA Gateway 004C NW SQL Server
0023 NACS Gateway 004D XTree Network
0024 Remote Bridge Server 0050 Btrieve Server
0026 Async Bridge Server 0098 NW Access Server
0027 TCP/IP Gateway 0103 Oracle DB Server
0028 X.25 Bridge 0107 Rconsole
0029 Gateway 6F00 Rabbit Gateway
Note that the above represents an incomplete server type list. For servers not
listed, contact the product manufacturer to obtain the object type, or you can
use the supplied program LBSCAN. LBSCAN displays all of the server types that
your network's bindery is aware of, along with the server's name. These two
fields are to be used, as mentioned previously, in the configuration file.
Simply run LBSCAN.COM with the network shell loaded. The program will display
objects as they are encountered in the bindery. If you wish to see a sorted
list, the optional '/S' parameter will display the list in ascending object
type order. This may take considerably longer than an unsorted list. To
interrupt the program at any time, hit.
Please make sure that the object type that you are scanning is the correct one.
I.e., a file server named FS1 running RCONSOLE will show up twice in LBSCAN's
output- once as type 0004 and once as type 0107. Using 'OBJECTTYPE=0107' and
'SERVERNAME=FS1' will cause the program to beep you if RCONSOLE is unloaded.
The correct configuration would be to use 'OBJECTTYPE=0004'. Another example
of misleading object types is print servers- using an object type of 0007 will
report on print servers that EXIST in the bindery regardless of whether or not
they are up and running, whereas object type 0047 will report on the status
(not all print servers advertise). Please note that the LanBeep PC may need to
be logged in to the file server to 'see' certain bindery objects.
LanBeep v2.3 Documentation Update (Continued)
To be sure that LanBeep is monitoring what you think it is monitoring, create a
situation to cause a beep.
The following is an example configuration for LanBeep v2.1, and its new format:
v2.1 v2.3
;identify this region ;identify this region
REGION=01 REGION=01
;file server names ;file server object type
FSNAME=FS1 OBJECTTYPE=4
FSNAME=FS2 ;file server names
FSNAME=FS3 SERVERNAME=FS1
FSNAME=FS4 SERVERNAME=FS2
FSNAME=FS5 SERVERNAME=FS3
FSNAME=FS6 ;access server object type
FSNAME=FS7 OBJECTTYPE=98
FSNAME=FS8 ;access server name
FSNAME=FS9 SERVERNAME=ACCESS_SRVR
;beeper number to dial ;beeper number to dial
BEEPER=912015556666 BEEPER=912015556666
LanBeep v2.3 now supports COM3 and COM4 by using 'PORT=COM3' or 'PORT=COM4' in
LANBEEP.CFG. LanBeep v2.3 also supports definable servers. Instead of using
the keyword 'FSNAME=', you now use the more generic keyword 'SERVERNAME='
followed by the name of the server that you wish LanBeep to monitor. The type
of server that SERVERNAME represents is defined by using the new keyword
'OBJECTTYPE=' followed by the 1-4 digit hex value that is recognized by the
network's bindery. OBJECTTYPE is used in the configuration file and any
servers named after this statement will use this object type as its definition
(until another 'OBJECTTYPE=' statement is found). The default OBJECTTYPE is
0004 (file server), so if no 'OBJECTTYPE=' statement is found, all server names
specified on 'SERVERNAME=' statements will be scanned as file servers.
Some of the known server types are:
0004 File Server 002E Archive Server
0005 Job Server 0045 DI3270 Gateway
0006 Gateway 0047 Advertising Print Server
0009 Archive Server 004B Btrieve Server
0021 NAS/SNA Gateway 004C NW SQL Server
0023 NACS Gateway 004D XTree Network
0024 Remote Bridge Server 0050 Btrieve Server
0026 Async Bridge Server 0098 NW Access Server
0027 TCP/IP Gateway 0103 Oracle DB Server
0028 X.25 Bridge 0107 Rconsole
0029 Gateway 6F00 Rabbit Gateway
Note that the above represents an incomplete server type list. For servers not
listed, contact the product manufacturer to obtain the object type, or you can
use the supplied program LBSCAN. LBSCAN displays all of the server types that
your network's bindery is aware of, along with the server's name. These two
fields are to be used, as mentioned previously, in the configuration file.
Simply run LBSCAN.COM with the network shell loaded. The program will display
objects as they are encountered in the bindery. If you wish to see a sorted
list, the optional '/S' parameter will display the list in ascending object
type order. This may take considerably longer than an unsorted list. To
interrupt the program at any time, hit
Please make sure that the object type that you are scanning is the correct one.
I.e., a file server named FS1 running RCONSOLE will show up twice in LBSCAN's
output- once as type 0004 and once as type 0107. Using 'OBJECTTYPE=0107' and
'SERVERNAME=FS1' will cause the program to beep you if RCONSOLE is unloaded.
The correct configuration would be to use 'OBJECTTYPE=0004'. Another example
of misleading object types is print servers- using an object type of 0007 will
report on print servers that EXIST in the bindery regardless of whether or not
they are up and running, whereas object type 0047 will report on the status
(not all print servers advertise). Please note that the LanBeep PC may need to
be logged in to the file server to 'see' certain bindery objects.
LanBeep v2.3 Documentation Update (Continued)
To be sure that LanBeep is monitoring what you think it is monitoring, create a
situation to cause a beep.
The following is an example configuration for LanBeep v2.1, and its new format:
v2.1 v2.3
;identify this region ;identify this region
REGION=01 REGION=01
;file server names ;file server object type
FSNAME=FS1 OBJECTTYPE=4
FSNAME=FS2 ;file server names
FSNAME=FS3 SERVERNAME=FS1
FSNAME=FS4 SERVERNAME=FS2
FSNAME=FS5 SERVERNAME=FS3
FSNAME=FS6 ;access server object type
FSNAME=FS7 OBJECTTYPE=98
FSNAME=FS8 ;access server name
FSNAME=FS9 SERVERNAME=ACCESS_SRVR
;beeper number to dial ;beeper number to dial
BEEPER=912015556666 BEEPER=912015556666
Contents of the README file
LanBeep v2.3 Documentation Update
LanBeep v2.3 now supports COM3 and COM4 by using 'PORT=COM3' or 'PORT=COM4' in
LANBEEP.CFG. LanBeep v2.3 also supports definable servers. Instead of using
the keyword 'FSNAME=', you now use the more generic keyword 'SERVERNAME='
followed by the name of the server that you wish LanBeep to monitor. The type
of server that SERVERNAME represents is defined by using the new keyword
'OBJECTTYPE=' followed by the 1-4 digit hex value that is recognized by the
network's bindery. OBJECTTYPE is used in the configuration file and any
servers named after this statement will use this object type as its definition
(until another 'OBJECTTYPE=' statement is found). The default OBJECTTYPE is
0004 (file server), so if no 'OBJECTTYPE=' statement is found, all server names
specified on 'SERVERNAME=' statements will be scanned as file servers.
Some of the known server types are:
0004 File Server 002E Archive Server
0005 Job Server 0045 DI3270 Gateway
0006 Gateway 0047 Advertising Print Server
0009 Archive Server 004B Btrieve Server
0021 NAS/SNA Gateway 004C NW SQL Server
0023 NACS Gateway 004D XTree Network
0024 Remote Bridge Server 0050 Btrieve Server
0026 Async Bridge Server 0098 NW Access Server
0027 TCP/IP Gateway 0103 Oracle DB Server
0028 X.25 Bridge 0107 Rconsole
0029 Gateway 6F00 Rabbit Gateway
Note that the above represents an incomplete server type list. For servers not
listed, contact the product manufacturer to obtain the object type, or you can
use the supplied program LBSCAN. LBSCAN displays all of the server types that
your network's bindery is aware of, along with the server's name. These two
fields are to be used, as mentioned previously, in the configuration file.
Simply run LBSCAN.COM with the network shell loaded. The program will display
objects as they are encountered in the bindery. If you wish to see a sorted
list, the optional '/S' parameter will display the list in ascending object
type order. This may take considerably longer than an unsorted list. To
interrupt the program at any time, hit.
Please make sure that the object type that you are scanning is the correct one.
I.e., a file server named FS1 running RCONSOLE will show up twice in LBSCAN's
output- once as type 0004 and once as type 0107. Using 'OBJECTTYPE=0107' and
'SERVERNAME=FS1' will cause the program to beep you if RCONSOLE is unloaded.
The correct configuration would be to use 'OBJECTTYPE=0004'. Another example
of misleading object types is print servers- using an object type of 0007 will
report on print servers that EXIST in the bindery regardless of whether or not
they are up and running, whereas object type 0047 will report on the status
(not all print servers advertise). Please note that the LanBeep PC may need to
be logged in to the file server to 'see' certain bindery objects.
LanBeep v2.3 Documentation Update (Continued)
To be sure that LanBeep is monitoring what you think it is monitoring, create a
situation to cause a beep.
The following is an example configuration for LanBeep v2.1, and its new format:
v2.1 v2.3
;identify this region ;identify this region
REGION=01 REGION=01
;file server names ;file server object type
FSNAME=FS1 OBJECTTYPE=4
FSNAME=FS2 ;file server names
FSNAME=FS3 SERVERNAME=FS1
FSNAME=FS4 SERVERNAME=FS2
FSNAME=FS5 SERVERNAME=FS3
FSNAME=FS6 ;access server object type
FSNAME=FS7 OBJECTTYPE=98
FSNAME=FS8 ;access server name
FSNAME=FS9 SERVERNAME=ACCESS_SRVR
;beeper number to dial ;beeper number to dial
BEEPER=912015556666 BEEPER=912015556666
From ROSE MEDIA - 55 Nodes - 53 Gigabytes
416-733-2285 - US Robotics 14400 HST lines
416-733-0894 - USR 16.8 DS and V.32 lines
416-733-7645 - Hayes V9600 / V42 line
416-226-9260 - Telebit T2500 line
416-575-5363 - Rose Media Hamilton Lines
This file has successfully passed a virus
check with McAfee's SCANV99 which tests
for 1561 known viruses. Backups recommended.
BACKING UP YOUR IMPORTANT FILES MAKES SENSE!
LanBeep v2.3 now supports COM3 and COM4 by using 'PORT=COM3' or 'PORT=COM4' in
LANBEEP.CFG. LanBeep v2.3 also supports definable servers. Instead of using
the keyword 'FSNAME=', you now use the more generic keyword 'SERVERNAME='
followed by the name of the server that you wish LanBeep to monitor. The type
of server that SERVERNAME represents is defined by using the new keyword
'OBJECTTYPE=' followed by the 1-4 digit hex value that is recognized by the
network's bindery. OBJECTTYPE is used in the configuration file and any
servers named after this statement will use this object type as its definition
(until another 'OBJECTTYPE=' statement is found). The default OBJECTTYPE is
0004 (file server), so if no 'OBJECTTYPE=' statement is found, all server names
specified on 'SERVERNAME=' statements will be scanned as file servers.
Some of the known server types are:
0004 File Server 002E Archive Server
0005 Job Server 0045 DI3270 Gateway
0006 Gateway 0047 Advertising Print Server
0009 Archive Server 004B Btrieve Server
0021 NAS/SNA Gateway 004C NW SQL Server
0023 NACS Gateway 004D XTree Network
0024 Remote Bridge Server 0050 Btrieve Server
0026 Async Bridge Server 0098 NW Access Server
0027 TCP/IP Gateway 0103 Oracle DB Server
0028 X.25 Bridge 0107 Rconsole
0029 Gateway 6F00 Rabbit Gateway
Note that the above represents an incomplete server type list. For servers not
listed, contact the product manufacturer to obtain the object type, or you can
use the supplied program LBSCAN. LBSCAN displays all of the server types that
your network's bindery is aware of, along with the server's name. These two
fields are to be used, as mentioned previously, in the configuration file.
Simply run LBSCAN.COM with the network shell loaded. The program will display
objects as they are encountered in the bindery. If you wish to see a sorted
list, the optional '/S' parameter will display the list in ascending object
type order. This may take considerably longer than an unsorted list. To
interrupt the program at any time, hit
Please make sure that the object type that you are scanning is the correct one.
I.e., a file server named FS1 running RCONSOLE will show up twice in LBSCAN's
output- once as type 0004 and once as type 0107. Using 'OBJECTTYPE=0107' and
'SERVERNAME=FS1' will cause the program to beep you if RCONSOLE is unloaded.
The correct configuration would be to use 'OBJECTTYPE=0004'. Another example
of misleading object types is print servers- using an object type of 0007 will
report on print servers that EXIST in the bindery regardless of whether or not
they are up and running, whereas object type 0047 will report on the status
(not all print servers advertise). Please note that the LanBeep PC may need to
be logged in to the file server to 'see' certain bindery objects.
LanBeep v2.3 Documentation Update (Continued)
To be sure that LanBeep is monitoring what you think it is monitoring, create a
situation to cause a beep.
The following is an example configuration for LanBeep v2.1, and its new format:
v2.1 v2.3
;identify this region ;identify this region
REGION=01 REGION=01
;file server names ;file server object type
FSNAME=FS1 OBJECTTYPE=4
FSNAME=FS2 ;file server names
FSNAME=FS3 SERVERNAME=FS1
FSNAME=FS4 SERVERNAME=FS2
FSNAME=FS5 SERVERNAME=FS3
FSNAME=FS6 ;access server object type
FSNAME=FS7 OBJECTTYPE=98
FSNAME=FS8 ;access server name
FSNAME=FS9 SERVERNAME=ACCESS_SRVR
;beeper number to dial ;beeper number to dial
BEEPER=912015556666 BEEPER=912015556666
From ROSE MEDIA - 55 Nodes - 53 Gigabytes
416-733-2285 - US Robotics 14400 HST lines
416-733-0894 - USR 16.8 DS and V.32 lines
416-733-7645 - Hayes V9600 / V42 line
416-226-9260 - Telebit T2500 line
416-575-5363 - Rose Media Hamilton Lines
This file has successfully passed a virus
check with McAfee's SCANV99 which tests
for 1561 known viruses. Backups recommended.
BACKING UP YOUR IMPORTANT FILES MAKES SENSE!
December 8, 2017
Add comments