click to close
help
edit

Forums ›
Computers

Problem acessing Vista from XP

  • Text Only
  • Search this Topic »
  • switch to 'Classic' view
  • Go to Page :
  • 1 2
   posted: May. 3, 2008 @ 5:41p
alert mods    

I have Windows XP with all the latest patches, etc. I'm trying to access files on a Windows Vista laptop. Both of them are in the same workgroup. When I try to access a Vista laptop I get "Logon failure: account currently disabled" error message. Acoording to Microsoft's articles it could be due domain controller and Windows 2000 none of which applies to my case. I did share C drive. There was a recommendation to set a password on a laptop so that in the XP computer I would get a login prompt. That doesn't happen.

Any other ideas please.

Thanks in advance.

   posted: May. 3, 2008 @ 5:41p

Quick Summary is created and edited by users like you... Add FAQ's, Links and other Relevant Information by clicking the edit button in the lower right hand corner of this message.

   posted: May. 4, 2008 @ 7:45a
alert mods    

What version of Vista? What version of XP?

What folder are you sharing on Vista? How, exactly, did you share the folder?

   posted: May. 4, 2008 @ 7:52a
alert mods    

XP Pro; Vista home. Shared a bunch of folders: some of them under C: drive and the c: drive by itself. Right clicking the folder you want to share and select Sharing this folder. In the tab that opens up, check the box under "Share this folder on the network"; then went to persmissions and gave full access to "Everyone"

   posted: May. 4, 2008 @ 7:56a
alert mods    

Are you using a different User Name on Vista than on XP?

Actually, take a look at this and let us know if you find your answer - Sharing in Vista

   posted: May. 4, 2008 @ 7:58a
alert mods    

Both computers have different names (obviously) and each has a different username. I'll read it.

   posted: May. 4, 2008 @ 8:06a
alert mods    

Btw, the Vista laptop can see shared folders in XP, but not vice versa and that is what my question is about. Just to clarify.

   posted: May. 4, 2008 @ 9:02a
alert mods    

Yeah, that is usually the problem. Vista security is different from XP security. I'm pretty sure that article explains it all, but let us know either way.

   posted: May. 16, 2008 @ 5:44p
alert mods    

I tried the instructions from the link provided above. It still doesn't help.

   posted: May. 16, 2008 @ 8:51p
alert mods    

How about trying the net use command? In XP you would go to a command prompt (Start, Run, CMD) and type:

net use f: \\vistamachine\sharename /user:username password

That's if you want to use drive letter F - you can change that to whatever you want. You may also want to try the IP of the machine in place of the machine name.

You can get all the net use parameters at the command prompt by typing net use /?

   posted: May. 16, 2008 @ 9:49p
alert mods    

then I get an error message "System error 1331 has occurred. Logon failure: account currently disabled."

   posted: May. 16, 2008 @ 10:11p
alert mods    

I finally got it. here's what I used:

net use \\vistamachine\sharename /u:username. Then it asked me for a password upon which it said "The command completed successfully." Then I tried accessing Vista laptop and now everything's fine.

Now, could someone explain what exactly was the problem?

Dmitriy

   posted: May. 17, 2008 @ 8:00a
alert mods    

I got the format backwards - that's why you had to do the manual password - it should have been net use f: \\name\share password /u:username. Sorry about that.

Do you know how to make that into a batch file and put it in startup so it will run every time you boot?

As for what happened, authentication was failing for some reason. The most likely cause is the name and password were not being passed correctly by XP. The net use command lets you put in exactly what you want the other machine to see, so there is no doubt about things.

   posted: May. 17, 2008 @ 9:20a
alert mods    

yea i know how to put it in a batch file; i still don't understand why it happened and why i've never had this before. also, if you're saying to create a batch file, does that mean that it will happen again? again, this is not the first computer i own and i never had this problem; so, i'm just really curious.

   posted: May. 17, 2008 @ 9:27a
alert mods    

The connection you make with NET USE will go away as soon as you reboot. Or at least it should, so putting it in startup as a batch file is the way to go.

Startup batch files are a really good idea for networking anyway. Most people don't bother with them because on small networks things tend to just work, but login scripts (batch files) are used on large networks because they are more reliable, and there is no reason not to use them on smaller networks.

   posted: May. 17, 2008 @ 9:34a
alert mods    

First thing, i just started both my computers since last night and both computers see each other and can access each other with no problems. So, net use command fixed it (maybe forever). I do understand that it's a good way of doing it, but again in my 10-11 years of dealing with computers I've never had this problem. Can I blame Vista for it?

   posted: May. 17, 2008 @ 9:57a
alert mods    

I guess it's remembering it for you. For now, anyway.

As for Vista, yes, that was the reason for the issue, because its security is different.

   posted: May. 17, 2008 @ 10:09a
alert mods    

Remembering meaning it's stored somewhere in the registry or is it just cached somewhere?

   posted: May. 17, 2008 @ 12:13p
alert mods    

With Vista I'm not sure. In XP it doesn't go into the registry, which is why you need to run it after rebooting.

   posted: May. 17, 2008 @ 12:16p
alert mods    

Everyone, thank you for your help.

 Close

Sign Me In
Nickname: 
Password: 
Remember My Login Information:

Forget your login information?

Not Already A Member?
Sign Up Now!


Disclaimer: By providing links to other sites, FatWallet.com does not guarantee, approve or endorse the information or products available at these sites, nor does a link indicate any association with or endorsement by the linked site to FatWallet.com.