Can't add folder on network share to library

Sempie said:

I have also this type of problem, I get an error when I want to open my nas
is there a solution for this problem

this thread may have a solution for your problem -https://www.sevenforums.com/network-internet/8303-cant-connect-samba-share-via-name-ip-works.html

I think there is a MAJOR problem here. Microsoft have clearly not checked out compatibility with XP/2000 in a domain environment which means corporates will treat it the same as Vista - ie: JUNK! As a professional IT consultant, I am evaluating Windows 7 on a corporate basis and it looks like a big NO! NO! Apart from the fixable(?) bugs, there is a major education issue which SMEs and corporates will be unwilling to address. I think Microsoft need to go back to the drawing board.

Has there been any progress made on this issue?

I've been testing out Win7 Pro x64 and the search functionality is driving me nuts. On non-indexed locations, you can only use 2 search filters, and if you want to search in more than one folder you have to select them manually from the explorer tree (rather then simply typing them in which I do on XP). I frequently perform searches on different folders located on 4-6 networked drives on a server running XP, so this can be very time consuming.

I can't add the network drives to a library because I can't index them - I've tried every method described in this thread. The symlink trick kind of worked - it allowed me to add them to a library, but I get zero results when I try to search it, regardless of what I type in the search field.

Easy fix - revert to XP and remove the program Windows Search 4.

Surely Microsoft can't be so incompetent as to leave out a feature far more needed now than years back for XP usage. Home and business networked drives are...almost fundamental now. There must be a solution to index networked drives??

Unfortunately, Microsoft seem to be forgetting the big advantages of Windows - ease of use in corporate as well as home environments.

They seem to think home users need mollycoddling, but the end results are an OS which is becoming increasingly unfriendly and cumbersome.

My kids are quite happy with networked shares and drives, so I think it is time Microsoft should stop treating adults as idiots.

Indexing a large network share is not always practical. I have written a tool to allow you to add network locations (mapped drives and UNC paths) without them having to be indexed. And it provides some additional features like backup/restore of library sets. You can download it for free (+ WPF source) here:

Win7 Library Tool Zorn Software

Faxedhead, you are kinda missing the point. You COULD index a network drive on XP and Vista, even years back with slower networks and CPUs. It's coming up on 2010 and Microsoft TAKES AWAY a feature that's even more useful now-- they don't allow you to index a networked drive which can store valuable shared docs etc. Nor does Microsoft discuss this anywhere.

Your tool offered makes no sense. I can already map a networked drive easily on Win7. I just can't index it. Problem statement is very simple, a lot of people on this thread don't seem to grasp it though.

For what it's worth, there seems to be an undocumented work-around. Run WDS4.0 on the networked drive and Win7 clients seem to use the networked computer's search engine to do the work. So now I can search a library that includes a networked drive.

starmanj said:

Faxedhead, you are kinda missing the point. You COULD index a network drive on XP and Vista, even years back with slower networks and CPUs. It's coming up on 2010 and Microsoft TAKES AWAY a feature that's even more useful now-- they don't allow you to index a networked drive which can store valuable shared docs etc. Nor does Microsoft discuss this anywhere.

Your tool offered makes no sense. I can already map a networked drive easily on Win7. I just can't index it. Problem statement is very simple, a lot of people on this thread don't seem to grasp it though.

For what it's worth, there seems to be an undocumented work-around. Run WDS4.0 on the networked drive and Win7 clients seem to use the networked computer's search engine to do the work. So now I can search a library that includes a networked drive.

I completely agree - indexing is the way to go when it comes to file management, and it's crazy that you need to make your files available 'offline' (i.e. create a local copy) in order to do that in 7. However consider these two points:

1. If your network drive is on a linux box, you are still screwed, WDS4.0 will not help afaik (please correct me if i am wrong).
2. Whilst search is useful, it is enough for many people to just have 'quick access' by adding commonly used folders to libraries. Many people actually organise their files quite well, meaning they know where things live, and only occassionally have to resort to search. If you do this with network drives you have no way of grouping them into a category or providing icons, default save location and other features that libraries provide.

faxedhead said:

I completely agree - indexing is the way to go when it comes to file management, and it's crazy that you need to make your files available 'offline' (i.e. create a local copy) in order to do that in 7. However consider these two points:

1. If your network drive is on a linux box, you are still screwed, WDS4.0 will not help afaik (please correct me if i am wrong).

Is there any solution in town, or in tow, like in SP1 or SP2...?

Shall we file an petition about this...? : )