VPN and Windows Networking

From what I read for Sonicwall's Global VPN client, it is an IPSec client as such it should carry all network traffic including MS Net Neighborhood traffic.

Here is most likely problem:

1) Roadwarrior connects to TZ 180 via VPN using GVC

2) IPSec terminates at TZ 180. TZ 180 will then forward unencrypted traffic to the internal LAN, to the Server specifically

3) The server receives the MS Net Neighborhood traffic and responds it.
Problem: it is most likely that your roadwarrior has an IP different from internal LAN IP. So when the server responds, it doesn't know where to send. So it send to the default gateway configured for your internal LAN the server belongs to. If that default gateway is TZ 180, everything should work and you will not be asking this. If that default gateway is not TZ 180, it will either be dropped or misrouted (and dropped eventually) unless that default gateway also knows (has static route to) about TZ 180.

Fix #1: In latter case, the fix will be that you can create static route in your server via 'route' command (for Windows too).

Fix #2: (alternate to #1) You can also fix at TZ 180. TZ 180 can (has DHCP over IPSec functionality?) give out the same internal addresses to roadwarriors; just make sure they don't overlap with internal scheme (i.e for internal 192.168.3.2-192.168.3.150, for roadwarriors 192.168.3.151-192.168.3.200)

Other note: your VPN connection is working fine based on the fact that you can Remote Desktop into the server via VPN.