> I finally don´t know if the cause is really Windows XP (or XP SP3) or NOD32
> or both, but I follow Vlad´s suggestion of not using TCP/IP connections and
> it seems to be working. What I did is not to use HOST:path and instead I use
> \\HOST\path. For Terminal server I had to use \\127.0.0.1\\path because
> \\LOCALHOST\path doesn´t work. BTW does anybody knows why this doesn´t work?

localhost is an TCP\IP name. NetBEUI used NetBIOS (and\or WINS) for name resolution,
while TCP\IP used hosts file and DNS. This is completely different name spaces. IP adress
for localhost present in hosts file therefore TCP\IP subsystem know what is "localhost".
You could add corresponding entry to the lmhosts file but this is not practical solution.
Better use simple dot as name, i.e. \\.\path, for local connection.

> And now I have a question:
>
> Is there any difference in using HOST:path against using \\HOST\path in
> performance, security, etc.?

For local connections NetBEUI will be much faster than TCP\IP (but still somewhat
slower than XNET). For network (remote) connections i can't said for performance.
From security POV i know no difference.

Regards,
Vlad