I was just assisting a user connecting to our company's Server 2012 Essentials Server over SSTP VPN.
The user has Windows 7, and Office 2010.
The SSTP VPN connection seems to work fine... we get to shares from the remote PC back to the server and can open files just dandy over VPN using Windows Explorer, and even mapped a drive to the share she uses most.
Oddly, when we try and open a Word doc via Word's file menu (File - Open) and browse to the share and the .docx file we want to open, nothing happens. It just sits there and the file never opens. We see the files (browses the directory just fine). When we click "open" or double click the file... it never opens.
We tried the same thing, this time not using the mapping ...used the UNC path instead... and same thing. The file open menu sits there and never opens the file.
This only happens when we try it from Word. When we try and open a PDF the same way through Adobe, it opens fine.
When we try and open Word docs directly from the share (via Explorer), they open fine. It's only when we try via File - Open in Word itself that it fails. Seems like a Word setting, but heck if I can find it.
I'm stumped. Anyone have a clue?
By the way, we could not replicate this on other remote PCs connecting over VPN. They open files through Word, just fine... so, this is specific to this one particular user. I have a hard time believing it's specific to her connection or router since it works fine via Adobe and Explorer. Once she's in the doc she can edit and save normally back to the server. It's just opening files through Word's directory browser that it fails at.
The user has no software firewall (other than Windows built-in) or anything that we could find that would be blocking Word's open feature.