[iyonix-support] Re: Networking problem
- From: Alan Adams <alan@xxxxxxxxxxxxxxxx>
- To: iyonix-support@xxxxxxxxxxxxx
- Date: Sun, 25 Jan 2009 18:57:39 GMT
In message <891a4d2350.martin@xxxxxxxxxxxxxxxxxxx>
Martin Wuerthner <lists@xxxxxxxxxxxxxxx> wrote:
> In message <7a383a2350.Alan.Adams@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
> Alan Adams <alan@xxxxxxxxxxxxxxxx> wrote:
>> Attempt to transfer several folders of files from Iyonix to XP,
>> pushing them from Iyonix, averaging 50MB/file.
>> Transfers stop with "Timed out while receiving", after successfully
>> copying somewhere between 350M and 750M. Any further attempts to use
>> LanMan98 repeat the error.
>> Then I stopped the LanMan98 filer, and RMKilled the LanMan98 module.
>> Then I ran LanMan98. Attempting to access XP gives "Timed out while
>> connecting".
>> This last suggests to me that the problem is elsewhere in RISC OS or
>> in XP, since both parts of LanMan98 have been reloaded from scratch.
> A reasonable conclusion, up to here.
>> I then, while the Iyonix was still unable to connect, used RO4.02 on
>> an RPC, and LanMan98 v 1.22, and successfully connected to the XP
>> computer. The problem is therefore within RISC OS.
> Not necessarily. After all, you are connecting from a machine with a
> different IP address and even using different client software. There
> are still valid scenarios in which this problem could be caused by the
> Windows side. For instance, what if XP has come to the conclusion that
> there was something strange with this unknown client and has decided
> to not allow this particular machine any further access?
Interestingly, a few hours later, with neither machine being rebooted,
LanMan98 will again connect to Windows. In between it has transferred
7.5GB of data to a NAS.
> What happens if you reboot just the Windows machine and try again?
> And, vice versa, what happens after rebooting just RISC OS?
Just rebooting RISC OS cleared the problem, last time I did the test.
> Martin
What seems significant to me is that the problem doesn't show up
immediately. If it was a security issue I would expect it to occur
immediately, or not at all. Failing after transferring somewhere
between 7 and 19 files, 350 and 750MB, suggests some sort of resource
exhaustion issue.
However, the subsequent success transferring to the NAS suggests the
issue is also related to the target machine. It can't just be running
out of internet buffers for example.
The error is "timeout while receiving" by the way - I could read that
either as "The Iyonix timed out while waiting for an acknowledgement"
or "Windows timed out while waiting for data". I feel the first is
more likely (without any evidence to support that feeling.) I wonder
whether a timer somewhere isn't being reset when data is received.
When I tested last week from the same Iyonix, first with LanMan98
V1.22 then with 2.00, I got the same failure at about the same point
in the transfer.
--
Alan Adams, from Northamptonshire
alan@xxxxxxxxxxxxxxxx
http://www.nckc.org.uk/
---
To alter your preferences or leave the group,
visit http://www.freelists.org/list/iyonix-support
Other info via http://www.freelists.org/webpage/iyonix-support
Other related posts: