Mapping Network drives with Vista - possible clues to problems.

I reported under another thread that I could map a network drive from Vista
to V5R3 but not to V5R1 and from the responses that I received it seemed
that no one could map to V5R1 using Vista. I have been looking further into
the problems and thought it made sense to start a new thread.

Firstly, I have since found that, whilst I could map a network drive to V5R3
internally, I could not do this remotely. So I used a network protocol
analyser (wireshark) to look at the traffic and found that Vista handled
remote and internal network drives very differently. The reason that the
remote network drive did not work was because Vista used HTTP for mapping
the external drive and found that under V5R3 I had not authorised PROPFIND,
hardly surprising because I had never heard of it. It is part of WEBDAV
about which I also know nothing. Does anyone else have problems mapping a
network drive remotely from Vista to V5R3? Has anyone got this to work?

Secondly, and as a result, I checked remotely using Vista to V5R1 and found
that my V5R1 box sent back a message saying that PROPFIND had not been
implemented, presumably because under V5R1 I am using the old HTTP server
rather than Appache. Has anyone one tried mapping a drive from Vista
remotely to a box that uses Appache under V5R1? It is possible that, in
this case, they would get the not authorised rather than the not implemented
message.

Network protocols are outside my comfort zone, and, as I am about to go away
for a few days, I thought that I would pass on what I have discovered,
because someone who knows more than me might say that I have misunderstood
or someone else might tell me how to authorise PROPFIND.

I have yet to try mapping from Vista to an internal V5R1 system when using
the protocol analyser.