Registrations are now open. Join us today!
There is still a lot of work to do on the wiki yet! More information about editing can be found here.
Already have an account?

Microsoft KB Archive/106687

From BetaArchive Wiki
Knowledge Base


NWLink Connections Fail Across Novell Routers

Article ID: 106687

Article Last Modified on 11/1/2006



APPLIES TO

  • Microsoft Windows NT Advanced Server 3.1
  • Microsoft Windows NT Workstation 3.1
  • Microsoft Windows NT Advanced Server 3.1



This article was previously published under Q106687

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. This problem has been reported in both Token Ring and Ethernet environments.

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.

The reported Ethernet problem occurred in a complex WAN environment. Lowering the packet size resolved the issue without any other changes being required. The symptom in this case was the inability to remotely administer one Windows NT Advanced Server from another one separated by a wide area link.

WORKAROUND

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. For Token Ring, enter 1500 in the Data field. For Ethernet, enter 1000 in the Data field (higher values may be possible). Choose OK.
  9. Quit the Registry Editor, quit all open applications, shut down and restart the machine.



Additional query words: adapter prodnt

Keywords: kbnetwork KB106687