after I upgraded my PC Win7 prof to Win10 prof I have problems to connect to my Medion NAS via the webbrowser. On Win7 everything runs fine.
In the firewall my network (homezone) is defined as a trusted private Network and nothing seems to be blocked. I can access single folders on the NAS that have assigned drive letters. So I can see the NAS in the network, define driveletters for folders and access via explorer or Total Commander. BUT always, when I try to conned the NAS via the webinterface or try to connect to the build in Twonky Mediaserver, the NAS crashed, connected folders are no longer available and I have to restart the NAS. This happens with Firefox and Edge.
Firewall is set to own rules, HIPS and the other stuff is off. The Profile “Comodo firewall” was active, not the “internet security”. I saw a post where a user said to simple switch and he could connect to his NAS - not me sadly. Using my Win10 Notebook I can access the webinterface without a Problem.
So, what else information do you need and could somebody maybe give me a hint what is going wrong on my system since W10?
Thanks in advance for your support and sorry for my bad English.
Make sure the windows firewall is off via control panel and also temporary disable comodo firewall and re-check. Though I doubt CFW is causing the issue.
Then you should check with NAS manufacture as it sounds like a compatibility issue with windows 10. I mean you could uninstall CFW and check but I doubt it would change anything.
I’m confused you said you couldn’t with the web interface:
BUT always, when I try to conned the NAS via the webinterface or try to connect to the build in Twonky Mediaserver, the NAS crashed, connected folders are no longer available and I have to restart the NAS. This happens with Firefox and Edge.
Sry for any confusion - forgot the word “PC”. So I use a PC with CFW Win10 and a notebook with Win10 without CFW. Connecting with PC → crashes NAS, connecting with notebook → all good.
I figured out that I can connect to the NAS Webinterface with my PC but only via the IP-Adress 192.168.xxx.x of the NAS. When I try to connect to the the NAS with the name “NAS-Server” the NAS crashes.
Maybe now we can pin down whats wrong. Any help would greatly be appreciated.
First try adding the all applications file group to detect shellcode injections exclusions. Then reboot and try connecting to NAS with name instead of IP address. If that doesn’t work then disable the comodo firewall driver in network adapter properties by unchecking the check box of COMODO Internet Security Firewall Driver. And try to connect to NAS again.
Thx - I´ll try that. Maybe the problem is Win10 related because of the change in SMB protocol to V3? The NAS is 5 years old and there´s no firmware update. My second NAS (QNAP) runs fine and I can connect with the name.