Bulletproofing NetWare

Name: Bulletproofing NetWare
Availability: OutOfStock
ISBN: 9780070676213

ISBN-10: 0070676216

ISBN-13: 9780070676213

Edition: 1997

Authors: Glenn Weadock, Mark Wilkins

List price: $34.95

30 day, 100% satisfaction guarantee!

Out of stock

We're sorry. This item is currently unavailable.

what's this?

Rush Rewards U
Members Receive:

You have reached 400 XP and carrot coins. That is the daily max!

Description:

Instead of waiting for trouble to arrive this book shows how to prevent it in the first place. The authors show how to make sure that PCs running NetWare carry on working thus reducing the time wasted trying to solve problems, and gaining valuable work time.

Book details

List price: $34.95
Copyright year: 1997
Publisher: McGraw-Hill Companies, The
Binding: Paperback
Pages: 384
Size: 7.50" wide x 9.50" long x 1.00" tall
Weight: 1.232
Language: English

Foreword	p. xiii
Acknowledgments	p. xv
Beyond Troubleshooting: The Bulletproofing Philosophy	p. 1
Bulletproofing NetWare File and Directory Services	p. 15
We added a new disk volume to a file server, but found wasted space and slow performance	p. 20
We can't afford new, superfast disk drives, but we still need to maximize file server performance	p. 21
We've tuned the file system, but performance is still slow	p. 24
File servers show saturated utilization and perform poorly	p. 26
File servers register seemingly random errors	p. 28
File servers report low memory errors	p. 30
The error log indicates that bad blocks are being redirected to the "hot fix" area	p. 32
We'd like to change drive mappings, but don't want to have to rebuild work-station INI files	p. 33
We can't tell who's using the server on a daily and monthly basis	p. 35
Disk drive failures create downtime	p. 36
Disk controller failures create downtime	p. 38
We need the benefits of duplexing but even more disk speed	p. 39
Server motherboard failures create downtime	p. 41
Users experience lockups on servers with CDROMs	p. 42
CDROMs take a long time to mount and unmount, and performance isn't great	p. 43
A few users are filling up space on file servers	p. 43
Copied files have different rights attributes	p. 45
Our file server directory structures are complex and hard to manage	p. 45
No volumes mount when the server starts	p. 46
File server console commands don't work correctly, if at all	p. 47
Windows 95 users can't use Long File Names (LFNs) on the server	p. 48
The server is logging "drive deactivation due to device failure" errors	p. 49
SCSI disks don't work properly	p. 51
Users can't find all resources on the NDS tree. (4.x)	p. 52
We have a mixed-version NDS LAN and don't know what NDS operations to perform where. (4.x)	p. 54
Bulletproofing NetWare Print Services	p. 55
We get insufficient IPX sockets or SPX connections errors when trying to load PSERVER.EXE. (3.x)	p. 61
There's not enough RAM to load PSERVER or NPRINTER	p. 62
There's not enough server disk space to spool print files	p. 63
Printers are occupying too many license slots	p. 64
Network printers process text properly, but not graphics	p. 64
Printers don't always reset properly between jobs	p. 66
PostScript printers occasionally produce gibberish	p. 67
VIP users don't get priority for print jobs	p. 68
PCONSOLE changes don't remain after a server restart	p. 70
NetWare doesn't print large jobs reliably to Unix printers	p. 70
Macintosh users need access to NetWare printers	p. 71
Complex documents aren't printing out completely	p. 72
Windows 3.x clients freeze up when printing over NetWare	p. 74
RPRINTER is causing problems for Windows 3.x users	p. 75
We're running Windows 95, and need remote printing services	p. 76
Windows clients print slowly due to double-spooling	p. 78
Windows 3.x users can only see 3 simultaneous network printers with NETX	p. 78
Screen fonts and printer fonts don't always match up	p. 80
Users can't keep track of all their fonts	p. 81
Users have trouble installing new printer drivers	p. 82
Network printing is too slow due to busy servers and outdated support files	p. 83
Network printing is too slow due to I/O bottlenecks	p. 84
High-res bitmap printing increases LAN traffic	p. 85
Network printers drop characters or print inaccurate graphics	p. 86
Managing dozens of printers is a time-consuming task	p. 87
Bulletproofing NetWare Communications Services	p. 89
We're not sure whether to use remote control or remote node access software	p. 93
Users running NetWare Connect report performance problems in remote control or remote node modes	p. 95
Users running NetWare Connect report performance problems in remote node mode	p. 96
Windows 3.x users accessing NetWare remotely can't run their modems reliably at higher speeds	p. 97
Notebook users running Windows 95 need to dial up NetWare	p. 99
We want our Windows 95 dial-up server to act as a NetWare gateway only	p. 100
The security of our Windows 95 dial-up server is inadequate	p. 101
Remote users can't always gain access to communications servers	p. 103
Users report access problems due to phone line quality	p. 103
Remote users need ISDN access to NetWare servers	p. 104
LAN users need outbound fax/modem access	p. 106
Users report slow file transfers over remote links	p. 107
Remote users with PCMCIA devices are having problems	p. 108
Configuring all those modem "AT" commands is a chore	p. 109
Managing a lot of separate NetWare Connect servers is difficult and time-consuming	p. 111
NetWare Connect doesn't provide sufficient access to our mixed network	p. 112
Remote users are racking up high telecommunications costs	p. 113
NetWare users need Internet access	p. 114
Users with certain modems report speed problems and disconnects	p. 115
Upgrading portable computers is very expensive	p. 116
NetWare Connect doesn't integrate well with Windows 95	p. 117
Mac users report problems accessing NetWare Connect	p. 118
Windows users aren't warned by NetWare Connect before making large file transfers	p. 118
IP clients can't access NetWare Connect using Windows 95	p. 118
Users need to connect to NetWare, but only have Internet access	p. 119
Bulletproofing NetWare Security	p. 121
Windows 95 clients use peer sharing under NetWare, but we've heard it's not secure	p. 128
Our LAN is adding servers, and security is harder to administer	p. 130
Users can't keep track of multiple passwords	p. 132
Users select passwords that are easily guessed	p. 132
Part-time or occasional users gain too much security access	p. 133
Windows 3.x users have too much access to desktop settings	p. 134
Electronic eavesdroppers are picking up security data	p. 136
Unwelcome outsiders are "hacking" into the LAN	p. 137
We don't want users logging in at multiple sites	p. 138
Users sometimes forget to log out	p. 139
Users can gain access to the file server console	p. 140
Users have access to too many NetWare utilities	p. 141
We can't run the risk of notebook thiefs accessing our LAN	p. 142
We're receiving error messages about the bindery. (3.x)	p. 143
We just migrated from 3.11 to 3.12, and our security database is a mess	p. 144
We don't have effective anti-virus technology in place	p. 144
We have anti-virus technology, but no anti-virus policy	p. 146
We've been hit by a virus and aren't sure how to recover	p. 148
There are certain files essential for NetWare that need extra protection	p. 149
The DOS COPY command changes file attribute security	p. 150
It takes us too long to uncover NetWare security breaches	p. 151
Our NetWare servers are pretty secure, but user workstations aren't	p. 152
Sensitive data that we thought was deleted, wasn't. 1	p. 153
Sensitive data that we thought was deleted, wasn't. 2	p. 154
We need to prevent forged packets being sent across the wire	p. 155
Bulletproofing NetWare Backups	p. 157
It isn't clear who's responsible for desktop workstation backups	p. 160
Portable PC users have no convenient backup mechanism	p. 163
When server-based tape drives fail, the server must come down	p. 164
The system crashed during a backup, corrupting our "restore" tape	p. 165
We upgraded to NDS and our backup utility doesn't work anymore. (4.x)	p. 167
Restoring files from incremental backups is time-consuming and laborious	p. 169
We use differential backups, but restores are still too slow	p. 171
Restoring after a problematical application upgrade is too slow	p. 172
A disaster destroyed our backups	p. 173
After a full server restore, users are missing their e-mail files	p. 174
A NetWare server boot disk failed, and we've lost files in the DOS partition	p. 175
We need to minimize disk space as well as perform backups	p. 176
SBACKUP reports a variety of intermittent errors	p. 178
We don't know if our backups will work if a restore becomes necessary	p. 179
We performed a restore and some files are now corrupt. 1	p. 180
We performed a restore and some files are now corrupt. 2	p. 181
We're not sure what backup storage medium is the best	p. 181
Our backup utility is encountering errors we don't know about	p. 184
We've had turnover in the IS group and no one knows how to do backups	p. 185
Our backup utility is skipping over some application files	p. 186
Differential backups aren't working correctly	p. 187
The backup utility is skipping entire volumes	p. 187
We have backups, but we need archives too	p. 188
We can't restore our archives because the format is no longer supported	p. 189
Our backup system fails when the target device fails	p. 190
Bulletproofing DOS and Windows NetWare Clients	p. 191
NETX workstation drivers take up too much low memory	p. 196
VLM workstation drivers take up too much low memory	p. 198
The VLM client is too slow	p. 199
Automatic reconnect isn't working	p. 200
We just added a new NIC to a workstation, and it doesn't work	p. 201
Windows workstations aren't getting any network messages	p. 203
Windows 95 clients can't see the network	p. 204
NETX and VLM clients can't see shared resources on Windows 95 PCs	p. 206
Logged-in Windows 3.x users have problems with NetWare	p. 207
Windows 3.x users report General Protection Faults	p. 208
Windows 3.x users report "Black Screen of Death" lockups	p. 208
Windows 3.x users change icon properties to invalid NetWare locations	p. 209
Users run Windows 3.x without being logged on to the network	p. 211
Windows client installations take too much time and effort	p. 211
Windows users get "NetWare VLM Not Loaded" errors	p. 213
Users report lost NetBIOS connections	p. 215
Drive mappings aren't working right with Windows 3.x	p. 216
Users change drive mappings in DOS sessions and they become global	p. 217
Users report poor workstation performance when networked	p. 218
Windows 95 clients don't synchronize time with NetWare servers	p. 220
We can't get a Windows 95 notebook to connect with NetWare	p. 220
We can't decide between Microsoft's and Novell's Windows 95 client	p. 221
Windows 95 clients register errors with 3.12 and 4.01 servers	p. 222
Windows 95 applications register errors when opening many files rapidly	p. 222
Windows 95 isn't loading TSRs specified in login scripts	p. 224
Bulletproofing LAN Infrastructure	p. 225
Some Token-Ring clients can't access the NetWare server	p. 231
We can only detect infrastructure problems after they've occurred	p. 232
Servers report "Router Configuration Error" messages	p. 234
We need to link our LAN to the Internet, but safely	p. 235
Our multiprotocol router seems slow due to processing and I/O constraints	p. 236
Our multiprotocol router seems slow due to excessive overhead traffic	p. 236
System performance suffers when everyone is attached to the network	p. 237
We're pulling cable for new LANs, but aren't sure what type to use	p. 238
Users report "Error Reading from Network" messages	p. 241
Ethernet hubs are unreliable	p. 243
Token-Ring hubs are unreliable	p. 244
We need to connect a NetWare LAN to an NT Domain	p. 245
LAN traffic is heavy and performance is poor	p. 246
Wide-area satellite links are prone to errors	p. 247
Leased-line WAN links have intermittent problems	p. 248
We need faster LAN throughput	p. 248
Some applications require a higher sustained transfer rate	p. 249
Infrastructure components fail when line power is erratic	p. 250
File servers fail when line power drops out	p. 252
Application servers occasionally lock up with broadcast messages	p. 253
We've configured a new external router, but it's not working	p. 254
Internetwork links seem too slow	p. 255
Users can see network resources we don't want them to see	p. 256
It takes too much time to lug a protocol analyzer around to branch-office LANs	p. 257
We're having trouble enabling Large Internet Packets	p. 258
References and Resources	p. 261
Glossary	p. 291
Index	p. 321
About the Authors	p. 336
Table of Contents provided by Syndetics. All Rights Reserved.