?
Solved

Windows 7 in a workgroup with network shares

Posted on 2010-01-04
13
Medium Priority
?
1,211 Views
Last Modified: 2012-05-08
Hi,

I have joined a first Windows 7 machine in a WORKGROUP environment. Usualy, by settings the same user on both (computer & server) I can access the network shares on the server no problem. But with Windows 7 I can see them both (workgroup computers including server AND the network shares).

The problem is, when I try to map such network shares, it keeps refusing it because of network access rights. I have tried to use WORKGROUP\USER since win 7 won't let me use only the user name but without any success.

Any ideas ?
0
Comment
Question by:SirTKC
  • 5
  • 5
  • 2
  • +1
13 Comments
 
LVL 4

Expert Comment

by:ITSP
ID: 26171865
Try adding a new user to the server, then adding that user to the windows 7 machine and accessing a network share?

You could be having a profile problem, by adding a new user we are troubleshooting with a clean profile.... Try the above and get reply with your results.
0
 

Expert Comment

by:Tafaer
ID: 26171900
To verify, you're saying that all the computer can see each others' shares, but the Windows 7 Machine won't let you map a network drive to one of those shares?

Also, is it Windows 7 Home Premium, Professional, or ultimate?
0
 
LVL 59

Expert Comment

by:LeeTutor
ID: 26172032
Here is a good tutorial to share files and printers between Windows 7 and Windows XP:

http://www.howtogeek.com/howto/windows-7/share-files-and-printers-between-windows-7-and-xp/
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
LVL 3

Author Comment

by:SirTKC
ID: 26172498
Hi.
Let me try some of the solution proposed here and get back to you guys.
To answer some questions : It is Win 7 Pro. It can see networked shared folders but when I try to access it in the network neighbourhood OR by a share mapping, it wont let me do so because of a permission problem.
0
 

Expert Comment

by:Tafaer
ID: 26173945
I think I may have your answer:
When mapping a network drive in Windows 7 there's an option to "Connect using different credentials"
You can try this option and provide the credentials from the host(to be specific the computer w/ the shares).
Here's a pic:

Map-Network-Drive.JPG
0
 
LVL 3

Author Comment

by:SirTKC
ID: 26175146
Hi guys,

I have tried every single possibility without any success. It keeps telling me that the user name and/or password is incorrect.

I have tried login by using a different credentials, no result the same window keeps coming back "Windows security" asking me to enter "DOMAIN\User name" for a WORKGROUP network.

This is very annoying - I can ping the server no problem bu cant access it. I think that this station is stuck thinking and working like it is in a DOMAIN. I have tried loging in with the name of the server as well as the name of the local computer = no result.

I remember as before, we did not need to specify the domain with the username in order to connect a networked shared folder in a workgroup. Why cant we now ?
0
 

Expert Comment

by:Tafaer
ID: 26175219
Well, one thing you could do (and this really isn't that good) is to set permissions on the non-windows 7 machines to let the user "everyone" have full/read access.
0
 
LVL 3

Author Comment

by:SirTKC
ID: 26175370
I already done this - setting "everyone" full control to test if I can access the network share... without any success... That's the first time I see this and I know that if I turn this workgroup into a domain this will solve this issue.

So I think this is a setting maybe in the local GPO that forces Win 7 to use the combination DOMAIN\USER credential instead of only USER and password.

This is causing me a lot of problems....

Any idea ?
0
 
LVL 4

Expert Comment

by:ITSP
ID: 26175551
Disable all firewalls on the win7 machine and try again
0
 
LVL 3

Author Comment

by:SirTKC
ID: 26175783
Hi ITSP,

I already tried this (actually - this is one of the first thing I tried !). No success with this approach as well... :-(


0
 

Expert Comment

by:Tafaer
ID: 26181910
This shouldn't make a difference, but on the Windows 7 machine when you connected to the network did you set the network location as home. location as home?


Also you can try this:
from a command prompt issue the following commands
Net use g: \\<name or IP of computer>\<name of share> /persistent:yes

This will prompt you for a username and password, use the password for the machine w/ the share.
Then enter "explorer.exe g:" (without the quotes)
HomeNetwork.JPG
0
 

Expert Comment

by:Tafaer
ID: 26182574
I forgot to say that you can replace G: with whatever you want(and it would probably be better to choose higher letter to avoid conflict with any removable media you might connect in the future) and that will be the drive letter that your mapped drive.
0
 
LVL 3

Accepted Solution

by:
SirTKC earned 0 total points
ID: 26353227
HI guys,
Sorry for the late reply.
Well guess what, the problem was caused by the time difference between the two (client and server). There was (for a reason that I ignore) a difference of 12 hours back time on the server... As soon as the correct time has been set on the server, the client could connect in the workgroup env. normaly.
I read after that a difference exceeding 5 minutes will stop the kerberos authentication, rendering thereafter any login attempt impossible.
0

Featured Post

How to Use the Help Bell

Need to boost the visibility of your question for solutions? Use the Experts Exchange Help Bell to confirm priority levels and contact subject-matter experts for question attention.  Check out this how-to article for more information.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

The recent Microsoft changes on update philosophy for Windows pre-10 and their impact on existing WSUS implementations.
By default the complete memory dump option is disabled in windows . If we want to enable the complete memory dump for a diagnostic purpose, we have a solution for it. here we are using the registry method to enable this.
In this Micro Tutorial viewers will learn how to use Boot Corrector from Paragon Rescue Kit Free to identify and fix the boot problems of Windows 7/8/2012R2 etc. As an example is used Windows 2012R2 which lost its active partition flag (often happen…
This Micro Tutorial will go in depth within Systems and Security in Windows 7 and will go into detail regarding Action Center, Windows Firewall, System, etc. This will be demonstrated using Windows 7 operating system.
Suggested Courses

850 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question