No Access to File Share from different Subnet

[NaDann]

Hi Guys,
I've got a strange behavior here, with my TS-653D. It is not possible, to get access to a WindowsFileShare from a different Subnet, eg. via VPN from Home. Name Resolutions works, and this is not a firewall related problem, Port 445 open. On the NAS AD Authentication is active and i try to connect with an User from that ad.
If i use an account which is local defined in the NAS, then it works OutOfTheBox! Same Behavior i have got, in the company but also on different subnet (behind a L3 switch). If i try, any other Windows machine, it also works out of the box, also on different subnets. I've this problem only on the qnap nas.
Any Idea?

[FSC830]

Late answer: did you check routing? Did you check if NAS has enabled IP security and allows only IPs from internal subnet?
Is NAS pingable from home PC?
Usually no need to open any port for access from remote.
At which device is your VPN endpoint?
Some more detailed network information would be helpful.

Regards

[NaDann]

Hi,
after 1 year, having no solution for this, I'll try to bring that up again, cause the problem is not gone ...

> Late answer: did you check routing?
I've been long after that point. There is no routing problem. Never was. If I try to access with my Laptop from within lan to \\NAS everything works as expected.

> Is NAS pingable from home PC?
Of course.

> Usually no need to open any port for access from remote.
I know.

> At which device is your VPN endpoint?
Its simply not working when accessing from different subnet. Doesnt matter if I'm connecting through my Site2Site VPN, or I'm using my FortiVPN, or if I'm just connected on a different Subnet in LAN. If I'm outside of my subnet, then it's over!!!

> Some more detailed network information would be helpful.
Dont think so complicated, your'e assuming the problem at the wrong place. If I'm outside my LAN Subnet, then its over!!! Under every circumstance i can ping the nas, and port 445 is also open, the question of my credentials is coming ....

If I access the \\NAS over an Site2Site VPN, its not working. If I access the \\NAS over my FortiVPN, it's also not working. If I connect from a different subnet
(direct on L3 Swich of my LAN) it is also not possible to get access to the \\NAS, WITH AN AD USER.

But if i use, an internal QNAP user (not someone out of my AD), the problem is gone ... then I can access the \\NAS, everything is as it should. WHY SHOULD THE PROBLEM A NETWORK OR WHATEVER PROBLEM!? The Problem must be within the QNAP.

And of course it's also possible to access the \\NAS over the vpn ... BUT ONLY WITH A USER DEFINED DIRECTLY ON THE QNAP. That's a very strange behavior, and i have no clue how to solve the Problem.
May be one year later somebody got the right hin, where's the problem at the QNAP NAS?!

Thx in advance
Kind regards

[NaDann]

Ahhh - fast noch vergessen! Wenn ich mit dem PC, von wo aus ich nicht auf das NAS zugreifen kann, auf eine Freigabe zugreifen will, wo ein echter Windows Server im LAN dahinter hängt ... dann geht das selbstverständlich! Und zwar OutOfTheBox. Egal ob über VPN, oder aus einem anderen Subnetz im LAN.
Will sagen, ich habe das Problem nur mit dem QNAP. Selbstverständlich wirken hier keine weiteren Regeln oder sonstige Verhinderungsmechanismen. Alles ist erlaubt.

[NaDann]

Ähhh: now in englisch *lol*

If i try to access from a pc, which can not access to qnap ... to a different windows share (in same lan subnet) on a real windows machine, the problem is also gone. I'ts working out of the box! I've the problem only with QNAP!

[NaDann]

Scheinbar bin ich wirklich der einzige mit so einem Problem.
Na gut, dann werde ich perspektivisch das Ding mal auf Halde legen müssen, wenn es das nicht drauf hat, ist mir zu doof da auf ewig hinterher zu suchen.
Mittlerweile habe ich auch mehr Platz zur Verfügung, auf einem echten Windows System, so dass ich das nervige Ding nicht mehr wirklich brauche und der Entsorgung zuführen kann. Da geht es auch sofort. Einfach so. Wie man es sich erwarten würde.
Aber Danke an den einen der geantwortet hat

[dolbyman]

Dein Englisch schwächelt wieder

Your English is failing you once more