Anilrgowda

have a site-to-site VPN based on RV042s. This is currently set up in a "lab" environment with one host on each LAN.
One host is Windows XP, the other is 98SE. Normally these computers network on the same LAN just fine.
The "internet" connection is implemented with a hub.
The VPN seems to be working fine.
The two sites have different subnets for routing.

I can't map network drives between the two sites.
I get: "The network path \\192.168.109.139\c could not be found."
I can ping that same IP address OK.
The two sites are worgroup arrangements / not domains. No login required.
It occurs to me that the *share name* is somehow not visible even though the IP address is reachable.
I have read things about setting MTU.
I have read things about LMHOSTS
I have read things about WINS
I've not tried anything in this regard yet because what I've read didn't make complete sense to me.
So, I have no idea how to resolve this and a real solution is needed.

Here's what a sniffer on the local host shows during the attempt to map:

No. Time Source Destination Protocol Info
2945 10:16:31.960824 192.168.109.213 192.168.109.139 TCP 3851 > microsoft-ds [SYN] Seq=0 Ack=0 Win=65535 Len=0 MSS=1460 WS=3 TSV=0 TSER=0

Frame 2945 (78 bytes on wire, 78 bytes captured)
Ethernet II, Src: 00:e0:b8:3d:13:e3, Dst: 00:16:b6:84:04:4c
Internet Protocol, Src Addr: 192.168.109.213 (192.168.109.213), Dst Addr: 192.168.109.139 (192.168.109.139)
Transmission Control Protocol, Src Port: 3851 (3851), Dst Port: microsoft-ds (445), Seq: 0, Ack: 0, Len: 0

No. Time Source Destination Protocol Info
2946 10:16:34.817942 192.168.109.213 192.168.109.139 TCP 3851 > microsoft-ds [SYN] Seq=0 Ack=0 Win=524280 Len=0 MSS=1460 WS=3 TSV=0 TSER=0

Frame 2946 (78 bytes on wire, 78 bytes captured)
Ethernet II, Src: 00:e0:b8:3d:13:e3, Dst: 00:16:b6:84:04:4c
Internet Protocol, Src Addr: 192.168.109.213 (192.168.109.213), Dst Addr: 192.168.109.139 (192.168.109.139)
Transmission Control Protocol, Src Port: 3851 (3851), Dst Port: microsoft-ds (445), Seq: 0, Ack: 0, Len: 0

No. Time Source Destination Protocol Info
2947 10:16:40.379277 192.168.109.198 224.0.0.1 IGMP V2 Membership Query

Frame 2947 (60 bytes on wire, 60 bytes captured)
Ethernet II, Src: 00:16:b6:84:04:4c, Dst: 01:00:5e:00:00:01
Internet Protocol, Src Addr: 192.168.109.198 (192.168.109.198), Dst Addr: 224.0.0.1 (224.0.0.1)
Internet Group Management Protocol

No. Time Source Destination Protocol Info
2948 10:16:40.826580 192.168.109.213 192.168.109.139 TCP 3851 > microsoft-ds [SYN] Seq=0 Ack=0 Win=524280 Len=0 MSS=1460 WS=3 TSV=0 TSER=0

Frame 2948 (78 bytes on wire, 78 bytes captured)
Ethernet II, Src: 00:e0:b8:3d:13:e3, Dst: 00:16:b6:84:04:4c
Internet Protocol, Src Addr: 192.168.109.213 (192.168.109.213), Dst Addr: 192.168.109.139 (192.168.109.139)
Transmission Control Protocol, Src Port: 3851 (3851), Dst Port: microsoft-ds (445), Seq: 0, Ack: 0, Len: 0

No. Time Source Destination Protocol Info
2949 10:16:40.939323 192.168.109.198 224.0.0.9 IGMP V2 Membership Report

Frame 2949 (60 bytes on wire, 60 bytes captured)
Ethernet II, Src: 00:16:b6:84:04:4c, Dst: 01:00:5e:00:00:09
Internet Protocol, Src Addr: 192.168.109.198 (192.168.109.198), Dst Addr: 224.0.0.9 (224.0.0.9)
Internet Group Management Protocol

No. Time Source Destination Protocol Info
2950 10:16:41.237158 192.168.109.213 239.255.255.250 IGMP V2 Membership Report

Frame 2950 (46 bytes on wire, 46 bytes captured)
Ethernet II, Src: 00:e0:b8:3d:13:e3, Dst: 01:00:5e:7f:ff:fa
Internet Protocol, Src Addr: 192.168.109.213 (192.168.109.213), Dst Addr: 239.255.255.250 (239.255.255.250)
Internet Group Management Protocol

No. Time Source Destination Protocol Info
2951 10:16:46.120448 192.168.109.198 192.168.109.255 RIPv2 Response

Frame 2951 (86 bytes on wire, 86 bytes captured)
Ethernet II, Src: 00:16:b6:84:04:4c, Dst: ff:ff:ff:ff:ff:ff
Internet Protocol, Src Addr: 192.168.109.198 (192.168.109.198), Dst Addr: 192.168.109.255 (192.168.109.255)
User Datagram Protocol, Src Port: router (520), Dst Port: router (520)
Routing Information Protocol

No. Time Source Destination Protocol Info
2952 10:16:52.903928 192.168.109.213 192.168.109.139 TCP 3852 > http [SYN] Seq=0 Ack=0 Win=65535 Len=0 MSS=1460 WS=3 TSV=0 TSER=0

Frame 2952 (78 bytes on wire, 78 bytes captured)
Ethernet II, Src: 00:e0:b8:3d:13:e3, Dst: 00:16:b6:84:04:4c
Internet Protocol, Src Addr: 192.168.109.213 (192.168.109.213), Dst Addr: 192.168.109.139 (192.168.109.139)
Transmission Control Protocol, Src Port: 3852 (3852), Dst Port: http (80), Seq: 0, Ack: 0, Len: 0

No. Time Source Destination Protocol Info
2953 10:16:55.848217 192.168.109.213 192.168.109.139 TCP 3852 > http [SYN] Seq=0 Ack=0 Win=524280 Len=0 MSS=1460 WS=3 TSV=0 TSER=0

Frame 2953 (78 bytes on wire, 78 bytes captured)
Ethernet II, Src: 00:e0:b8:3d:13:e3, Dst: 00:16:b6:84:04:4c
Internet Protocol, Src Addr: 192.168.109.213 (192.168.109.213), Dst Addr: 192.168.109.139 (192.168.109.139)
Transmission Control Protocol, Src Port: 3852 (3852), Dst Port: http (80), Seq: 0, Ack: 0, Len: 0

No. Time Source Destination Protocol Info
2954 10:17:01.856822 192.168.109.213 192.168.109.139 TCP 3852 > http [SYN] Seq=0 Ack=0 Win=524280 Len=0 MSS=1460 WS=3 TSV=0 TSER=0

Frame 2954 (78 bytes on wire, 78 bytes captured)
Ethernet II, Src: 00:e0:b8:3d:13:e3, Dst: 00:16:b6:84:04:4c
Internet Protocol, Src Addr: 192.168.109.213 (192.168.109.213), Dst Addr: 192.168.109.139 (192.168.109.139)
Transmission Control Protocol, Src Port: 3852 (3852), Dst Port: http (80), Seq: 0, Ack: 0, Len: 0
******************************

Anilrgowda

Okay, I read the original question more thoroughly, and there are some things you need to consider for your follow up questions..

First, Netbios Browsing cannot be done across subnets (or VPNs for that matter) unless you configure a WINs server at each location.. but, you can map drives by the IPAddresses as you are currently trying to do, as long as you are using different subnets.. it is just Browsing that does not work... you can cirumvent this with the LMHosts file, or the WINs servers..

MTU might need to be adjusted, but in your test environment, it is doubtful that this would prevent the connection.. It is more important when tranversing large networks, like the Internet... It is basically an adjustment to the Maximum Packet Size (Unit) that can be Transmitted..