Cannot access NAS after successful login with UT11

[Braveheart]

Hi Experts,

I am running version: Build: 11.0.0~svn20141103r38961release11.0-1wheezy Kernel: 2.6.32-5-untangle-686

I have my internal network exported.
I have created my windows setup.exe and installed it
I have set OpenVPNGUI to run as an adminstrator
My client is running Windows 7 Pro x64 with firewall turned off
I have a nas running on my network
I can ping the nas successfully from the client
When I try to browse/unc to the nas fqdn or ip, I cannot access the nas/shares

This worked fine in Untangle 9

Suggestions?

[jcoffin]

Do you have any IP access restrictions on the NAS?

[sky-knight]

The NAS will see Untangle's LAN IP now, instead of the connected client IP. So check your ACLs on the NAS.

[Braveheart]

There are no access restrictions on the nas device. No settings have changed on it in the last 3 years. It all worked fine in UT9.

When I updated to UT10.2 it broke and i had to add the following 2 lines to my ovpn file to be able to browse a share on the nas:

ip-win32 netsh
route-method exe

Now that I have updated to UT11, it is broken again. I can ping the nas fine. Whether or not I add those 2 lines to the newly generated ovpn file, makes no difference except that I get an error on netsh: ERROR: netsh command failed: returned error code 1

I get connected fine. I can ping my nas ip fine. Just cannot browse to any share on my nas.

[Braveheart]

And I'm using \\IP\share name to rule out any possible dns.

[Braveheart]

My bad. While I had Windows fw turned off, I forgot I was running Bitdefender fw. I had to change the setting on the nic in Bitdefender to make the adapter Trusted. Now it works.

Sorry to waste your time guys. Pasting the fix in case someone else has the issue.

Capture.JPG

[jcoffin]

Thanks for the follow-up as it may help others in the future.

[Braveheart]

No problem. I work in the industry. I know the benefit when people come back and take the time to log the fix. Thanks for your help Guys!

And now I'll go create a new post about using WOL remotely to power up a remote machine...