Windows Forum / Windows XP / Networking and Web / December 2007
Pulling my hair out over file sharing
|
|
Thread rating:  |
Pam - 05 Nov 2005 15:36 GMT I orginally posted this issue in the wireless forum - a couple of kind folks tried to help but so far to no avail. I manage to isolate the problem to my wired desktop computer so I thought I would try posting over here. Here goes:
I have a laptop and a desktop networked via a router. Laptop is wireless, desktop is wired. Verizon DSL comes to both via the router.
Problem: Internet access is fine. I can access the laptop files from the desktop fine. I can use the desktop's printer from the laptop fine. I CAN'T access the desktop's files from the laptop. I get the 'you may not have permission...access denied'message.
Details: Desktop is running XP Pro. Network connect is static IP. Laptop is running XP Media Edition (this means it must be Home Edition, right?) -wireless connect -DHCP. Router is from Verizon - Westell Versalink
I can ping the desktop from the laptop I turned off all firewalls - Windows and Norton I took off the WEP security file sharing is on - simple file sharing and switched to Advanced - didn't help I turned everything off and went to make coffee. Then turned everything on, router first. I made sure the user accounts have the exact same names. System permissions are simple - anybody can do anything I tried putting a password (identical) on each account I switched the laptop to a wired connection I connected a wired Windows 98SE machine (could get to the XP desktop files from there)
Any ideas?
Jim Macklin - 05 Nov 2005 15:52 GMT Check the properties on each protocol on the connection to be sure you have the required protocols installed on each. Make sure you have specifically shared a folder. You don't and should not turn the firewalls off, add each computer to the trusted list. Have you run the XP networking wizard on each computer and do both computers show up in your workgroup list?
 Signature The people think the Constitution protects their rights; But government sees it as an obstacle to be overcome. some support http://www.usdoj.gov/olc/secondamendment2.htm
|I orginally posted this issue in the wireless forum - a couple of kind folks | tried to help but so far to no avail. I manage to isolate the problem to my [quoted text clipped - 29 lines] | | Any ideas? Dingley Mellowcreme - 05 Nov 2005 15:55 GMT > I orginally posted this issue in the wireless forum - a couple of kind > folks tried to help but so far to no avail. I manage to isolate the [quoted text clipped - 30 lines] > > Any ideas? When you say "user accounts" are you referring to the individual computer's workgroup name? For instance, the default workgroup name is MSHOME, I believe, when you first set up a home netwoek through the wizard. Maybe something got switched somewhere and they have different workgroup names?
Good luck.
Malke - 05 Nov 2005 16:24 GMT >> I orginally posted this issue in the wireless forum - a couple of >> kind folks tried to help but so far to no avail. I manage to isolate [quoted text clipped - 38 lines] > > Good luck. Workgroup names are just a cosmetic/organizational function. Windows computers do not need the same Workgroup name in order to share files/printers.
XP Media Edition isn't the same as Home. It is a subset of Pro. Just try running the Network Setup Wizard on the laptop again, making sure you answer "yes" to file/printer sharing. After you finish, if you are running a third-party firewall you'll need to go to the Control Panel and turn off Windows Firewall. Make sure your third-party firewall is configured to allow lan traffic as trusted.
Malke
 Signature MS-MVP Windows User/Shell Elephant Boy Computers www.elephantboycomputers.com "Don't Panic"
Chuck - 05 Nov 2005 16:56 GMT >I orginally posted this issue in the wireless forum - a couple of kind folks >tried to help but so far to no avail. I manage to isolate the problem to my [quoted text clipped - 29 lines] > >Any ideas? Pam,
The "...access denied" messages has many causes. Attack the problem systematically, and it should be possible to find the cause. <http://nitecruzr.blogspot.com/2005/06/mysterious-error-5-aka-access-denied.html> http://nitecruzr.blogspot.com/2005/06/mysterious-error-5-aka-access-denied.html
 Signature Cheers, Chuck, MS-MVP [Windows - Networking] http://nitecruzr.blogspot.com/ Paranoia is not a problem, when it's a normal response from experience. My email is AT DOT actual address pchuck mvps org.
Pam - 22 Jan 2006 21:31 GMT Chuck, your blog is marvelous. I read every bit and checked every setting one by one. Then I had to step away because it was making me really crazy. Now I'm back after a long rest and re-read and tried everything again - one by one, of course. Same result.
A summary of where I stand is:
- A Dell desktop running XP Pro SP2 is the server - The desktop is wired to a versalink router - I have two choices of client - Toshiba laptop XP MCE SP2 wireless and Windows 95SE wired to router. - All machines have identical accounts with identical passwords. - The guest account is activated with identical password on the XP machines. - I tried creating a new account just for test
result: Access denied error=5 using laptop or Win95 machine as client to access Dell Desktop. Can access both the laptop and the Win95 as server.
There was just one thing that was a bit odd (I'm grasping at straws) - in the security settings, user rights assignment, 'access this computier from the network' - there is the list of familar items Administrators, everyone, users, powerusers, there are two stranges ones: aspnet and *s-..... (where ..... is a long string of numbers letters and dashes) - could that meaning anything?
No firewalls are on, Norton Internet Security is completely removed (as far as I can tell, how can I know for sure...)
any thoughts?
> >I orginally posted this issue in the wireless forum - a couple of kind folks > >tried to help but so far to no avail. I manage to isolate the problem to my [quoted text clipped - 36 lines] > <http://nitecruzr.blogspot.com/2005/06/mysterious-error-5-aka-access-denied.html> > http://nitecruzr.blogspot.com/2005/06/mysterious-error-5-aka-access-denied.html Chuck - 22 Jan 2006 22:04 GMT >> >I orginally posted this issue in the wireless forum - a couple of kind folks >> >tried to help but so far to no avail. I manage to isolate the problem to my [quoted text clipped - 36 lines] >> <http://nitecruzr.blogspot.com/2005/06/mysterious-error-5-aka-access-denied.html> >> http://nitecruzr.blogspot.com/2005/06/mysterious-error-5-aka-access-denied.html
>Chuck, your blog is marvelous. I read every bit and checked every setting one >by one. Then I had to step away because it was making me really crazy. Now [quoted text clipped - 25 lines] > >any thoughts? Hi Pam,
First, thanks for the feedback. Any time I see "your blog" and "marvelous" in the same sentence, I feel that I've accomplished something. But enough back patting, I see "any thoughts?" at the end of the post.
Let's take an easy approach, and start by reviewing your setup. Let's look at "browstat status" and "ipconfig /all" from each computer, and try and diagnose the problem. Read this article, and linked articles, and follow instructions precisely: <http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html# AskingForHelp> http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html# AskingForHelp
And when you reply, please type your reply after my latest post. <http://nitecruzr.blogspot.com/2005/05/how-to-post-on-usenet-and-encourage.html#T opPosting> http://nitecruzr.blogspot.com/2005/05/how-to-post-on-usenet-and-encourage.html#T opPosting
Patience and persistence, Pam.
 Signature Cheers, Chuck, MS-MVP [Windows - Networking] http://nitecruzr.blogspot.com/ Paranoia is not a problem, when it's a normal response from experience. My email is AT DOT actual address pchuck mvps org.
Pam - 22 Jan 2006 23:35 GMT Here goes, as requested:
Background Information
Delldesktop running XP Pro SP2, bblaptop running XP MCE SP2. Simple file sharing on both. File permissions are set. Account is an administrator account, Guest account is on.
When attempting to view shared docs bblaptop as client, Delldesktop as server message is ‘\\Delldesktop\shareddocs is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions. Access is denied.’
I believe that I am using guest authentication because I am using simple file sharing. I’m not seeing anything in the event viewer that looks at all relevant. Retrictanonymous is set to zero It’s hard to say what happened new to cause the problem because there was a fair amount of time when I didn’t even try to access data via the lan however, four events that I can think of – from the sublime to the trivial - are: • I had a flood in my office, 6 in. of H2O killed the delldesktop. I replaced the motherboard and it came back to life • Installed sp2 • Installed Verison DSL • On a whim decided to change the user accounts from first and last name to first name only on one of the machines (can’t remember which) and changed it back when the problems started.
I am using a static IP connection to the router for the desktop – this was after a long long process of getting the Verizon dsl to work.
Ipconfig:
Windows IP Configuration Host Name . . . . . . . . . . . . : DellDesktop Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No Ethernet adapter Local Area Connection via Westell: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Broadcom NetXtreme 57xx Gigabit Controller Physical Address. . . . . . . . . : 00-11-11-72-6E-F1 Dhcp Enabled. . . . . . . . . . . : No IP Address. . . . . . . . . . . . : 192.168.1.48 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.1.1 DNS Servers . . . . . . . . . . . : 192.168.1.1
Browstat from the Delldesktop:
Status for domain MSHOME on transport \Device\NetBT_Tcpip_{DA61C3E3-2C4C-49EC-914A-43E2BD39BB82} Browsing is active on domain. Master browser name is: DELLDESKTOP Master browser is running build 2600 1 backup servers retrieved from master DELLDESKTOP \\DELLDESKTOP There are 2 servers in domain MSHOME on transport \Device\NetBT_Tcpip_{DA61C3E3-2C4C-49EC-914A-43E2BD39BB82} There are 1 domains in domain MSHOME on transport \Device\NetBT_Tcpip_{DA61C3E3-2C4C-49EC-914A-43E2BD39BB82}
Browstat from the bblaptop:
Status for domain MSHOME on transport \Device\NetBT_Tcpip_{B9F52395-BFCB-4F4B-B32B-546270C9CBF4} Browsing is active on domain. Master browser name is: DELLDESKTOP Could not open key in registry, error = 5 Unable to determine build of browser master: 5 \\\\DELLDESKTOP . Version:05.01 Flags: 51207 NT POTENTIAL MASTER 1 backup servers retrieved from master DELLDESKTOP \\DELLDESKTOP There are 2 servers in domain MSHOME on transport \Device\NetBT_Tcpip_{B9F52395-BFCB-4F4B-B32B-546270C9CBF4} There are 1 domains in domain MSHOME on transport \Device\NetBT_Tcpip_{B9F52395-BFCB-4F4B-B32B-546270C9CBF4}
> >> >I orginally posted this issue in the wireless forum - a couple of kind folks > >> >tried to help but so far to no avail. I manage to isolate the problem to my [quoted text clipped - 85 lines] > > Patience and persistence, Pam. Chuck - 23 Jan 2006 00:49 GMT >> >> >I orginally posted this issue in the wireless forum - a couple of kind folks >> >> >tried to help but so far to no avail. I manage to isolate the problem to my [quoted text clipped - 83 lines] >> <http://nitecruzr.blogspot.com/2005/05/how-to-post-on-usenet-and-encourage.html#T opPosting> >> http://nitecruzr.blogspot.com/2005/05/how-to-post-on-usenet-and-encourage.html#T opPosting
>Here goes, as requested: > [quoted text clipped - 78 lines] > There are 1 domains in domain MSHOME on transport >\Device\NetBT_Tcpip_{B9F52395-BFCB-4F4B-B32B-546270C9CBF4} Pam,
Well, "access denied" is a normal error, when you're using Simple File Sharing, for any administrative access. For instance, browstat doing a registry lookup on the master browser will always get "access denied". Or, attempting network access to a protected folder or share, such as (but not limited to) "C$", "C:\", "C:\Program Files", or "C:\Windows" will always get "access denied". <http://nitecruzr.blogspot.com/2005/06/mysterious-error-5-aka-access-denied.html> http://nitecruzr.blogspot.com/2005/06/mysterious-error-5-aka-access-denied.html
But, if you're getting "access denied" when you try to access any normal (non-admin) shares, you may have a problem. If you do, it will most generally be a personal firewall error. Which shares are you trying to access? Be specific here please. Maybe provide "ipconfig /all" from bblaptop too.
Did you follow the complete instructions from Symantec? I used to do a yearly un install (previous years version of NAV) / re install (new years version of NAV) because NAV sold in the store, with rebate, was way cheaper than paying the yearly (and ever increasing) subscription fees. Then I realised it was far easier to re format and re install Windows XP, and all apps, so I did that for a couple years.
Finally, I re formatted and re installed Windows XP, and installed another antivirus. And never looked back on Symantec again. And as of last fall, I am completely S$ free on all computers.
Are you sure that you un installed all components in NIS? Let's see if Autoruns (free) from SysInternals can help. Run Autoruns on DELLDESKTOP, and get a Protocol_Catalog9 extract. <http://nitecruzr.blogspot.com/2005/12/lsp-winsock-analysis-using-log-from.html> http://nitecruzr.blogspot.com/2005/12/lsp-winsock-analysis-using-log-from.html
And Pam, before you reply again, please read THIS article. <http://nitecruzr.blogspot.com/2005/05/how-to-post-on-usenet-and-encourage.html#T opPosting> http://nitecruzr.blogspot.com/2005/05/how-to-post-on-usenet-and-encourage.html#T opPosting
 Signature Cheers, Chuck, MS-MVP [Windows - Networking] http://nitecruzr.blogspot.com/ Paranoia is not a problem, when it's a normal response from experience. My email is AT DOT actual address pchuck mvps org.
Pam - 23 Jan 2006 23:49 GMT > >> >> >I orginally posted this issue in the wireless forum - a couple of kind folks > >> >> >tried to help but so far to no avail. I manage to isolate the problem to my [quoted text clipped - 202 lines] > <http://nitecruzr.blogspot.com/2005/05/how-to-post-on-usenet-and-encourage.html#T opPosting> > http://nitecruzr.blogspot.com/2005/05/how-to-post-on-usenet-and-encourage.html#T opPosting Chuck, right it is definitely not an admin share. In my desperation I even set up a share for another folder – also not admin – same result.
Ipconfig for bblaptop:
Windows IP Configuration Host Name . . . . . . . . . . . . : BBLaptop Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Unknown IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : myhome.westell.com Ethernet adapter Wireless Network Connection 3: Connection-specific DNS Suffix . : myhome.westell.com Description . . . . . . . . . . . : Atheros AR5001X+ Wireless Network Adapter #2 Physical Address. . . . . . . . . : 00-90-96-67-68-A8 Dhcp Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes IP Address. . . . . . . . . . . . : 192.168.1.46 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.1.1 DHCP Server . . . . . . . . . . . : 192.168.1.1 DNS Servers . . . . . . . . . . . : 192.168.1.1 192.168.1.1 Lease Obtained. . . . . . . . . . : Monday, January 23, 2006 7:57:06 AM Lease Expires . . . . . . . . . . : Tuesday, January 24, 2006 7:57:06 AM Ethernet adapter Local Area Connection: Media State . . . . . . . . . . . : Media disconnected Description . . . . . . . . . . . : Realtek RTL8139/810x Family Fast Ethernet NIC Physical Address. . . . . . . . . : 00-02-3F-81-E7-46 PPP adapter Verizon Online: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface Physical Address. . . . . . . . . : 00-53-45-00-00-00 Dhcp Enabled. . . . . . . . . . . : No IP Address. . . . . . . . . . . . : 71.250.166.147 Subnet Mask . . . . . . . . . . . : 255.255.255.255 Default Gateway . . . . . . . . . : 71.250.166.147 DNS Servers . . . . . . . . . . . : 151.197.0.39 151.198.0.39 NetBIOS over Tcpip. . . . . . . . : Disabled
On the NIS un-install – it was an OEM version of NIV 2004 – I did follow the Symantec instructions, although I wish I had some positive proof that is was successful – the add/remove programs appeared to complete successfully on all Norton/Symantec programs and they strongly stressed not to run the utility that they provide if add/remove worked – so I didn’t. I did go with a different firewall for the re-install (once I solve this problem!) but bought another copy NAV. I came to Norton in the first place because I had an issue w/ McAfee.
Here is the Autoruns Catalog9 Extract. I compared it to your attachment A and couldn’t find any thing that looked at all odd.
HKLM\System\CurrentControlSet\Services\WinSock2\Parameters\Protocol_Catalog9 + MSAFD NetBIOS [\Device\NetBT_Tcpip_{3B434AD0-DE25-43AF-B225-06E892F79F38}] DATAGRAM 3 Microsoft Windows Sockets 2.0 Service Provider (Verified) Microsoft Windows Publisher c:\windows\system32\mswsock.dll + MSAFD NetBIOS [\Device\NetBT_Tcpip_{3B434AD0-DE25-43AF-B225-06E892F79F38}] SEQPACKET 3 Microsoft Windows Sockets 2.0 Service Provider (Verified) Microsoft Windows Publisher c:\windows\system32\mswsock.dll + MSAFD NetBIOS [\Device\NetBT_Tcpip_{3B600DB8-CA9C-4209-B329-4FD089B2612B}] DATAGRAM 4 Microsoft Windows Sockets 2.0 Service Provider (Verified) Microsoft Windows Publisher c:\windows\system32\mswsock.dll + MSAFD NetBIOS [\Device\NetBT_Tcpip_{3B600DB8-CA9C-4209-B329-4FD089B2612B}] SEQPACKET 4 Microsoft Windows Sockets 2.0 Service Provider (Verified) Microsoft Windows Publisher c:\windows\system32\mswsock.dll + MSAFD NetBIOS [\Device\NetBT_Tcpip_{48B1C096-3947-4F43-8383-4751845BE020}] DATAGRAM 5 Microsoft Windows Sockets 2.0 Service Provider (Verified) Microsoft Windows Publisher c:\windows\system32\mswsock.dll + MSAFD NetBIOS [\Device\NetBT_Tcpip_{48B1C096-3947-4F43-8383-4751845BE020}] SEQPACKET 5 Microsoft Windows Sockets 2.0 Service Provider (Verified) Microsoft Windows Publisher c:\windows\system32\mswsock.dll + MSAFD NetBIOS [\Device\NetBT_Tcpip_{DA61C3E3-2C4C-49EC-914A-43E2BD39BB82}] DATAGRAM 0 Microsoft Windows Sockets 2.0 Service Provider (Verified) Microsoft Windows Publisher c:\windows\system32\mswsock.dll + MSAFD NetBIOS [\Device\NetBT_Tcpip_{DA61C3E3-2C4C-49EC-914A-43E2BD39BB82}] SEQPACKET 0 Microsoft Windows Sockets 2.0 Service Provider (Verified) Microsoft Windows Publisher c:\windows\system32\mswsock.dll + MSAFD NetBIOS [\Device\NetBT_Tcpip_{F1107D55-F085-4820-81B9-4EF15C564736}] DATAGRAM 1 Microsoft Windows Sockets 2.0 Service Provider (Verified) Microsoft Windows Publisher c:\windows\system32\mswsock.dll + MSAFD NetBIOS [\Device\NetBT_Tcpip_{F1107D55-F085-4820-81B9-4EF15C564736}] SEQPACKET 1 Microsoft Windows Sockets 2.0 Service Provider (Verified) Microsoft Windows Publisher c:\windows\system32\mswsock.dll + MSAFD NetBIOS [\Device\NetBT_Tcpip_{FA682C52-60A2-46E2-9E1C-4893C61441AB}] DATAGRAM 2 Microsoft Windows Sockets 2.0 Service Provider (Verified) Microsoft Windows Publisher c:\windows\system32\mswsock.dll + MSAFD NetBIOS [\Device\NetBT_Tcpip_{FA682C52-60A2-46E2-9E1C-4893C61441AB}] SEQPACKET 2 Microsoft Windows Sockets 2.0 Service Provider (Verified) Microsoft Windows Publisher c:\windows\system32\mswsock.dll + MSAFD Tcpip [RAW/IP] Microsoft Windows Sockets 2.0 Service Provider (Verified) Microsoft Windows Publisher c:\windows\system32\mswsock.dll + MSAFD Tcpip [TCP/IP] Microsoft Windows Sockets 2.0 Service Provider (Verified) Microsoft Windows Publisher c:\windows\system32\mswsock.dll + MSAFD Tcpip [UDP/IP] Microsoft Windows Sockets 2.0 Service Provider (Verified) Microsoft Windows Publisher c:\windows\system32\mswsock.dll + RSVP TCP Service Provider Microsoft Windows Rsvp 1.0 Service Provider (Verified) Microsoft Windows Publisher c:\windows\system32\rsvpsp.dll + RSVP UDP Service Provider Microsoft Windows Rsvp 1.0 Service Provider (Verified) Microsoft Windows Publisher c:\windows\system32\rsvpsp.dll
I looked at your instructions on winsock repairs but did not follow them as I have no problems connecting to the internet – if you meant for me to try this, please let me know.
I do apologize for not following your instructions on the bottom post….
Thanks so much for you kind attention.
Chuck - 24 Jan 2006 00:16 GMT >> >> >> >I orginally posted this issue in the wireless forum - a couple of kind folks >> >> >> >tried to help but so far to no avail. I manage to isolate the problem to my [quoted text clipped - 202 lines] >> <http://nitecruzr.blogspot.com/2005/05/how-to-post-on-usenet-and-encourage.html#T opPosting> >> http://nitecruzr.blogspot.com/2005/05/how-to-post-on-usenet-and-encourage.html#T opPosting
>Chuck, right it is definitely not an admin share. In my desperation I even >set up a share for another folder also not admin same result. <SNIP>
>I looked at your instructions on winsock repairs but did not follow them as >I have no problems connecting to the internet if you meant for me to try [quoted text clipped - 3 lines] > >Thanks so much for you kind attention. Looks normal, Pam. I wonder could this be 885250 again? <http://nitecruzr.blogspot.com/2005/11/irregularities-in-individual-share.html> http://nitecruzr.blogspot.com/2005/11/irregularities-in-individual-share.html
Is shares permissions setup properly? <http://nitecruzr.blogspot.com/2005/06/file-sharing-under-windows-xp.html#Help> http://nitecruzr.blogspot.com/2005/06/file-sharing-under-windows-xp.html#Help
 Signature Cheers, Chuck, MS-MVP [Windows - Networking] http://nitecruzr.blogspot.com/ Paranoia is not a problem, when it's a normal response from experience. My email is AT DOT actual address pchuck mvps org.
Pam - 27 Jan 2006 11:26 GMT Chuck, I'll top post this one because it is the end.
YEAH! I turned off simple file sharing - deleted the share, restart, created a share, and restarted. Voila!
Somehow I missed the link that suggested that the first two times I worked my way through the links. In any case, that worked. I guess I'll never know what really caused it.
In any case, thank you so so much for your help and for your blog. You are the best.
> >> >> >> >I orginally posted this issue in the wireless forum - a couple of kind folks > >> >> >> >tried to help but so far to no avail. I manage to isolate the problem to my [quoted text clipped - 223 lines] > <http://nitecruzr.blogspot.com/2005/06/file-sharing-under-windows-xp.html#Help> > http://nitecruzr.blogspot.com/2005/06/file-sharing-under-windows-xp.html#Help Chuck - 27 Jan 2006 15:27 GMT Thank you, Pam. Glad to help.
>Chuck, I'll top post this one because it is the end. > [quoted text clipped - 235 lines] >> <http://nitecruzr.blogspot.com/2005/06/file-sharing-under-windows-xp.html#Help> >> http://nitecruzr.blogspot.com/2005/06/file-sharing-under-windows-xp.html#Help
 Signature Cheers, Chuck, MS-MVP [Windows - Networking] http://nitecruzr.blogspot.com/ Paranoia is not a problem, when it's a normal response from experience. My email is AT DOT actual address pchuck mvps org.
Kevin - 28 Dec 2007 05:54 GMT I am having a similar problem. I have a XP Media Edition hooked up to a wireless router. Also hardwired to the router is an XP Home Edition. I also have a Vista Laptop that is wireless. THe problem is I can';t access my files, even thouh it appears they are fully shared, that are on my XP Home machine. Any suggestions?
> >I orginally posted this issue in the wireless forum - a couple of kind folks > >tried to help but so far to no avail. I manage to isolate the problem to my [quoted text clipped - 36 lines] > <http://nitecruzr.blogspot.com/2005/06/mysterious-error-5-aka-access-denied.html> > http://nitecruzr.blogspot.com/2005/06/mysterious-error-5-aka-access-denied.html Robert L. (MS-MVP) - 28 Dec 2007 16:18 GMT Also check the permissions in the Security tab. Or this search result may help. Please post back with the result.
Vista Permission IssuesCan I assume the external drive used to be connecting to other computer and you just re-connect it the the Vista? Check the permission using this command: . ... www.chicagotech.net/vista/vistapermission.htm
 Signature Bob Lin, MS-MVP, MCSE & CNE Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
>I am having a similar problem. I have a XP Media Edition hooked up to a > wireless router. Also hardwired to the router is an XP Home Edition. I [quoted text clipped - 51 lines] >> <http://nitecruzr.blogspot.com/2005/06/mysterious-error-5-aka-access-denied.html> >> http://nitecruzr.blogspot.com/2005/06/mysterious-error-5-aka-access-denied.html
|
|
|