Strange problem - we have an SA4500 (6.5R5) with two roles configured. One is used for our internal company users, then other is used for a partner. Access into the VPN works great with both, except for drive mappings. For the remote users using the "company" role, everything works great - apps, drive access, etc. For PCs using the "partner" role, there is no problem with connectivity. However, when they map a drive (either through Windows explorer or a home-built script that uses 'net use' commands), they have problems with accessing all of the folders underneath the root of that drive. This share is actually a DFS share, so all it's doing is referring them to clusters where the actual data is stored. After doing a Wireshark capture, I found that some SMB and NBNS lookups are actually being sent out the physical adapter of the PC and not the Network Connect adapter. I think this is the reason why they can't access the shares referred to them by the DFS, but how can I tell the client to use the NC adapter so that I can eliminate that as the problem?? I have some split tunneling set up, but all that is doing is sending traffic for two specific subnets (neither of which contain the cluster hosts or the WINS/DNS servers) out the physical adapter. In fact, the capture shows me that the SMB and NBNS lookups are being sent to the physical adapter's broadcast address. ????? I'm a network guy (routers, switches, firewalls) with minimal knowledge of netbios, DFS, etc, so I don't know...is that supposed to happen? Why wouldn't these lookups be sent out the Network Connect adapter like all other traffic destined for the internal company network? The client PCs are NOT in the same Active Directory domain as our company servers, but does that even matter in this case? TIA
... View more