How do I stop a samba connection from my pc every half hour?

[rdsoftware]

Spindown works for me now (set to 5 mins), but when my PC is on, it wakes up the harddrive every half an hour. Checking the connection logs on my qnap 109. I can see that my pc has logged in as a guest with a Samba connection every half an hour for the entire time that my PC is on. Does anyone know how I can stop that happening? (my pc is running windows XP SP3)

In windows explorer I don't have any Shares on the QNAP as mapped network drives. I used to have, but I removed them, thinking that was a likely reason for the spin up every half an hour. If I want to use the folders on the QNAP I do it the long way by going into windows explorer and then to my network places --> entire network --> Microsoft Networking --> Home --> QNAP. Doing that cause the drive to spin up (as it should) but I can't see why it would do it on its own every half an hour...

I do have up to date virus software etc, so I am as sure as I can be that there is no malware lurking around opening the connection.

any help much appreciated!

[petur]

Under Win2000 you could find network sessions not attached to a drive letter that were still 'open' by going (in Explorer) to Tools->Disconnect Network Drive

I just checked under XP and it only shows mapped drives, but it can be it also still has those sessions it keeps open. Maybe you can search in that direction?

[rdsoftware]

Just gave that a try, but it says 'you have no network drives to disconnect'

Thanks anyway though, it was worth a try!

[KL643]

This is what i did. I made a new networkgroup for my NAS called "NAS" with subnetmask 255.254.0.0
Now in explorer i open my NAS with entering the fixed IP, in my case \\192.168.1.19 On my desktop i made a shortcut called NAS were i put my NAS folders. This did the trick for me. Hope this will help you.

Best regards,
KL643

[petur]

Did a quick google on the subject and found a page that talked about using Net use \\server1 /delete to kill sessions that remain open after disconnect. this is commandline stuff, replace server1 with the network name of your NAS.

You can see all open sessions with net session - not sure if it really shows all connections.
This webpage has some more details, however, one site mentioned the fact that net session \\server1 /delete does not kill the connection, it has to be net use \\server1 /delete


again, I'm unable to test/verify this here atm but it is worth a try....

[petur]

Just tried on an XP system and this is what I found:

net use will not show the connection unless mapped to a drive
net use \\servername /delete will delete the connection if there is one (it says either it has been removed or there wasn't one)

so try net use \\servername /delete on the commandline of your windows machine and see if that helps

[rdsoftware]

The dos commands didn't find any open connections either, but changing the workgroup of the QNAP from HOME to NAS, has stopped the drive spinning up every half hour while my PC is on.

So, problem solved! thanks very much for the help!

[petur]

thanks for mentioning the solution, this is interesting...

XP seems to scan the computers in its workgroup every 30 minutes ?!

[KL643]

So, problem solved! thanks very much for the help!

Good to hear it worked out for you..

[murda]

so actually we can't map drives because the stupid quest account keeps my NAS server up!
Thats sh*t in my opinion. Just delete the guest account imo in the next firmware or make an option to enable or disable it.

I have a pc idling with one mapped drive towards the qnap and every x minutes it wakes up my NAS.

I already killed the mapping with the "net use \\mynas /delete" command but please fix these annoying issues ....


I am already spending more then 3 days fixing my NAS and everywhere I go I bump into troubles
Sh*t I even need to be a Linux pro to get some things done but its good that we help each other out otherwise this player was only used for storage.

UPDATE:seems like disconnecting the networkdrive and killing them from usenet still didn't solve the guest problem logging in true samba.
Any ideas ??

[stevebow]

so actually we can't map drives because the stupid quest account keeps my NAS server up!

Do you specifically need to map a share?

I don't have any of my shares mapped. I simply have a shortcut on my desktop pointing to "\\TS-409" (the name of my NAS) and it works just fine to access the shares. I don't have any problems with the drives waking up every half hour.

[petur]

maybe he uses some (old) software that specifically needs drive letters and can't handle \\servername\share ?
Otherwise, I also do not see the need to map a share....

[murda]

so actually we can't map drives because the stupid quest account keeps my NAS server up!

Do you specifically need to map a share?

I don't have any of my shares mapped. I simply have a shortcut on my desktop pointing to "\\TS-409" (the name of my NAS) and it works just fine to access the shares. I don't have any problems with the drives waking up every half hour.

Well, I don't use mapdrives anymore since I thought that would fix the guest problem waking up my nas everytime.
But now I removed all my mapped drives but that don't seem to solve my problem.

The guest account is still connecting towards my NAS from my pc. Even if I am idling.

[petur]

I thought the issue was caused by the NAS being in the same workgroup/domain as the PC? So the solution given earlier in the thread doesn't work for you?

[murda]

I thought the issue was caused by the NAS being in the same workgroup/domain as the PC? So the solution given earlier in the thread doesn't work for you?

that didn't worked in the beginning but that was maybe because my drives were still mapped.
I am going to try both and see what that gives.

Thx for reminding me

This forum needs a "known bugs and solution thread"