I have recently purchased a new server with Microsoft Server 2008 SP2. My company has never run with a true server before, so I am new to working with MS Server permissions. I can see all my work stations from the server and can access the 10 different work stations. What I can not do is access the server from the work stations. All of the workstation can see the server and the shared files, but when I try to access the server from the work stations, I get an error that the workstation does not have permission to access the server. What do I need to do to be able to access the server from the work stations. FYI I did purchase 10 CAL's when I purchased the server software.

To be able to access resources among the computers (workstations and server) in a non-domain environment, you will need to define the same local accounts on every single system. The next step is to create the resources such as file and print shares on the server and provide Share/NTFS permissions to the appropriate local accounts. When a user from another computer in the workgroup attempts to access the server resource, the local credentials (username and password) are used to gain access. The same user name and password needs to be defined on both systems (workstation and server).Visit: anITKB.com, an IT Knowledge Base.

Is it part of an AD domain? How did you access the server from workstation? Santhosh Sivarajan | MCTS, MCSE (W2K3/W2K/NT4), MCSA (W2K3/W2K/MSG), CCNA, Network+ Houston, TX http://blogs.sivarajan.com/ http://publications.sivarajan.com/ This posting is provided "AS IS" with no warranties, and confers no rights.

Right now there is no domain. I can see the server from the work stations but cannot access any files.

Perhaps the easiest way to establish the shares & to ensure controlled access over server resources would be to setup an Active Directory Domain. To establish this go to Run and key in 'dcpromp'. Prior to doing so I advise reviewing the below link so you're familar with the concepts and terminology & what features & involved & what procedures should be followed to ensure the envirionment can be restored in case directory services is corrupted. http://technet.microsoft.com/en-us/library/cc732887(WS.10).aspx http://technet.microsoft.com/en-us/library/bb727048.aspx

Prior to deciding to move forward with a domain design, make sure you a certain comfort level. Managing a few workstations in a workgroup is definatley not equivalent to keep a domain up and running. As I mentioned above, that if all you need is to share some files and folders amongst a few computers, a workgroup model is appropriate. However, as you scale out, yes, the domain model would provide a lower total cost of ownership (TCO).Visit: anITKB.com, an IT Knowledge Base.