Re: Problem Allolwing Remote Users Access to Files on Host Computer in WinXP Pro SP2

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



On Sat, 9 Jul 2005 15:08:47 -0500, "AA Smith" <*email_address_deleted*> wrote:

>Actually this is a peer-to-peer network (LAN,) so there's not really a Host
>per se. We have several computers in our network. I intend for all users
>on this LAN to have access through the network to shared files on this
>computer. For some reason that stopped working in the not-too-distant past,
>though it used to work fine.
>
>This apparently applies to all users on one computer in this LAN. Even me!
>For simplification, I'll refer to the computers involved as LAN1 and LAN2.
>LAN1 is what I refer to as the Host in that the files that users are trying
>to access reside on that computer. All users (User IDs) in the network are
>setup on LAN1 as users for LAN1. The same holds true for LAN2. And all
>users have the same User IDs on both computers. On LAN1, I opened the System
>Properties dialogue and clicked on the Remote tab.I checkmarked both boxes
>on that tab. I also clicked on the Select Remote Users button and entered
>all User IDs appear in the list. That would seem to be all I need to do to
>grant access to shared files on LAN1 to users on LAN2. However, when
>anyone, myself included, tries to access shared files on LAN1 from LAN2 they
>get an error message telling them that they don't have access to LAN1.
>
>What am I overlooking? How can I resolve this problem?

Dick,

The Remote Users dialogue in System Properties is for setting up Remote Access
(for controlling the desktop thru the network). If you want to setup access to
shared files or folders, you use the Properties wizard for the folder in
question from Windows Explorer.

When you use the wizard, remember to set permissions in both Sharing -
Permissions (for network access rights), and in Security (for local access
rights). Both local and network access rights are required for access over the
network.

If you've done that, and you're still getting "access denied" or similar, check:
# Registry setting restrictanonymous.
# Misconfigured / overlooked firewall.
# Browser conflict.
# Non-activated account.
# Non-synchronised passwords.

Check restrictanonymous on each computer.
<http://nitecruzr.blogspot.com/2005/07/restrictanonymous-and-your-server.html>

Look for any misconfigured or overlooked firewalls. What antivirus products do
you use?
<http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html>

Diagnose a browser conflict by running "browstat status" on all computers.
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#Browser>

Make sure the account selected from the shared folder Properties wizard is
properly activated on each computer.
<http://nitecruzr.blogspot.com/2005/06/file-sharing-under-windows-xp.html#Activate>

If the account being used is not Guest, make sure that passwords are
synchronised for the account between the two computers.
<http://nitecruzr.blogspot.com/2005/06/file-sharing-under-windows-xp.html#Synchronise>

--
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.
.



Relevant Pages

  • Re: The Hard Problem for Behaviorists
    ... correct low level abstractions to define the operation of the brain with - ... Do you not know how computers work? ... you can think of this type of network like you ... when you drop a marble in hole X1, ...
    (sci.cognitive)
  • Re: Networks : Workgroups and Domains. How Do I Use Them?
    ... I think the problem is from my lack of understanding whether these machines are together as a workgroup or domain. ... If I want to configure solely for a workgroup network, then I would think I do not need to provide a domain name, and vice versa for a domain network. ... It's not clear whether any of your computers is running Windows 2000 *Server.* If not, you don't have a "domain" and shouldn't be using domain names. ... Problems sharing files between computers on a network are generally caused by 1) a misconfigured firewall or overlooked firewall; or 2) inadvertently running two firewalls such as the built-in Windows Firewall and a third-party firewall; and/or 3) not having identical user accounts and passwords on all Workgroup machines; 4) trying to create shares where the operating system does not permit it. ...
    (microsoft.public.windowsxp.network_web)
  • Re: {workgroup}"...is not accessible" after removing NWLINK
    ... I generally reboot the machine whenever I make network ... >problem is a browse service that won?t run on the XP machine using the TCP/IP ... >?The browser has forced an election on network ... >> computer, and one, or preferably two, of the Windows 98 computers. ...
    (microsoft.public.windowsxp.network_web)
  • Re: Help with 070-217
    ... The network contains 25,000 computers. ... > single Windows 2000 domain named research.contoso.com. ... > Server computers that are configured as domain controllers. ...
    (microsoft.public.cert.exam.mcse)
  • RE: Help with 070-217
    ... The network contains 25,000 computers. ... > single Windows 2000 domain named research.contoso.com. ... > Server computers that are configured as domain controllers. ...
    (microsoft.public.cert.exam.mcse)