• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 289
  • Last Modified:

Forcing permissions Windows 7 64-bit

My network server can't access a new client notebook.  The server runs Windows 7 32-bit and the notebook Windows 7 64-bit.  Other clients on the network, including a desktop running 32-bit Windows 7, can access the notebook, and the notebook can access the server.  I've tried changing ownership of the disc, including by logging on with the default administrator account, but access is denied.  I've tried assigning full privileges to Everyone, but access is denied.  Please advise.
3 Solutions
JAN PAKULAICT Infranstructure ManagerCommented:
1 can you ping the client from server? (by name and by IP)

2 turn off firewall on client and try

3  disable temporary antivirus and try

4 lastly Try that
ddantesAuthor Commented:
Thank you.  I can ping the client from the server, and no packets are lost.  
Firewall and Antivirus are managed by McAfee, which came factory installed.  Turning off the firewall did not fix the issue.  Turning off real time antivirus scanning did not help.  I have not visited the link you provided yet.
JAN PAKULAICT Infranstructure ManagerCommented:
Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

ddantesAuthor Commented:
I doubt it is a virus.  Other clients can access that client, and the client can access the server.  The server can access every other client.  There must be some unique issue with the server-client connection between these two machines.
JAN PAKULAICT Infranstructure ManagerCommented:
you could try 2 utitlities - depanding where the issue happens

1 if in application layer go with process monitor


run it just before you attempt to access server

Or if it is on cable try
2 Wireshark (packet sniffer)

ddantesAuthor Commented:
I just discovered that the issue doesn't happen if the notebook is booted into a second operating system, also 64-bit Windows 7.  No problem with network access.  So I am thinking there is something about the user profile with the first operating system which is blocking access.  Any thoughts?
JAN PAKULAICT Infranstructure ManagerCommented:
if it is a domain enviroment remove from domain and add again

 is user getting temporary profile?
ddantesAuthor Commented:
It is a Workgroup environment.  Sorry I don't understand the question about getting a temporary profile.
JAN PAKULAICT Infranstructure ManagerCommented:
In Regedit

KEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList

f you have two folders starting with S-1-5 followed by some long numbers and one of them ended with .bak, you have to rename the .bak folder. To do this, follow these steps:

JAN PAKULAICT Infranstructure ManagerCommented:
As it is a workgroup

if you run from cmd


and then type name of the server you cant access

are you getting the right ip? (for given server)

(under the user which doesn't work)
Shouldn't be anything to do with the userprofile.  You should be able to access the machine whether a user is logged on or not.
Check the local adminstrators group membership on the notebook and make sure the account you're using from the server is in there.  Since you're in a workgroup environment the account you use has to be present on both machines.
What is the UNC that you're trying to use?  Just "\\notebook\c$"?
JAN PAKULAICT Infranstructure ManagerCommented:
Footech is Right - it shouldn't be User profile - unless there is custom proxy setting in his IE settings??

if you open Internet Explorer  

On the Internet Explorer window, click on Tools, then click on Internet Options.

On the Internet Options window, click the Connections tab, then click on the LAN settings button.

  Make sure that the Proxy Server  box is unchecked.

David Johnson, CD, MVPOwnerCommented:
Windows 7 is not a server product, don't call it a server since it is just a workgroup computer.   All machines must be a member of the same workgroup i.e. WORKGROUP and a user with a password can be used for the shares.

shares have 2 levels of access (share level and NTFS file system level)
Daniel KlineSr. SharePoint DeveloperCommented:
With the clarification that you have a peer-to-peer network and not a client-server network, David is correct.  The workgroup name should determine access security.

Things to be aware of:
1.) Workgroups are NETBIOS names and should comply with NETBIOS standards.
2.) Workstation names likewise must comply with NETBIOS standards.
      There is no DNS service so the only way to resolve workgroup and Workstation names is by NETBIOS broadcast
3.) All workstations must be on the same network segment unless there is some type of NETBIOS over TCP routing.    (usually configured on the NIC).  NETBIOS is layer 2 and TCPIP is Layer 3.  NETBIOS will not route by default.
Another workaround is to add the IP address of the new notebook to the hosts file in Windows/System32/Drivers/etc on all the machines that need to access this workstation.

Good luck.  I hope this helps.
ddantesAuthor Commented:
Thank you.  However, adding the IP address of the new notebook to the hosts file did not help.   All network machines are members of the same workgroup and are on the same network subnet.

In User Accounts, I removed and then re-created stored credentials for accessing the notebook, and now it is accessible.

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now