We have just setup a new office temporally in NYC. It was decided not to make this office a non-active directory site. I have a Windows 2003 server setup as a workgroup. When I type in the computer name in the run box the pop-up login box comes up as Computer\Guest account comes up. Is it possible to c$ a pc in a non-active directory domain environment?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
C$
- Thread starter magbag
- Start date
Yes.
The best way to handle this issue is to add as new local users of the Windows 2003 server the usernames and passwords of all XP Workstation users.
Do not use blank or empty passwords for users.
You can control access to any share through NTFS security permissions and share-level permissions.
The best way to handle this issue is to add as new local users of the Windows 2003 server the usernames and passwords of all XP Workstation users.
Do not use blank or empty passwords for users.
You can control access to any share through NTFS security permissions and share-level permissions.
Yes it is. I believe that AD has nothing to do with your current problem! (correct me if I'm wrong folks)
In any case, right click on 'My Network Places' and select 'Map Network Drive'
In this dialogue, as the drive to mount, type \\computername\c$
The click the button to use alternate credentials and type in;
computername/username (where the username is a valid user with appropriate privelidges for that machine) and enter the password.
This should explicitly provide a different username to guest, and bypass that annoying message.
Sorry if these instructions are a little vague, I'm stuck on NT4 here and all this information is coming from memory!
Good luck... hope this helps!
Terry-Lee Blay
MCP, A+, Net+, Server+, APS, IBM Thinkpads/Portables
In any case, right click on 'My Network Places' and select 'Map Network Drive'
In this dialogue, as the drive to mount, type \\computername\c$
The click the button to use alternate credentials and type in;
computername/username (where the username is a valid user with appropriate privelidges for that machine) and enter the password.
This should explicitly provide a different username to guest, and bypass that annoying message.
Sorry if these instructions are a little vague, I'm stuck on NT4 here and all this information is coming from memory!
Good luck... hope this helps!
Terry-Lee Blay
MCP, A+, Net+, Server+, APS, IBM Thinkpads/Portables
- Thread starter
- #4
Auger282
MIS
- Sep 27, 2003
- 978
the problem is that you have simple file sharing enabled..
in my computer go to Tools/ folder options/ View Tab/ Advanced settings area...
at the bottom you will find:
"Use simple file sharing (recommended)"
..I recommend you uncheck that box...
then you should be able to type in your own user and not be forced to use guest.
I hope that helps!
in my computer go to Tools/ folder options/ View Tab/ Advanced settings area...
at the bottom you will find:
"Use simple file sharing (recommended)"
..I recommend you uncheck that box...
then you should be able to type in your own user and not be forced to use guest.
I hope that helps!
This is Windows 2003 and not XP.
See issues #1 and #2 here for the rights adjustments required:
See issues #1 and #2 here for the rights adjustments required:
Users who can connect their computers to the network can access resources on remote computers that they have permissions for. For example, access this computer from the network user right is required for a user to connect to shared printers and to folders.
If this user right is granted to the Everyone group, and if some shared folders have both share and NTFS file system permissions configured so that the same group has read access, anyone can view files in those shared folders. However, this is an unlikely situation for fresh installations of Windows Server 2003 because the default share and the NTFS permissions in Windows Server 2003 do not include the Everyone group. For systems that are upgraded from Microsoft Windows NT 4.0 or Windows 2000, this vulnerability may have a higher level of risk because the default share and the file system permissions for these operating systems are not as restrictive as the default permissions in Windows Server 2003.
Users who can connect their computers to the network can access resources on remote computers that they have permissions for. For example, this user right is required for a user to connect to shared printers and to folders. If this user right is granted to the Everyone group, and if some shared folders have both share and NTFS file system permissions configured so that the same group has read access, anyone can view files in those shared folders. However, this is an unlikely situation for fresh installations of Windows Server 2003 because the default share and the NTFS permissions in Windows Server 2003 do not include the Everyone group. For systems that are upgraded from Microsoft Windows NT 4.0 or Windows 2000, this vulnerability may have a higher level of risk because the default share and the file system permissions for these operating systems are not as restrictive as the default permissions in Windows Server 2003.
If this user right is granted to the Everyone group, and if some shared folders have both share and NTFS file system permissions configured so that the same group has read access, anyone can view files in those shared folders. However, this is an unlikely situation for fresh installations of Windows Server 2003 because the default share and the NTFS permissions in Windows Server 2003 do not include the Everyone group. For systems that are upgraded from Microsoft Windows NT 4.0 or Windows 2000, this vulnerability may have a higher level of risk because the default share and the file system permissions for these operating systems are not as restrictive as the default permissions in Windows Server 2003.
Users who can connect their computers to the network can access resources on remote computers that they have permissions for. For example, this user right is required for a user to connect to shared printers and to folders. If this user right is granted to the Everyone group, and if some shared folders have both share and NTFS file system permissions configured so that the same group has read access, anyone can view files in those shared folders. However, this is an unlikely situation for fresh installations of Windows Server 2003 because the default share and the NTFS permissions in Windows Server 2003 do not include the Everyone group. For systems that are upgraded from Microsoft Windows NT 4.0 or Windows 2000, this vulnerability may have a higher level of risk because the default share and the file system permissions for these operating systems are not as restrictive as the default permissions in Windows Server 2003.
To all,
Regard above posts, I have a problem with XP pro machine. Can't connect to C$ event map network dirve with different user "computername/username (where the username is a valid user with appropriate privelidges for that machine) and enter the password".
This Novell network and NO AD active.
Thank you.
Regard above posts, I have a problem with XP pro machine. Can't connect to C$ event map network dirve with different user "computername/username (where the username is a valid user with appropriate privelidges for that machine) and enter the password".
This Novell network and NO AD active.
Thank you.
- Status
Similar threads