?
Solved

File sharing LOGIN on Windows 2003 server

Posted on 2004-10-08
4
Medium Priority
?
166 Views
Last Modified: 2010-04-19
Hi want everybody on my network to access the files on my shared folder on my windows 2003 server Standard Ed.

So I set up the shared folder with group everybody having the permissions to access and read only permissions.

However, when the clients browse the network and try to access the server, they are getting prompt to login in. I don’t want to create accounts on that server for everybody on the network. I want them to just access that folder without the login.

Thanks in advance.
0
Comment
Question by:glowas
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
4 Comments
 
LVL 18

Expert Comment

by:luv2smile
ID: 12260677
Did you set both the share permissions and the ntfs permissions?
0
 
LVL 18

Expert Comment

by:luv2smile
ID: 12260709
If this is the scenerio that you want then you must set the NTFS permissions to allow everyone access because in windows 2003 the default NTFS settings are set to allow Users (not everyone) Read and Execute.

Right click the folder, properities, then go to the security tab- this is where you will find the NTFS permissions.
0
 

Author Comment

by:glowas
ID: 12261431
I did that, but it did not change anything.
The login with window name "connecting to [server_name]" shows up when you click on the server name in workgroup computers.
So I don't even see what is shared on that win 2003 server.
????
0
 
LVL 104

Accepted Solution

by:
Sembee earned 1000 total points
ID: 12264304
That is by design.
The server will be asking the clients for user credentials. Windows will try to use the same credentials that it is logged in as - which will only work if there are matching credentials on the server.

The only way you will get it to let the user in is to enable the guest account. That of course lets ANYONE in - which is a massive security risk.

However if you have Windows 2003 server why don't you setup a domain? These types of problems will go away as the credentials will pass through as part of the domain structure.
One set of username and passwords, one set of security, much simplier management.

Simon.
0

Featured Post

[Webinar] How Hackers Steal Your Credentials

Do You Know How Hackers Steal Your Credentials? Join us and Skyport Systems to learn how hackers steal your credentials and why Active Directory must be secure to stop them.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

The HP utility "HP Lights-Out Online Configuration Utility for Windows Server 2003/2008" could be of great use when it comes to remotely configure a HP servers ILO WITHOUT rebooting the server. We would only need to create and run scripts using thi…
This may not be a text book method to resolve VSS backup issues but it seemed to have worked on few of the Windows 2003 servers we had issues while performing a Volume Shadow Copy backup. If you have issues while performing a shadow copy backup usin…
NetCrunch network monitor is a highly extensive platform for network monitoring and alert generation. In this video you'll see a live demo of NetCrunch with most notable features explained in a walk-through manner. You'll also get to know the philos…
Have you created a query with information for a calendar? ... and then, abra-cadabra, the calendar is done?! I am going to show you how to make that happen. Visualize your data!  ... really see it To use the code to create a calendar from a q…
Suggested Courses

762 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question