home *** CD-ROM | disk | FTP | other *** search
- DOCUMENT:Q106687 19-NOV-1993 [W_NT]
- TITLE :NWLink Connections Fail Across Novell Routers
- PRODUCT :Windows NT
- PROD/VER:3.10
- OPER/SYS:WINDOWS
- KEYWORDS:
-
- ----------------------------------------------------------------------
- The information in this article applies to:
-
- - Microsoft Windows NT operating system version 3.1
- - Microsoft Windows NT Advanced Server version 3.1
- ----------------------------------------------------------------------
-
- SUMMARY
- =======
-
- When you cross Novell routers (file servers or multi-protocol routers)
- using NWLink, you may receive some erratic behavior unless a Registry
- entry is made for maximum packet size.
-
- SYMPTOMS
- ========
-
- The symptoms for this problem vary. In some cases, the response to a
- drive connection in File Manager takes minutes to respond. In other
- cases, File Manager stops responding (hangs). Sometimes, error
- messages are returned indicating a network problem. Even if a
- connection takes place, erroneous results may be returned.
-
- For example, share the WINNT\SYSTEM32 directory which contains greater
- than 500 on one Windows NT Advanced Server machine. When you attempt
- to connect to this share (as Administrator) from a different Windows
- NT Advanced Server, you will receive a "No Files Found" error message.
- In this example, the only machines on this internetwork are the two
- Windows NT Advanced Servers and a NetWare 3.11 file server acting as a
- router. The following NLMs are loaded on the NetWare server: ISADISK,
- TOKEN, NMAGENT, and MONITOR.
-
- Making the same connection when both Windows NT Advanced Server
- machines are connected to the same Token Ring produce the correct
- result. Directories containing only a few files may not exhibit the
- above behaviors.
-
- RESOLUTION
- ==========
-
- The workaround to this problem is to add an entry to the registries of
- the Windows NT machines as follows:
-
- WARNING: Using Registry Editor incorrectly can cause
- serious, system-wide problems that may require you to
- reinstall Windows NT to correct them. Microsoft cannot
- guarantee that any problems resulting from the use of
- Registry Editor can be solved. Use this tool at your own
- risk.
-
- 1. At a command prompt, type REGEDT32.
-
- 2. Single-click on HKEY_LOCAL_MACHINE window.
-
- 3. Double-click the following in the order listed: SYSTEM,
- CurrentControlSet, Services.
-
- 4. Scroll to NWLINKIPX.
-
- 5. Double-click the following in the order listed: NWLINKIPX,
- NetConfig, Driver01.
-
- 6. Check to see if there is a MaxPktSize entry in the box on the right.
- If so, double-click it and proceed to step 8.
-
- 7. If MaxPktSize does not exist, select choose Add Value from the Edit
- menu. In the Value Name field, type "MaxPktSize" (without the
- quotation marks. Change the Data Type field to REG_DWORD. Choose OK.
-
- 8. Change the Radix field to Decimal. In the Data, enter 1500. Choose
- OK.
-
- 9. Quit the Registry Editor, quit all open applications, shut down and
- restart the machine.
-
- Additional reference words: 3.10
- KBCategory:
- KBSubCategory: prot
-
- =============================================================================
-
- THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS
- PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS
- ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES
- OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO
- EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR
- ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL,
- CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF
- MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE
- POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION
- OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES
- SO THE FOREGOING LIMITATION MAY NOT APPLY.
-
- Copyright Microsoft Corporation 1993.