Member Avatar for secret-code

Hii

I have a work network and all computers have the same workgroup name, but the workgroup is a part of whole bulding network.

I wanted to restrict access to on of the computers to only employees at the office and I enabled guest account on that computer an set a password to it.

after that all users who want to open that computer must provide the username of "Guest" and its password.

everything went fine...
but later computers with windows 7 installed always had the problem saying that username or password is wrong (while the password entered is the right one)

so what might be happened ??? and how to fix it ?
and is there another way to protect a computer in a workgroup from unauthorized access ?

thanks in advance

  • 2 Contributors
  • 2 Replies
  • 213 Views
  • 1 Day Discussion Span
  • Latest Post Latest Post by secret-code

Dani AI

Generated

A few clarifications before troubleshooting steps: the workgroup itself has no shared “workgroup password” (so ’s suggestion about a workgroup password is incorrect). The built‑in Guest account is a special, limited account and Windows often blocks or restricts network logons for Guest for security reasons — enabling Guest + a password is fragile and commonly causes the exact “wrong username/password” behavior you describe. (learn.microsoft.com)

Actionable troubleshooting to try now:

  • Confirm the Guest password actually works at the target PC by logging in at its console (this rules out a simple mismatch).
  • From a Windows 7 client, force authentication to the remote machine (don’t rely on automatic cached credentials). Map a drive or run a test like:
net use \\TARGET-PC\Share /user:TARGET-PC\Guest YourPassword

or when using Explorer choose Map Network Drive -> Connect using different credentials and enter TARGET-PC\Guest. If you have saved/cached credentials, remove them from Credential Manager and try again. (daniweb.com)

Better long‑term fix and security notes:

  • Do not rely on the built‑in Guest account. Create a local, standard user account on the protected PC for office staff, give it a strong password, then set the share and NTFS permissions to that user. Password‑protected sharing in Windows requires a matching user on the host (or you must turn password‑protected sharing off — not recommended). This is cleaner, auditable, and avoids Guest policy restrictions. Also consider restricting SMB access with the host firewall or your network/router to office IPs only. (learn.microsoft.com)

Quick checklist: (1) verify local login on target, (2) clear stored credentials, (3) test with TARGET-PC\username or net use, (4) create a dedicated local account and apply share/NTFS permissions, (5) if problems continue check Local Security Policy -> User Rights Assignment for any deny rules that include Guests. (learn.microsoft.com)

This sequence will both diagnose why Win7 clients see “bad password” and give a secure, practical alternative to using Guest.

Recommended Answers

All 2 Replies

Member Avatar for mjdodd

There are two password levels with win 7, one is the actual user password and many are the times I have had clients swear their passwords were correct only to find that they had the capos lock on or were using the wrong password.

However id everyone is having this problem then you need to check that the win 7 workgroup password is the same on all the computers as the workgroup has to have a password as well in win 7.
M

Member Avatar for secret-code

thanks mjdodd ..
I've tried the password on 3 computers and caps lock is off
but what I'm talking about is not a password concerning the whole work group...

you can consider it as a password protecting access to that computer only
and that's what I meant with activating guest account and set a password to it !

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.