• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 721
  • Last Modified:

File sharing over a network

HI all,

I have a server running Windows Server 2003 Web, this is a workgroup and not a domain.  I have made a folder on the C: Drive and I want to share it on the network.  I have done everything I can think of, including reading way too much documentation, to no avail.  Anyway.  I have made a user and set their permissions to full access.  From a client machine, I can browes to the folder but when I try to access it, I get an error message that says:' \\Acctserver\Weatherization is not accessible.  You might not have permission to use this network resource.  Contact administrator of this server to find out if you have access.  Access Denied.'  I checked the regisry value of HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Control/LSA/restrictanonymous. to make sure it was set to 0 on both the server and the client.  They are both set to 0.  I would love to check the firewall but, I get another error that I cant because some other application might be using NAT.  I have also been trying to figure that one out.  Anyway, this used to be very simple with Windows Server 2000, but, I cant think of why my users do not have access. Any thoughts from anyone?  Another interesting thing with this, is that my other server, a windows 2000 server, can access the shared file with no problems.  None of my XP Pro client can however.  

Thanks in advance.

1 Solution
There's two steps to sharing a folder with Server 2003. Right clicking the folder and going to Sharing and Security, the Sharing tab displays first. This tab has a Permissions button, which you should click on and make sure "Everyone" has full permission. Then in the Security tab, you want to make sure you give appropriate permission to all of your users. I prefer the advanced tab, as it shows all of the allows and denies seperately. IIRC, a deny will always override an allow . . .
jwoodhamsAuthor Commented:
I have set the permissions to allow everyone to have full permission, and also assigned full rights to users on the security tab and still the same.  
vguzmanIT ManagerCommented:
Check that the service "server" is started and set to "automatic" in your SERVER and also check that the service "workstation" is started and set to "automatic" in your CLIENT PC.
Cloud Class® Course: Python 3 Fundamentals

This course will teach participants about installing and configuring Python, syntax, importing, statements, types, strings, booleans, files, lists, tuples, comprehensions, functions, and classes.

vguzmanIT ManagerCommented:
Also, how is your network setup ?  all the computers and servers connected to the same switch or router ? do they all have the same netmask?  can you PING the server ?
Use IPCONFIG /ALL to check that info on all the pcs before to go any further.
jwoodhamsAuthor Commented:
Hi Thank you vguzman,

Server service is started and automatic on server.  Workstation is started and automatic on client.  I can ping the server, all use the same netmask, and all workstations share the same 4 switches (uplinked).
vguzmanIT ManagerCommented:
Do you have all the updates installed in your server and client PC ?
Are you using WINS in your server ?
Are you manually setting up the IPs on the client PCs or they are setup to automatic ? Can you post the IPCONFIG of the client PCs ?
jwoodhamsAuthor Commented:
I do have all the current updated installed.  Just made sure this morning.  Also, I am not using WINS.  And I am getting the IPs automatically through DHCP.  Here is the ipconfig/all of the client:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Aaron>ipconfig/all

Windows IP Configuration

        Host Name . . . . . . . . . . . . : D027HS
        Primary Dns Suffix  . . . . . . . :
        Node Type . . . . . . . . . . . . : Unknown
        IP Routing Enabled. . . . . . . . : No
        WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

        Connection-specific DNS Suffix  . :
        Description . . . . . . . . . . . : Realtek RTL8168/8111 PCI-E Gigabit E
thernet NIC
        Physical Address. . . . . . . . . : 00-E0-4D-3A-1F-D2
        Dhcp Enabled. . . . . . . . . . . : Yes
        Autoconfiguration Enabled . . . . : Yes
        IP Address. . . . . . . . . . . . :
        Subnet Mask . . . . . . . . . . . :
        Default Gateway . . . . . . . . . :
        DHCP Server . . . . . . . . . . . :
        DNS Servers . . . . . . . . . . . :
        Lease Obtained. . . . . . . . . . : Friday, November 21, 2008 1:26:35 PM

        Lease Expires . . . . . . . . . . : Sunday, December 21, 2008 1:26:35 PM

C:\Documents and Settings\Aaron>
vguzmanIT ManagerCommented:
I seems like your subnet mask is wrong.  If you want to use the "" IP your subnet mask MUST be ""
Change that in you DHCP settings on your server and "renew" the IP of your computer and try to browse the contents of your sharefolder again.
Also check the "local policies" of your server. (I just received this as an answer in another question I have pending)
Try enabling  the guest account and then:
GO to start run -- gpedit.msc -- Windows settings -- Security Settings -- local policies -- security options --
Network Access:  Let everyone permission apply to anonymous users -- set to enable
Network Access:  Shares that can be accessed anonymously - add the share name
Now give everyone rights to the folder you are sharing.
Good luck.
jwoodhamsAuthor Commented:
Thanks very much, I did enable permission for anonymous users and that did the trick.

What you need to do is create a user with SAME username and password on the client machine. Another way you can also do this is by mapping a drive with alternate user/pass option.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

The 14th Annual Expert Award Winners

The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now