[ Usenet FAQs | Search | Web FAQs | Documents | RFC Index ]
Part01 - Part02 - Part03 - Part04 - Part05 - Part06 - Part07 - Part08 - Part09 - Part10 - Part11 - Part12 - Part13 - Part14 - Single Page
Top Document: Win95 FAQ Part 6 of 14: NetWare (tm) Networking
Previous Document: 6.8. Bugs to watch out for, and patches
Next Document: 6.10. What does Client32 offer that MS's client does not?
-
Search the FAQ Archives
Part01 - Part02 - Part03 - Part04 - Part05 - Part06 - Part07 - Part08 - Part09 - Part10 - Part11 - Part12 - Part13 - Part14 - Single Page
Top Document: Win95 FAQ Part 6 of 14: NetWare (tm) Networking
Previous Document: 6.8. Bugs to watch out for, and patches
Next Document: 6.10. What does Client32 offer that MS's client does not?
6.9. Top ten NetWare client mistakes
10. Using a '386 machine as a server with Pentiums running Win95 as clients 9. Installing File & Print Sharing for NetWare without knowing what you're doing 8. Enabling long filenames on a NetWare 3.11 server (Patch it first!) 7. Installing Novell's Client32 out of fear 6. Capturing LPT1: to a network printer when you have MSPSRV (Print Agent for NetWare) on some workstation 5. Turning on SAP advertising in a large routed network 4. Leaving "Auto-Detect" as the frame type for IPX 3. Not specifying the preferred server in Client for NetWare properties 2. Not updating the server before adding Win95 clients 1. Not using system policies (Always a good idea to use system policies for basic stuff)
Top Document: Win95 FAQ Part 6 of 14: NetWare (tm) Networking
Previous Document: 6.8. Bugs to watch out for, and patches
Next Document: 6.10. What does Client32 offer that MS's client does not?
Part01 - Part02 - Part03 - Part04 - Part05 - Part06 - Part07 - Part08 - Part09 - Part10 - Part11 - Part12 - Part13 - Part14 - Single Page
[ Usenet FAQs | Search | Web FAQs | Documents | RFC Index ]
Send corrections/additions to the FAQ Maintainer:
gordonf@intouch.bc.ca
Last Update December 05 2008 @ 00:13 AM