• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

wtf. Creating a share in Win2k3 and getting denied access

I setup a share called "stuff" on a server named BACKUP running Win2k3 Web Edition. I have 4 other servers that all need to map a drive to this share. I created a user for each server on the BACKUP server. I gave each user read and write permissions on the share and the folder. I've successfully got one machine to map a drive using its respective username, but when I try to map a drive using the other machines, I get denied stating that only one user can map to the share and that I must disconnect the other share first..
 
"Designed for dedicated Web serving and hosting, Windows Server 2003 Web Edition, delivers a single-purpose solution for Internet service providers, application developers, and others who use or deploy specific Web functionality"

I'm gonna guess that is by design and the concurrent share limit is set to one (unless I'm wrong and you set it yourself to 1 when setting up the share...)
 
Originally posted by: bsobel
"Designed for dedicated Web serving and hosting, Windows Server 2003 Web Edition, delivers a single-purpose solution for Internet service providers, application developers, and others who use or deploy specific Web functionality"

I'm gonna guess that is by design and the concurrent share limit is set to one (unless I'm wrong and you set it yourself to 1 when setting up the share...)

i thought it might be due to that specific version, but I tried using the ip in teh share path instead of the servername and it works...
 
So you've changed the Share permissions (and NTFS it sounds like you covered)? 2K3 creates share permissions with Everyone: RO by default.
 
Maybe it's something to do with the ten connection limit.

"Dedicated Web-serving functionality.

Supports two-way symmetric multiprocessing, 2 gigabytes (GB) of RAM, and 10 in-bound server message block (SMB) connections for content publishing."


And this Microsoft Link.

"Since Web Edition is limited to 10 in-bound server message block (SMB) connections for content publishing, Windows CALs are not required."

Check out the "Computer Management / Shares" screen on the Server and see how many Client Connections that server has. Maybe you are already right at the limit and the addtiional connections are refused.

A LOT of Server 2003's features are disabled in the Web Edition. It's almost more like XP Pro than it is full Server 2003.
 
Back
Top