[SOLVED] Cannot Access QNAP NAS - IP Keeps Getting Blocked

[a_team]

Hi:

I'm a newb with my QNAP NAS, but after 4 days I've read the entire 695 page manual up-side down. I've been running into a re-current issue with my QNAP and I'm not the only one; I discovered what was happening by running into someone else's frustration thread online after a lot of looking around but there was never a posted solution (Thanks buddy)... Therefore, I'm hoping to get to the bottom of this and post it so everyone else as frustrated as I was can find this solution and start buying me beer

Problem:
Running Windows 7, I go to log into the fixed IP of the NAS and it doesn't load. The QNAP Finder can't find the QNAP NAS either. I can ping the address with a response when in CMD-Prompt (Start -> Search: Type "CMD" -> Type: "Ping <NAS IP>" -> Enter -> Read). I've tried Restarting my Connection, Computer, QNAP, Cup of Coffee, all with no effect.

When I access the NAS IP from a second computer it works. I go into the Security Settings (System Administration -> Security) and I find my computer's IP in the blocked list. I remove the IP, but only for my main computer to break the security violations and get back on the list.

My Security Settings are:
> Security Level
>>Security Level: Low

>Network Access Protection
>>NAP: Enabled
>> SSH, Telnet, HTTP, FTP, SAMBA, AFP : In 5 MINUTES, After 5 TIMES, Block for 1 DAY

The methods that my computer is accessing the QNAP are:
(1) Mapped FTP in Windows Explorer - Set to re-connect upon start-up
(2) NetDrive Program creating a Mapped Drive - Set to re-connect upon start-up
(3) NetBak Replicator
(4) HTTP via web-browser (Chrome & IE)

I will eliminate these one by one and keep myself updated on here as to what I tried until success is stumbled upon

Attempt #1 -> Remove NetBak Replicator Program & Restart

[a_team]

So far so good...

It looks like it's the NetBak Replicator program that comes with the QNAP Software that is trying to access the NAS upon Windows start-up but is transmitting too many incorrect username/passwords getting the IP blocked.

Funny how the first thing I looked at was the supplied free-ware.

[P3R]

I'm no Netbak user but when browsing the documentation I see no user authentication options in the application. Therefore I think it is relying on the operating system to do the authentication. If I'm correct your analysis of the cause to the problem you have is wrong.

I think that Netbak is only triggering the network access but the real problem is that Windows is by itself testing several logins when not being initially successful. If so you have exactly the same problem as all the others that ask about this. The easiest solution is to make sure your Windows login credentials (both username and password) are exactly the same as for a user on the NAS. If you do that I think that Netbak will work for you.

[a_team]

If I'm correct your analysis of the cause to the problem you have is wrong.

You are correct and I am wrong.

After this, I went onto seeing that my NAS wasn't showing up in the Network Map and that the Microsoft Protocol wasn't being discovered. This was caused because my Router's Firewall was blocking it. After resetting the firewall, setting up the Microsoft Protocol, and adding the NAS into my Network Map with the proper Username and P-Word, my Windows 7 was then cooperating with the NAS with the proper credentials.

The Key thing was to create the network map and selecting "Login with different credentials" and then entering the proper User Name and P-Word.

I re-installed NetBak with no issues.

You were definitely right. Goes back to that Assume thing... (Ass-Out of-U&Me)

http://www.youtube.com/watch?v=Vh78T--ZUxY

Hahaha