NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
MickB
Dec 17, 2012Follower
ReadyNAS remote and windows XP
Hi everyone
Have tried installing latest version of ReadyNAS Remote, (1.6.5.19), on two separate PC's running XP Professional SP3. In each case Leaf Adapter failed to acquire an IP address and I got the message " A connection to the server could not be established: this error may occur if you are on a network that uses a proxy server or if you have previously configured leaf to use a proxy server and the proxy server has changed. Would you like to configure Ready NAS remote to use a proxy to connect to the internet? "
Behind same router I have successfully installed ReadyNAS remote on a Windows 7 machine and it is working perfectly.
Have tried multiple disable/enables, uninstall/installs but all to no avail. Would appreciate any help/guidance on this issue.
Update:
Just tried another installation, this time a desktop with a fresh install of Windows XP, (fully updated). Desktop connects to internet via a totally different router but result is the same. Seems there must be something wrong with the ReadyNas Remote software?
Also noted that version number on download page is 1.6.5.18, (for XP, Vista, Windows 7), but version that downloads from link is 1.6.5.19, (for Windows 8)?
Have tried installing latest version of ReadyNAS Remote, (1.6.5.19), on two separate PC's running XP Professional SP3. In each case Leaf Adapter failed to acquire an IP address and I got the message " A connection to the server could not be established: this error may occur if you are on a network that uses a proxy server or if you have previously configured leaf to use a proxy server and the proxy server has changed. Would you like to configure Ready NAS remote to use a proxy to connect to the internet? "
Behind same router I have successfully installed ReadyNAS remote on a Windows 7 machine and it is working perfectly.
Have tried multiple disable/enables, uninstall/installs but all to no avail. Would appreciate any help/guidance on this issue.
Update:
Just tried another installation, this time a desktop with a fresh install of Windows XP, (fully updated). Desktop connects to internet via a totally different router but result is the same. Seems there must be something wrong with the ReadyNas Remote software?
Also noted that version number on download page is 1.6.5.18, (for XP, Vista, Windows 7), but version that downloads from link is 1.6.5.19, (for Windows 8)?
20 Replies
Replies have been turned off for this discussion
- thebusdetAspirantI am having the same trouble, unfortunately. Windows XP - connection error. So many people still use XP - please escalate this fix if possible!
- Joe_HellAspirantAfter updating to the presently availabe ReadyNAS Remote 1.6.5.18 (a.k.a 1.6.5.19?), I am experiencing exactly the problems mentioned initially in this thread, on XP SP3 notebooks and laptops. We used a previous version (made no note of the rev.no) and it seemed to work fine, but to my knowledge earlier versions are nowhere to be found anymore.
Seems like there are a few of us customers out here losing productivity because of this issue, so if Netgear has not yet managed to sort out this problem with a working new version of ReadyNAS Remote for XP clients, at least please make the previous version available for download again!
Sincerely, Joe H - nildachangAspirant
Joe_Hell wrote: We used a previous version (made no note of the rev.no) and it seemed to work fine, but to my knowledge earlier versions are nowhere to be found anymore
Is it possible to make a downgrade somehow? - John_HudsonAspirantI have the same problem!
Running XP-Pro SP3
Current version returns an error:
A connection to the server could not be established; this error may occur if you are on a network that uses a proxy server or
if you have previously configured Leaf to use a proxy server and the proxy server has changed.
Would you like to configure ReadyNAS Remote to use a proxy to connect to the Internet?
If I uninstall and install the original version (I kept a copy), it works fine.
Reinstall the latest version and get the error message.
(During installation the installer could not configure the leaf adaptor)
If I set the leaf adaptor manually to 5.0.0.3 255.0.0.0, it shows as set, but the moment I try to log-on it reverts to 0.0.0.0 0.0.0.0 and I get the error
This is repeatable on my systems, I have tried on two XP-Pro computers running sp3
Help would be appreciated, I want to try out "ReadyDROP"
Kind regards - de_niroGuideHello Guys
I uploaded Remote 1.6.5.16 to my Google drive,please feel free to download this version and install it on your WinXP system,please note there is no ReadyDROP function can be used and it is just a temporary workaround,I am also waiting for the new Remote application.
https://docs.google.com/file/d/0ByPyKrb ... lldGs/edit - de_niroGuideLatest Remote addon has been released,which version is 1.6.5.21 and fixed issue in WinXP
http://www.readynas.com/download/remote ... 6.5.21.exe - John_HudsonAspirantLatest Remote addon has been released,which version is 1.6.5.21 and fixed issue in WinXP
http://www.readynas.com/download/remote ... 6.5.21.exe
This software prevents (or drastically slows) access to some, not all web sites.
See below my report to Netgear:
Dear Sirs,
Please be advised, you have solved a problem... but in the process created another problem, please see below...
" Case #: 20438705
Case Summary: remote not working on windows
Product:
Update from NETGEAR:
Expert ID: 56012
Case Number: 20438705
Dear Mr. Hudson,
Thank you for choosing NETGEAR. My name is MJ, and I will be your support expert.
Last Solution was:
There is an update on this issue. Please download ReadyNAS Remote for Windows (v1.6.5.21):
https://remote.readynas.com/download.html
Thanks again for choosing NETGEAR. Have a great day!
There is now a problem accessing SOME web sites, this has been traced to a problem with the LEAF Network Adaptor.
With the adaptor DISABLED,I can access any and all web sites - but of course I cannot use the ReadyNas on line.
If I ENABLE the Leaf Network Adaptor, I can access some sites e.g. www.bbc.co.uk and many others, but I cannot access e.g. www.gooutdoors.com or www.ebuyer.com
This state of affairs is repeatable and is replicated on two different MS XP-Pro SP3 computers.
This applies to all browsers IE6, Firefox and Chrome.
A Google Nexus 7 running Chrome on the same network works fine.
Please advise
John Hudson"
I have tried to re-open this case or tried to create a new case, I don't know if this was successful?
Please advise?
Best regards
John Hudson
***********
On a positive note I was able to access ReadyDrop.
But, I have now had to disable the Leaf Network Adaptor and therefore can no longer access the ReadyNas remotely, nor of course ReadyDrop.
At least I have control of my web browsers back!
John Hudson - FrankAuAspirantIn my case this new version still can not successfully login (Win XPP SP3).
There seems to be some sort of firewall issue in XPP because my iPad has no problems. - FrankAuAspirantOK - having now got Wireshark on the case it all becomes crystal clear!
The problem is the ReadyNAS Remote application is sending a HTTP/1.1 POST request over a connection that only supports HTTP/1.0.
In that request is a "Expect: 100-continue" statement which is not supported for HTTP/1.0 and causes a "417 Expectation failed" response.
Soon after the connection is dropped (with FIN ACK RST packets) and the login attempt fails.
Based on my research the simplest change is to not use the "Expect:" request - rather send the POST with a small delay between the requests.
In my case the HTTP/1,0 hop is the squid cache (v3.1.9) on my gateway server however it could also occur further away if transparent caches are used by any ISP in the path.
If I get time I will post the sequence of packets in detail. - chirpaLuminaryThat could also explain a funky loop I've been the Remote client get into. While I worked at NTGR and admin'd readynas.com, I saw a large number of clients hitting the server for the /download/remote/win_version.xml, to see if a new Remote client is available. It should only do that upon connect. If it gets into this weird area like you saw, I could see that loop going wild. It was around 200 clients hitting the server once a second. So over 1 minute, there is a few thousand hits to that file; total waste of network resources. The Remote guys never did figure out the cause, over a two year gap I kept pointing it out to them. I'm sure its still going on today as the main Remote developer also quit earlier this year.
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!