Search the FAQ Archives

3 - A - B - C - D - E - F - G - H - I - J - K - L - M
N - O - P - Q - R - S - T - U - V - W - X - Y - Z
faqs.org - Internet FAQ Archives

Win95 FAQ Part 6 of 14: NetWare (tm) Networking
Section - 6.8. Bugs to watch out for, and patches

( Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Part8 - Part9 - Part10 - Part11 - Part12 - Part13 - Part14 - Single Page )
[ Usenet FAQs | Web FAQs | Documents | RFC Index | Business Photos and Profiles ]


Top Document: Win95 FAQ Part 6 of 14: NetWare (tm) Networking
Previous Document: 6.7. Why don't I get a NetWare login prompt when Win95 starts?
Next Document: 6.9. Top ten NetWare client mistakes
See reader questions & answers on this topic! - Help others by sharing your knowledge
     * 6.8.1. Automatic Frame Detection Bug: 
       
   Auto detect does not always work, especially in multi-protocol
   networks. Bring up IPX properties and manually select a frame type.
   Use 802.3 on pre-NetWare 3.12 networks, use 802.2 on 3.12 and later
   networks.

     * 6.8.2. NetWare C$ peer sharing bug: 
       
   If you use Remote Administration, it may keep the Admin share
   active after you disconnect! Apply Service Pack 1 to fix.

     * 6.8.3. WAN routing tables keep getting trashed: 
       
   When Win95 stations act like NetWare servers, all hell can break
   loose. SAP traffic can bog the network, RIP routing tables get
   re-built, clients might log in to a Win95 station instead of the real
   NetWare server. Don't use File & Print Sharing for NetWare to share
   out printers and files to non-Win95 clients; use the server and print
   queues like you're supposed to, or use Client/FPS for MS networks
   instead. More on print sharing via RPRINTER later.
   
   NOTE: Novell's latest patch sets for NetWare 3.11, 3.12, and 4.1
   correct routing problems caused by lots of SAP traffic. Visit
   Novell's downloads site and get the base OS patch sets for your
   version of NetWare. Also, to prevent non-Win95 stations from trying to
   log in to Win95 machines using FPS for NetWare, set their Preferred
   Server switch to the server you're supposed to log in to.

     * 6.8.4. Password caching bugs: 
       
   Win95 will store your login password locally, and the password
   encryption is easily cracked! Apply Service Pack 1 to fix, or better
   yet, disable password caching and use User Level Security for
   peer sharing. Check out the System Policies part to find out how
   to do force this.

     * 6.8.4.1. How do I disable password caching? 
       
   Set up a system policy file, and include "Disable Caching of
   Login Password" or "Disable Password Caching" in Default
   Computer/Network.

     * 6.8.5. Server ABENDs when I start a Win95 machine (and other
       bugs): 
       
   Any general mishap that occurs to the server that either causes an
   ABEND or otherwise kills it (I won't get into technical details; all I
   know is that Win95's demonstrated that it does bad stuff to NetWare
   servers). Check the steps you need to prepare the server or
   dis-arm the Win95 client.
   

User Contributions:

Comment about this article, ask questions, or add new information about this topic:

CAPTCHA




Top Document: Win95 FAQ Part 6 of 14: NetWare (tm) Networking
Previous Document: 6.7. Why don't I get a NetWare login prompt when Win95 starts?
Next Document: 6.9. Top ten NetWare client mistakes

Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Part8 - Part9 - Part10 - Part11 - Part12 - Part13 - Part14 - Single Page

[ Usenet FAQs | Web FAQs | Documents | RFC Index ]

Send corrections/additions to the FAQ Maintainer:
gordonf@intouch.bc.ca





Last Update March 27 2014 @ 02:12 PM