Strange Novell redirector behaviour

NTFSD
1

Probably is nothing new to say that Novell redirector behaves in strange
ways
but we have detected some new problems when using 4.6 Netware client.(with
SP2)

When we pass a UNC path to LanManredirector, using for
example “\MYSERVER\MYSHARE\MYFILE.TXT” (suppose MYSERVER is the local
server),
the Netware client does something like trying to find this server name in
the network.
The first effect of this behaviour is a delay in opening the file, wich
actually is a local file.
The path, finally, reaches LanMan redirector and the file is opened as
expected.
(Other secondary effects are long timeouts in named pipe connections, …)

It seems that Novell has placed some code above redirector and that this
code
is causing this problem.

Anyone is aware of or is experienced this problem ?

Thanks.

Inaki.

2

See MSDN article Q171386 - Connectivity Delay with Multiple Redirectors
Installed

In light of what it says, it sounds like you have the Novell redirector
configured as the higher priority redirector, or the SP2 version of MUP
is unnecessarily waiting for all redirectors to respond to the query
regardless of priority. The article suggests fixes.

Dave Cox
Hewlett-Packard Co.
HPSO/SSMO (Santa Barbara)
https://ecardfile.com/id/Dave+Cox

-----Original Message-----
From: I?aki Castillo [mailto:xxxxx@pandasoftware.es]
Sent: Friday, March 17, 2000 10:08 AM
To: File Systems Developers
Subject: [ntfsd] Strange Novell redirector behaviour

Probably is nothing new to say that Novell redirector behaves in strange
ways
but we have detected some new problems when using 4.6 Netware client.(with
SP2)

When we pass a UNC path to LanManredirector, using for
example “\MYSERVER\MYSHARE\MYFILE.TXT” (suppose MYSERVER is the local
server),
the Netware client does something like trying to find this server name in
the network.
The first effect of this behaviour is a delay in opening the file, wich
actually is a local file.
The path, finally, reaches LanMan redirector and the file is opened as
expected.
(Other secondary effects are long timeouts in named pipe connections, …)

It seems that Novell has placed some code above redirector and that this
code
is causing this problem.

Anyone is aware of or is experienced this problem ?

Thanks.

Inaki.

You are currently subscribed to ntfsd as: david_cox2@hp.com
To unsubscribe send a blank email to $subst(‘Email.Unsub’)

3

> the Netware client does something like trying to find this server name in

the network.
The first effect of this behaviour is a delay in opening the file, wich
actually is a local file.
The path, finally, reaches LanMan redirector and the file is opened as
expected.

It is exactly how it must be according to the MUP functionality described in
various places.
You can change the network order on your machine to set LanMan first,
NWRDR second - this will help you.

Max

4

Of course, Lanman is in first place in my system.
The problem is: being LanMan in first place and Netware in second place,
why it,Netware client, is appearing as being in first place ?

Note that this only happens when using client 4.6 .

Inaki.

At 08:42 18/03/00 +0300, you wrote:

> the Netware client does something like trying to find this server name in
> the network.
> The first effect of this behaviour is a delay in opening the file, wich
> actually is a local file.
> The path, finally, reaches LanMan redirector and the file is opened as
> expected.

It is exactly how it must be according to the MUP functionality described in
various places.
You can change the network order on your machine to set LanMan first,
NWRDR second - this will help you.

Max

You are currently subscribed to ntfsd as: xxxxx@lander.es
To unsubscribe send a blank email to $subst(‘Email.Unsub’)