I know it is a bit archaic, but remember that this is a workgroup configuration.
Main Topics
Browse All TopicsI can't get a Windows / XP client to map to a shared folder on a Windows 2003 Server in a workgroup environment. Alll the other clients are mapped with no problem. I verified IP connectiviity and passwords and account lockout. Any suggestions?
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Yes, I understood that. It was just a suggestion to promote it to domain for improving functionality/security and simplifying management. Workgroup management will give alot more management as all settings nead to be done locally on each host instead of centralize it in domain management.
The important thing independent of having workgroup or domain is that both sides of the client/server communication nead to match the security settings.
SMB-signing requirement on one side and the other side doesn't support/respond the requirement will make the connection fail.
Do you get any error message when trying to connect?
Any error in eventlog (any side) when trying to connect?
accept http:#24484216
Business Accounts
Answer for Membership
by: henjoh09Posted on 2009-05-27 at 08:31:02ID: 24484216
What error do you get? network path not found, access denied etc
With workgroup environment, same username and password nead to exist on both client and server.
It can be a SMB-signing problem as client/server nead to atleast respond if the other side requires it.
In local policy, check following security options
\Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options
Microsoft network client: Digitally sign communications (always)
Microsoft network client: Digitally sign communications (if server agrees)
Microsoft network server: Digitally sign communications (always)
Microsoft network server: Digitally sign communications (if client agrees)
Other security options like 'Network security: LAN Manager authentication level' can also cause problem if one side of client/server communication requires higher level compared to the other side.
As you have a server running Windows Server 2003, why not just run dcpromo on the server to promote it as DC and join the client computers to the AD-domain? You'll get better security, less user administration, centralize user/policy management etc.