NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
ReadyNASty
Apr 10, 2013Aspirant
Vista Home Premium/Duo V2 - mapped connection dropping
Hello-- Not sure where to start on fixing this. I've already Googled and tried a few solutions (including this one http://support.microsoft.com/kb/297684) even though none seem to apply to my exact...
ReadyNASty
Apr 11, 2013Aspirant
Well, I can rule out the cables, because I swapped in two brand new Cat6 cables tonight, and it didn't change a thing. But I think I now have a clue what the problem is. Tonight, after some intermittent problems, the ReadyNAS disconnected and would not reconnect.
RAIDar finds it, but when I tried to connect to it using the "setup" button in RAIDar, I got this message:
This webpage is not available
The webpage at http://192.168.11.2/ might be temporarily down or it may have moved permanently to a new web address.
Error 103 (net::ERR_CONNECTION_ABORTED): Unknown error.
So I went to the laptop downstairs, typed the ReadyNAS IP into the browser, and got this:
This webpage is not available
Google Chrome's connection attempt to 192.168.11.2 was rejected. The website may be down, or your network may not be properly configured.
Here are some suggestions:
Reload this webpage later.
Check your Internet connection. Restart any router, modem, or other network devices you may be using.
Add Google Chrome as a permitted program in your firewall's or antivirus software's settings. If it is already a permitted program, try deleting it from the list of permitted programs and adding it again.
If you use a proxy server, check your proxy settings or contact your network administrator to make sure the proxy server is working. If you don't believe you should be using a proxy server, adjust your proxy settings: Go to the Chrome menu > Settings > Show advanced settings... > Change proxy settings... > LAN Settings and deselect the "Use a proxy server for your LAN" checkbox.
Error 102 (net::ERR_CONNECTION_REFUSED): The server refused the connection.
Soooooo, I went back upstairs and turned off the Windows Firewall in the computer that has the ReadyNAS as the mapped drive. BINGO! Instant stable connection to the ReadyNAS as network drive mapped a U. My guess is, there has been some update to the Windows Firewall, or to Trend Micro Internet Security which "optimizes" the Windows Firewall instead of having its own, that has caused this problem to rear its ugly head. The question now is how I go about fixing it. My crystal ball says I am going to get in the situation where Netgear says (and I can't blame them) that it's Trend Micro's fault, and Trend Micro says it's Microsoft's, and Microsoft says it's Trend Micro's, and so on and so on.
RAIDar finds it, but when I tried to connect to it using the "setup" button in RAIDar, I got this message:
This webpage is not available
The webpage at http://192.168.11.2/ might be temporarily down or it may have moved permanently to a new web address.
Error 103 (net::ERR_CONNECTION_ABORTED): Unknown error.
So I went to the laptop downstairs, typed the ReadyNAS IP into the browser, and got this:
This webpage is not available
Google Chrome's connection attempt to 192.168.11.2 was rejected. The website may be down, or your network may not be properly configured.
Here are some suggestions:
Reload this webpage later.
Check your Internet connection. Restart any router, modem, or other network devices you may be using.
Add Google Chrome as a permitted program in your firewall's or antivirus software's settings. If it is already a permitted program, try deleting it from the list of permitted programs and adding it again.
If you use a proxy server, check your proxy settings or contact your network administrator to make sure the proxy server is working. If you don't believe you should be using a proxy server, adjust your proxy settings: Go to the Chrome menu > Settings > Show advanced settings... > Change proxy settings... > LAN Settings and deselect the "Use a proxy server for your LAN" checkbox.
Error 102 (net::ERR_CONNECTION_REFUSED): The server refused the connection.
Soooooo, I went back upstairs and turned off the Windows Firewall in the computer that has the ReadyNAS as the mapped drive. BINGO! Instant stable connection to the ReadyNAS as network drive mapped a U. My guess is, there has been some update to the Windows Firewall, or to Trend Micro Internet Security which "optimizes" the Windows Firewall instead of having its own, that has caused this problem to rear its ugly head. The question now is how I go about fixing it. My crystal ball says I am going to get in the situation where Netgear says (and I can't blame them) that it's Trend Micro's fault, and Trend Micro says it's Microsoft's, and Microsoft says it's Trend Micro's, and so on and so on.
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!