Network timeout

AVE160 · Post by *AVE160 » 2005-07-15, 18:25 UTC

Please excuse me if this question has been posted before, I cannot find it.

It happens quite often that I have to access a computer which is not responding somehow (switched off, crashed or whatever, or I mistype the name). I'm typing in the UNC to go directly to its share.

When the remote computer does not respond, TC freezes for a certain time.
Is it somehow possible to interrupt, because I know right away that is it not going to succeed and want to break off immediately.

Thanks.

Sheepdog · Post by *Sheepdog » 2005-07-15, 18:45 UTC

Unfortunately there's no way to cancel this attempt.

But you may start another instance of TC and can work with it immedately. After a certain while the first instance will respond again.

sheepdog

Tigerman · Post by *Tigerman » 2005-07-25, 13:10 UTC

Is there a way to shorten the "freeze" time?
I often start TC with a directory opened on a computer which is not switched on at that time.
It takes a while before TC responds, so is there a possibility to shorten the "try to access" time?

Post by *ghisler(Author) » 2005-07-25, 16:02 UTC

No, unfortunately this is impossible - there is no function to reduce this Windows timeout.

Tigerman · Post by *Tigerman » 2005-07-25, 16:49 UTC

Too bad

Thanks for the quick answer

CoMiKe · Post by *CoMiKe » 2005-07-25, 22:51 UTC

This page comments some timeout parameters for NetBIOS. Perhaps some of them could help to reduce the timeout when accessing network drives...

I have not tested, anyway. Use at your own risk.

Sheepdog · Post by *Sheepdog » 2005-07-25, 23:09 UTC

I would not recommend to meddle with those values.

It is a very complex procedere how Windows decides which PC in a peer to peer network acts as WINS -Server - except you have a dedicated WINS-Server.

And I'm not sure but it may be that the PC where you change those values changes them at the other PCs too. That may result in a paralysed network, if you don't know what you do.

sheepdog

CoMiKe · Post by *CoMiKe » 2005-07-25, 23:18 UTC

That's why I haven't tested the values myself, huh.

Well, you can always do a backup (export) of that registry key, then if you broke your network, you can restore the values easily.

Sheepdog wrote:And I'm not sure but it may be that the PC where you change those values changes them at the other PCs too. That may result in a paralysed network, if you don't know what you do.

I don't think it would change other PC's values, it would be a very dangerous behavior (imagine a virus that modifies that registry values, then Windows itself tells other PCs to modify them acordingly). But who knows...

Sheepdog · Post by *Sheepdog » 2005-07-25, 23:45 UTC

CoMiKe wrote:I don't think it would change other PC's values, it would be a very dangerous behavior (imagine a virus that modifies that registry values, then Windows itself tells other PCs to modify them acordingly). But who knows...

AFAIK is in peer to peer networks after a negotiation one of the PC's the WINS -Server. And it should tell the other PCs which timeouts are used etc. Thus it's imaginable that these values are changed this way- although I really don't know.

After all you first have to find out which PC is currently the WINS-Server to let the changes take effect.

sheepdog

CoMiKe · Post by *CoMiKe » 2005-07-26, 11:36 UTC

Sheepdog wrote:AFAIK is in peer to peer networks after a negotiation one of the PC's the WINS -Server. And it should tell the other PCs which timeouts are used etc. Thus it's imaginable that these values are changed this way- although I really don't know.

I didn't know that. Thanks for the info.

I better use the noreread ini option in my specific case, as said in other topics.