NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
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 go...
OK - 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.
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.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
