Cannot map network drive on VPN (W2K)

[mpascu]

Hello ALL,
The problem is I cannot map a drive on a client computer connected to my LAN through dial-up connection+VPN . There are no such problems on LAN .
The LAN server is Windows 2000 , DNS installed, the Internet proxy is Linux (but this problem occured even with ISA Server ) . The client is Win98 . The ping with the client is 500-800 ms .
File Sharing is active at the client , of course .
This problem is not always, only sometimes . I ussualy can map the drive, but sometimes not .
Could it be the low quality of dial-up connection to ISP at the client ?

Thank You,
Mihai.

[mysterywolf]

what happens when it won't work exactly?

[mpascu]

Hello ,
The message I get when it doesn't work is "The network path \\client\c could not be found" .

[POBrien]

To further isolate the problem, you need to fix the ping time. 500 + is a nightmare. For a dialup, you should trace around 100-180 from source to destination. Here's my dialup trace to winguides.com to compare.

Microsoft(R) Windows 98
(C)Copyright Microsoft Corp 1981-1999.

C:\Program Files\Site Surfer>tracert winguides.com

Tracing route to winguides.com [66.216.113.81]
over a maximum of 30 hops:

1 100 ms 96 ms 98 ms nas1.snfc21.pbi.net [209.233.202.10]
2 99 ms 100 ms 95 ms dist1-vlan10.snfc21.pbi.net [209.233.202.2]
3 99 ms 93 ms 95 ms bb1-g8-0.snfc21.pbi.net [209.232.130.82]
4 99 ms 99 ms 100 ms sl-gw11-sj-3-0.sprintlink.net [144.228.44.49]
5 104 ms 95 ms 98 ms sl-bb25-sj-6-1.sprintlink.net [144.232.3.133]
6 104 ms 115 ms 115 ms sl-bb23-ana-6-0.sprintlink.net [144.232.20.158]
7 129 ms 129 ms 135 ms sl-bb21-fw-10-3.sprintlink.net [144.232.18.61]
8 134 ms 135 ms 135 ms sl-gw40-fw-8-0.sprintlink.net [144.232.8.246]
9 139 ms 135 ms 135 ms sl-racks-2-0.sprintlink.net [144.232.204.10]
10 134 ms 135 ms 138 ms vl130.core1.sat.rackspace.com [64.39.2.33]
11 137 ms 140 ms 140 ms vl905.aggr5.sat2.rackspace.com [64.39.2.82]
12 140 ms 140 ms 140 ms winguides.com [66.216.113.81]

Trace complete.

POBrien