A similar question had been asked here (Windows file explorer using port 80 (webdav) instead of 445 (samba smb cifs) for UNC path), however the solution did not work for my purposes.
I've recently set up an OpenVPN solution and am attempting to use it to connect to other computers. I got all that set up OK, but now I've been trying to connect via SMB to those computers.
When I attempt to connect via SMB (using
net use, windows explorer, or whatever else) locally (192.168.x.x), Windows will use port 445 just fine. However, when I attempt to connect to the remote network (192.168.y.y), Windows decides it needs to use port 80 and 135. Naturally, 80 fails and 135 doesn't have the services I'm trying to use.
TCP/IP NetBIOS Helper service is running (and works just fine in the local subnet). When I disable the web client service (even though it's not running), Windows will just skip the port 80 attempts and go straight to port 135 for the remote network. I have similarly changed around the provider orders of preference in the network settings, but that hasn't changed anything.
How do I tell restrict Windows to use only port 445 for SMB? This seems to have something to do with it not being in the local subnet.
If it matters, the clients are using Windows 7 Pro x64.