Windows XP Cannot See "Home" Share?

Normally the only way you would see home would be if you connected to the NAS as admin (using the NAS admin password), and then browsed to the C volume.

If you are logged in as a NAS user, then you would see that user's private share (which is saved under home) - but not home itself.

if you are getting guest access you wouldn't see home, and you wouldn't see a private share either.

StephenB wrote:
Normally the only way you would see home would be if you connected to the NAS as admin (using the NAS admin password), and then browsed to the C volume. If you are logged in as a NAS user, then you would see that user's private share (which is saved under home) - but not home itself. if you are getting guest access you wouldn't see home, and you wouldn't see a private share either.

I've been connecting as "admin" since day 1..... I think..... -) What I'm getting at is that when I click on the NAS icon under Network Places, there is no ID or PW prompt and I'm assuming it remembers me from some long-gone day.

When I try to map a share to \\NAS\Home\PeteCress (I do have an ID on the box with that name) it keeps prompting me for Username and Password. Ditto \\NAS\PeteCress. OTOH, with \\NAS\Home, Windows throws "The network path \\NAS\Home could not be found.

I've tried both ID's NAS\Admin and NAS\PeteCress with the corresponding PWs... but it just keeps throwing the prompt again with User Name still populated, but Password cleared.

But I keep coming back to the fact that I'm connecting on my Android device with no problem (Using the "admin" ID/Pw).

Try opening a command prompt and typing

net use * /delete
net use  z: \\NAS\PeteCress password /user:PeteCress 

where password is your user password on the NAS.

Also try

net use * /delete
net use  z: \\NAS\C password /user:admin 

where password is the admin password on the NAS.

Both commands will map the share to drive z:

StephenB wrote:
Try opening a command prompt and typing net use * /delete net use z: \\NAS\PeteCress password /user:PeteCress where password is your user password on the NAS.

I'm starting to think Windows is somehow wacked:

c:\>net use * /delete
There are no entries in the list.

c:\>net use p: \\NAS\PeteCress Suedog999 /user:PeteCress
System error 1219 has occurred.

Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed. Disconnect all
 previous connections to the server or shared resource and try again..

c:\>

PeteCress wrote:
I'm starting to think Windows is somehow wacked:

For anybody having a similar problem: I went through several re-iterations of

 Net Use * /Delete 

and, finally, was able to get a connection.

Dunno what was happening or why, but the proximate cause seems to have been one or more existing connections to the NAS box that did not get removed by the first Net Use * /delete... or even the second one...

But once all existing connections were finally deleted, things went as expected.

The most confusing part was Windows' looping on the ID/PW dialog when I was trying to map a drive to the NAS box from the Windows UI. It didn't throw any errors like "Hey dummy, you already have a connection and we don't play dat....". Instead it just quietly re-issued the ID/PW dialog as if an incorrect ID or PW were being supplied.

Hi PeteCress, StephenB
Just wanted to comment that I also had the same issue with XP, and was able to resolve it using the "net use * /delete" command to clear all old connections.

At first I thought my new user was not set-up correctly, but realised something must be wrong when I couldn't access the shares with admin user either.

Your comments above were most useful to me, thanks.

However, there is one thing I noticed:
Does this mean that if I were to map one share as a network directory for a particular user in XP, that I wouldn't be able to map another share using a different ReadyNAS user, but on the same XP user?

kullyrai wrote:
Does this mean that if I were to map one share as a network directory for a particular user in XP, that I wouldn't be able to map another share using a different ReadyNAS user, but on the same XP user?

Yes, that is what it means.

Though there is a cheap trick to use 2 different readynas users. You can map one share using the NAS name, and a second one using the NAS IP. At least I've seen posts that say that trick works...

OK, so here I am with the same problem on just one XP computer, but not the other XP one nor the two Win 7 ones, and on just one of my ReadyNAS's. So, It HAS to be XP (Pro, w/ service pack 3) that's doing it, I think. If I try to access my home directory using either the NAS name or the IP address and either my own or admin credentials, it won't work. No problem with access to public directories. I can access my home directory on my other NAS just fine. They have the same users and everyting, I exported users and groups from one to the other when I set up the second one. Disabled my firewall (which should have affected public and home directories if that was it), and no change.

I've tried multiple net use * /delete, removed ALL of my cached passwords from Key Manager, rebooted both the NAS and XP machine (multiple times), and still no go. I've gone so far as to delete all references to the share name in the registry, and still nothing. I've renamed the NAS and given it another IP address. Nothing seems to work.

If I do a NET USE (with password and user name) to map the share as a drive, all seems OK. Get "The command completed successfully." I can even change to that directory. But I can't see any files or diectories. I get an error that the network name is already in use. The mapped drive shows up wih status "OK" with a NET USE command.

If I just double-click on the share in "My Network Places"(without first having the drive maped), it prompts for a user name and password. I put them in, and after a LONG wait it tells me I don't have permission to access and the network name no longer exists. It seems to be searching the LOCAL hard drive for something during this long wait. Now, NET USE shows the path without a drive letter, but still with status "OK". Checking the box to save the password when I enter it creates an entry in the Key Manager, but makes no difference as far as access is concerned. If I use Explorer to go to top level on the NAS, I see the share there, but still can't access it.

It's an NVX Business edition, if it matters; but I don't think it does. Otherwise, it would be affecting all my computers. Just to be sure, I checked file permissions using SSH, and I'm the owner and have full RWX permissions.

My best guess is that XP is not properly storing and/or passing on my credentials when it trys to access the NAS. But why only on one and not the other NAS? Have Googled up a storm and not found anything that looks like a solution.

And the offender is: jumbo frames. Why it causes problems with shares that are protected and not open ones, I'm just guessing. But my suspicion is that it initially trys to negotiate using jumbo frames and fails (regardless of share type), then re-negotiates with a standard frame but messes up the credentials (or doesn't re-send them at all). That doesn't bother the open share, but does the protected one.

A couple of weeks ago, I re-aranged my ethernet cabling, and I apparently didn't get it back quite the way it was. I ended up having to go through my WNDR4000 router to get to one NAS but not the other. The WNDR4000 does not support jumbo frames, but my switches do. So, now I was trying to get to the NAS via a device that doesn't support jumbo frames with jumbo frames enabled on the PC. Why it didn't happen right away, I am clueless. My computer typically stays on, but I may have re-booted it for a Windows update or something, and that did it in. It didn't happen on the other XP machine because it's NIC doesn't support jumbo frames. And Win7 or that NIC driver must do a better job with the jumbo frames conflict than the XP one.

After finding that disabling jumbo frames on the PC fixed the issue, I re-checked my wiring and figured out what I changed. Now I'm back to all working with jumbo frames enabled.

Thanks to StephenB in this thread -- http://www.readynas.com/forum/viewtopic.php?f=23&t=61931 -- for the hint that finally got me to the solution.

Sandshark wrote:
And the offender is: jumbo frames.

Can one perceive the added speed of Jumbo Frames or is it more of a theoretical thing?

i.e. Might it be worthwhile for me to adopt them?

I looked at http://en.wikipedia.org/wiki/Jumbo_frame and it seemed to say they were not such a big deal now.... but I have no clue as to what they are talking about:

To Wit:

Obsolescence

By making CPU load independent of frame size, large segment offload (LSO) has eliminated the per-packet overhead that jumbo frames were designed to reduce.[9] Large receive offload (LRO), the inbound counterpart of large segment offload, does not quite eliminate per-packet overhead borne by the CPU, therefore jumbo frames remain beneficial for inbound traffic.