"Norm Dresner" <(E-Mail Removed)> wrote in message
news:3VkZd.135792$(E-Mail Removed)...
> "Malke" <(E-Mail Removed)> wrote in message
> news:Nu2dnWITHeh2CqjfRVn-(E-Mail Removed)...
> > Norm Dresner wrote:
> >
> > > Actually it's only one specific WinXP system on the network but it's
> > > maddening because it's not only mine but also my personal e-mail
> > > computer as well.
> > >
> > > Anyway, in the heterogeneous network consisting of several Linux boxes
> > > with various system versions, a few SGI IRIX machines, and PCs with
> > > four
> > > different versions of Windows, there's one that's driving me crazy.
> > > If I mount a shared folder with smbclient from this PC -- and only
> > > this PC -- then everything works perfectly for a while, but if I
> > > simply let the connection sit idle for a period of time -- probably
> > > several 10's of minutes
> > > [though I've never done a formal experiment], then the WinXP machine
> > > [seems
> > > to have forgotten about the connection but the Linux box hasn't and
> > > any
> > > process that attempts to reference this connections hangs. The only
> > > way
> > > I've found to recover from this is to reboot the Linux machine. I
> > > have no
> > > problems at all with other WinXP, nor Win2K, WinME, or Win98 PCs.
> > > While each PC has a fairly unique software load, I've set up the two
> > > WinXP machines myself and (I think) the networking complement is more
> > > or less "the same".
> > >
> > > As long as I remember to connect, do whatever I need to, and
> > > disconnect,
> > > then everything and everyone is happy. But if I forget -- maybe once
> > > every
> > > few days -- then I need to reboot my Linux box. Since I don't think
> > > it's worth spending a lot of time to debug this problem, I'd want a
> > > workaround that would automatically unmount the WinXP share after a
> > > set period of
> > > inactivity. I guess a second choice would be to disconnect it a fixed
> > > length of time after connecting, perhaps 5-10 minutes or so. I could
> > > probably do this with a script file that mounted the share, did an
> > > appropriate sleep, and then unmounted it. I'd need all sorts of
> > > checking like killing this if I remember to manually disconnect or if
> > > I'm doing a very long transfer or even if I go to reconnect.
> > >
> > > Since the option to disconnect after a fixed period of inactivity is
> > > so much more appealing, I'd really like to find some way to implement
> > > it, but I'd also like to limit the amount of time I spend on this
> > > annoyance.
> > >
> > > Suggestions, hints, URLs and even sincere expressions of sympathy are
> > > welcome.
> > >
> > > TIA
> > > Norm
> >
> > Look at the network adapter's Properties from Device Manager on that XP
> > box. Click on the Power Management tab and make sure that the box to
> > allow Windows to turn off the device when not in use is *not* checked.
> >
> > Malke
>
> I've never seen that option before but it was, in fact, checked. I admit
> that I don't see how that might affect this problem since any new accesses
> to the computer via the local network seem to work just fine from other
> boxes, but I have unchecked it and I will try and see if it makes a
> difference.
>
> thanks
> Norm
>
Okay, I unchecked the option and have rebooted. I made the connection from
Linux to WinXP and let it sit idle for a little under 2 hours. The Linux
shell in which I tried to execute 'ls' of the share is "hung", simply doing
nothing, not accumulating any CPU time, etc.
I guess that doesn't solve the problem.
Norm
|
Similar Threads
Linear Mode
