up vote 0 down vote favorite
share [g+] share [fb]

I'm running Win7 Ultimate and I had mapped networked NFS drives (Client for NFS Services required) from a FreeBSD (FreeNAS) server.

I have the reverse problem of many users who have difficulty establishing persistent, reliable mounts in Win7.

My problem is that I did a major reconfiguration of my FreeNAs server and now Win7 keeps on making mount requests to now non-existent, former shares and is flooding my FreeNAS logs with entries, such as these:

Dec 18 18:08:00 freenasbox mountd[1550]: mount request from 192.168.0.101 for non existent path /1-Seagate400
Dec 18 18:08:00 freenasbox mountd[1550]: mount request denied from 192.168.0.101 for /1-Seagate400

"192.168.0.101" is my Win7 machine, and "/1-Seagate400" is an old, no longer existent share in my FreeNAS installation.

I know this is something vestigal in "Client for NFS Services", because when I turn the service off, the logs are quiet and when turned back on, they get flooded again.

I've tried everything it seems:

  1. I deleted the NFS shares in explorer;

  2. (from command prompt) "umount -a" and get "the command completed sucssesfully"; the command "mount" gives me an empty list:

  3. "Net use * /delete" tells me "there are no entries in the list"

  4. looked all over Google and it seems the problem has always been to keep the connections alive (I'm thinking Microsoft may have made some sort of change to answer the complaints to keep mounts persistent, and made it practically impossible to get rid of the connections thereafter??)

  5. I made sure there were no lists or libraries in media player and elswhere, pointing to the former shares etc...

  6. I went into regedit and deleted all references to the former shares, even passing references in mru lists and also any references to the FreeNAS Server and to it's static ip.

I'm on my Nth reboot...

I'm stumped. Anyone have insight on this?

link|improve this question
Can you add the output you get from net use (pro-tip: pipe it to clip, like this: net use | clip. You can paste the info here then. – Bart De Vos Dec 19 '11 at 11:54
This is what the output gives : "New connections will not be remembered. There are no entries in the list." (note that I had set "persistent:no" for *, while trying to get rid of the ghost mapping, but before I had deleted them, the mappings were persistent connections) – Wibo Fichten Dec 19 '11 at 16:12
feedback

Know someone who can answer? Share a link to this question via email, Google+, Twitter, or Facebook.

Your Answer

 
or
required, but never shown
discard

Browse other questions tagged or ask your own question.