We have combination NT 4.0 and Netware 3.11/3.12 network. Had it for many years, and nothing has recently been added or removed such as new servers, client configuration changes, etc. We recently are having periodic problems running the login.bat file on the NT servers. We perform drive maps via the NET USE command within login.bat. They are taking 1-2 minutes per NET USE to complete the mapping. The problem comes and goes, but seems to be related to the Netware servers across the WAN. There are 3 local netware servers and 2 over 384k frame relay links. If we disconnect the WAN, the NET USE map is quicker but still not normal (1-2 seconds I consider normal). Once a person is logged in, all software applications, file copies, etc are normal, its only the NET USE mapping.
Does anyone know how the NET USE actually functions or what its doing that might cause it to take so long? It never actually times out. Eventually the mapping takes place. It can take someone with 5-6 maps up to 10 minutes to log in. Clients are using the Client for Microsoft Networks as the primary client.
I'm really interested in exactly how the NET USE works in regards to protocol, process, etc.