Windows 2000 /XP NetBIOS over VPN. Slow on first access to hidden share.

  • Thread starter Thread starter Fai
  • Start date Start date
F

Fai

Hi,
Here is the network setup

WinXP1 (10.1.1.1) <-> IPSec VPN <-> WinXP2 (192.168.0.1)

I am sure the IPSec VPN work correctly
the problems is like that.
When usng WinXP1 access hidden share on WinXP2 (eg: C$)
( use "start \\192.168.0.1\c$" in cmd or enter \\192.168.0.1\c$ in the
address of Windows Explorer)
the process is very slow, i need to wait for few mins.
but when i use "start \\192.168.0.1" in cmd or enter \\192.168.0.1 in
the address bar of windows explorer, the result return in a normal
speed.

during the waiting "start \\192.168.0.1\c$" i found that there are
many HTTP port probe from WinXP1 at WinXP2.
it is there any parameter i can configure to skip the HTTP scanning ?
or make it more faster when access hidden share?

same case on WinXP2 access WinXP1

thx a lots.
 
Hi, after certain testing
i found that the results like that
if i edit the hosts file and added the name, resluts the same ( slow)
(even if i use the correct internal DNS which can resolve host name
correctly, its slow too)
if i remove the entries of hosts and added in lmhosts.
(and enalbe lmhosts lookup in TCP/IP properties)
i can browser the hidden share with normal speed (eg: \\winxp1\c$)

does anyone know why ? Thx a lots.!
 
during the waiting "start \\192.168.0.1\c$" i found that there are
many HTTP port probe from WinXP1 at WinXP2.
it is there any parameter i can configure to skip the HTTP scanning ?
or make it more faster when access hidden share?
Click to expand...

The http port probe suggest that your client is testing to
see if it is a web share that it is being asked to access
if i remove the entries of hosts and added in lmhosts.
(and enalbe lmhosts lookup in TCP/IP properties)
i can browser the hidden share with normal speed (eg: \\winxp1\c$)
Click to expand...

using the computer name rather than an IP address probably
changes the behavior of the client. This syntax eliminates the
possibility that the share being accessed is a web share.
 
Back
Top