I have an evaluation version of Windows Server 2003 Enterprise Edition with SP1. It is currently acting as an WSUS server for around thirty clients while sitting behind a NAT router. On the local side of the router, the server provides DNS and WINS services to various Mac, Linux, and Windows clients. IIS 6 is configured with the URLScan utility to enhance security in addition to WS2003 SP1's firewall.
I would like to place a single file share on the server, and have that share be read-only. The share is located on a different partition from the system volume and is configured. Share permissions are configured to their default values of "Everyone - Read" and NTFS permissions are configured to their default levels, "SERVER\users - Read and Execute". Active Directory is not a part of this equation in any manner. There are two accounts on the server, the admin, and a standard user account. The local PCs have a standard account that utilizes the same username and password and the server's local account.
When I try to access the share via UNC path, \\SERVER, a prompt appears asking for a password. I expected this, but the username is "guest" and is greyed-out. The guest account is disabled on the server, and has no future of being enabled. WS2003 is insecure as it is without the guest account turned on. If I try to access the share via UNC from a Vista RC2 machine, I get a prompt but this time the username and password are blank. Any combination of username and password will not work.
What gives? Is this one of WS2003's undocumented features?