[win7] Network sharing files and printers


Recommended Posts

Ok so I have three Windows 7 computers(two laptops, one desktop with a printer) I am having a great deal of trouble getting a consistent, easy to use network setup so I can browse files and use the printer between these computers.

I have tried setting up a Homegroup, but it seems very fickle; the printer is often detected as not connected and sometimes other machines in the homegroup don't appear, yet that machine will appear on the other machines

Also If my user on the desktop is not logged in on the desktop I can't see it on the homegroup on my laptop so I have to go and login, which is annoying.

Also what is with the "lock" icon that comes up on some folder icons? It seems to indicate that the folder is not shared, yet lots of folder aren't shared and don't have this icon until you specify "share with... nobody".

Any help with this would be great! Thanks!

  • 3 weeks later...

Have you shared the printer from the desktop?

From your Devices and printers list, right-click your printer and select Printer Properties. Click the Sharing tab, then select the box to share the printer.

Also, from the Network and Sharing Center, go into your Advanced Sharing Settings and make sure that Network Discovery, & File and Printer Sharing are enabled. Do this from the laptops as well.

Last, make sure that the user account you're using to connect to the files or printers exists on the host PC as well as the connecting PCs, and has been granted access to the shared items.

Not a fan of homegroups - I understand they were trying to make it easier for the normal user. I personally think it has been an utter failure, they made it way more complicated than it needed to be. Why they brought IPv6 into the mix is beyond me!

I would make sure you have homegroups disabled and just use normal file sharing. You don't have to be logged into a machine for that to work ;)

Most of the issues with file sharing come down to firewalls -- are you running a 3rd party one, antivirus suite, etc.?

First thing I would do is verify you can ping the the computers by name, if not name then IP -- once we have ping working (connectivity verified) with IP, then we can work out any name resolution issues.

From there we can work out the permissions problem that would prevent access to share.

Have you shared the printer from the desktop?

From your Devices and printers list, right-click your printer and select Printer Properties. Click the Sharing tab, then select the box to share the printer.

Also, from the Network and Sharing Center, go into your Advanced Sharing Settings and make sure that Network Discovery, & File and Printer Sharing are enabled. Do this from the laptops as well.

Last, make sure that the user account you're using to connect to the files or printers exists on the host PC as well as the connecting PCs, and has been granted access to the shared items.

1. Printer is shared and everything. I can see it in devices but it's faded out.

2. Yep all this is on. It was all working fine a few days back.

3. But this was never necessary before. I would simply go to network and login as an admin and have access to that users files. I can share files like this between other machines.

Not a fan of homegroups - I understand they were trying to make it easier for the normal user. I personally think it has been an utter failure, they made it way more complicated than it needed to be. Why they brought IPv6 into the mix is beyond me!

I would make sure you have homegroups disabled and just use normal file sharing. You don't have to be logged into a machine for that to work ;)

Most of the issues with file sharing come down to firewalls -- are you running a 3rd party one, antivirus suite, etc.?

First thing I would do is verify you can ping the the computers by name, if not name then IP -- once we have ping working (connectivity verified) with IP, then we can work out any name resolution issues.

From there we can work out the permissions problem that would prevent access to share.

1. I have no Homegroups set up. Out of a desktop and 2 laptops (all win7) my laptop to the desktop is the only time I get this error. my Laptop is also the only 64bit. But I can go to the other win7 laptop with no issues...

2. I am using windows firewall and MSE. Should I turn them off?

3. I can ping fine with name or IP.

Throwing it out there but what about AP Isolation... potentially?

What's this?

^ possible, but sounded like it was working on and off? But sure that is a common cause to sharing between wireless and wired or wireless to wireless sure.

Quite often I see that wireless is on the network next door for why they can not access their wired stuff as well ;)

edit: Well if you can ping by name and ip, then that is not an issue.

do a simple

net view \\dell-pc

if that is the name from box your want to access the share with.. You get access denied error 5?

Do that from the dell pc as well so we can see your shares.

If you just getting access denied, error 5 - then from a cmd prompt do a simple auth

net use * \\dell-pc\sharename /u:dell-pc\usernameondellpc passwordofuserondellpc

keep in mind that blank is NOT a password. This will map next drive letter open to that sharename

So did you then auth to the dellpc with a user account from dellpc

what is the output of net view \\dellpc on the dellpc -- what do you have shared and what are the permissions on the shares?

What accounts are you logged into on the different machines. Its common to use passthru, ie same username and password on both machines - this can be used to give access to shares with automatic auth via matching credentials, etc.

Ok yes! The auth thing worked.

Now I have a "network location" under "my computer" on the laptop. I can also now access the dellpc under "network" with out the error.

But why do I need this "network location" for the dellpc and not the other laptops?

net view \\dellpc on the dellpc shows the printer and the users folder as shared. what are the permissions I need to check?

Also the dellpc doesn't ask for any username or password on when being acessed from one of the laptops. For either of the laptops to access each other I just click the machine under network and give the username and password.

Comes down to your share permissions or username and passwords you have on your boxes.

Are you sharing to everyone or anonymous? What are the ntfs permissions as well. Share and ntfs are different permissions.

Everyone group does not = anonymous depending on your OS and or if you have made a registry change, etc.

UAC can also come into play in accessing. If you auth while elevated as administrator, you may not be able to access while not elevated. And vice versa - depending on some settings that might be set you maybe not be able to access an admin share, ie c$, d$, admin$ -- these were turned off starting with vista - have to set registry to allow them again.

There are lots and lots of things that can come into play.

But very simple -- you need to set the share and ntfs how you want, and then you need to auth with an account on that machine that is allowed under the permissions you set. Be it your prompted when you try and access, or if you send the auth in one command like the command I showed you.

So by default you might create a session to the machine as guest, guest has been denied access! So your screwed until you kill that session and then auth with an account that has permission. You can only ever be authed to machine from another machine with one account at a time.

If you don't have at least 1 share open to guest -- your going to get denied, and once that session is there your never going to be able to auth as a different user.

Also on Windows 7 make sure both computers network connections are set to either Work or Home, if doing a homegroup, the best is to have them set to home. I've seen people have intermittent issues where they would have a laptop that would work fine when it was hard wired in (with the hard wire set to a home network) but when they changed to wireless nothing would work (because the wireless connection was set to public) If you have both adapters enabled, and the laptop is both on the wireless and hardwired with two different network preferences setup, it can cause all hell to break loose.

@BudMan

Alot of that probably goes over my head. I don't really know what permissions should be or what I change them to or under which window. I tried comparing permissions of the shared Users folder between each machine and there is nothing different that I can see.

I tried to just set up a homegroup but still the dellpc won't let my laptop access it.

ugh... this is just frustrating.

EDIT: ok I think I did it. Don't ask me how exactly, but I can simply go properties>sharing>advanced sharing>share this folder and I can access files between with all machines.

That's good enough for me.

Thanks BudMan & others for your help!

"I can simply go properties>sharing>advanced sharing>share this folder and I can access files between with all machines"

Yup that is how simple it is suppose to be!!

And what share permissions are listed there?

post-14624-0-77768000-1337341879_thumb.j

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • The machines are starting to fight back any way they can.
    • No news articles about the Arch Linux repo being majorly infected with malware?!?
    • Waymo recalls self-driving software after cars enter closed freeway work zones by Paul Hill Waymo, the self-driving car maker owned by Alphabet – the parent company of Google –, has recalled some of its fifth-generation Automated Driving Systems (ADS). It did so after some of its cars drove through closed construction zones. According to the National Highway Traffic Safety Administration (NHTSA), the affected vehicles were capable of driving through a closed freeway construction zone and continuing to drive at speed. The listing on the NHTSA website says that Waymo is currently developing a solution to fix this issue, but in the meantime, freeway driving is being restricted. Waymo will update its ADS software so that vehicles can detect when they can avoid entering construction zones. According to the Safety Recall Report, on April 20, 2026, Waymo’s Field Safety Committee began meetings reviewing an event from April 11, 2026, and five events from April 19, 2026, where Waymo’s autonomous vehicles didn’t recognize and drove past ramp closure signs into the pre-planned freeway construction zones. This took place in Phoenix, Arizona. Separately, on May 18, 2026, seven Waymo vehicles entered freeway lanes with active construction in the San Francisco Bay Area by driving between cones that were placed to show the lane was closed. On the back of both of these events, Waymo restricted freeway driving until it could address the issue. In June, Waymo’s Safety Board reviewed the issue and additional information related to ADS performances around construction zones; then, as a result, it decided to conduct a recall. This development is not good for Waymo as it adds to a growing list of technical hiccups its cars have experienced. Ultimately, it will lead to more scrutiny from lawmakers around the world who will be more cautious about letting autonomous vehicles on their roads without tighter regulation. For readers in areas where Waymo operates, does this news make you more wary about stepping into one of these vehicles?
    • I'm still on Windows 10 22H2 because I didn't want to deal with all the issues in Windows 11, so I waited almost a week before installing the latest Patch Tuesday update (KB5094127), I went ahead and did it, and it was a huge mistake—ever since then, my File Explorer has seen a performance drop of about 30% when transferring large files... Once again, Microsoft has outdone itself! This update cannot be uninstalled, either through the Control Panel (via Settings) or by accessing Advanced Startup Options. The only possible alternative would be to use system restore points, but I’d have to reinstall all app and driver updates (and there’s no guarantee it would work). Or there’s the “nuclear option” of a in-place repair without losing files or apps, but even then, all my customizations would be lost! Microsoft just can’t help but mess everything up! Way to go, Microsoft! But I still don’t want your c****y Windows 11!
    • Microsoft: Windows 11 could finally solve a major issue across AMD, Nvidia, and Intel GPUs by Sayan Sen While Microsoft has been trying to improve it, Windows 11 is definitely not flawless, as even today some issues are taking a year to publicly acknowledge. However, one area of trouble that may finally see much better results soon is graphics driver crashes. Work on graphics driver timeouts, also called Timeout and Detection Recovery (TDR), is not new as the latest WDDM 3.2 also has specific improvements regarding it. Windows Display Driver Model (WDDM) version 3.2 is supported on Windows 11 24H2 and 25H2. However, with the upcoming version 26H2, TDR crash diagnosis could go to the next level as Microsoft is introducing a new DirectX 12 API feature called "DirectX Dump Files". Similar to how system memory dump files work when a system crashes or freezes or encounters any such major issue, DirectX Dump Files (DDF) will essentially record a snapshot of the GPU execution right at the moment a graphics-related crash or hang or freeze occurs, so that developers can better understand and diagnoze these TDR and timeout detection errors. The dump will be available as a .dxdmp file for analysis and it will be a comprehensive dump file generated with detailed insights about the hardware, drivers, Windows, as well as the affected application. This should be another welcome change in this department. Earlier at GDC 2026, when the technology was first debuted, Microsoft had shared more details regarding it. The company had explained how DDF is designed to gather data from every layer of the graphics stack into a single file, eliminating the need for developers to manually correlate logs from multiple tools. As mentioned above, the dump can contain a lot of useful details like GPU hardware state information such as register values, shader program counters, page fault virtual addresses, shader memory data, and command buffers. Alongside that, it also captures DirectX runtime and kernel information, including D3D objects, pipeline state objects, device error data, adapter details, and CPU call stacks. Microsoft says the feature has been built around two primary use cases: retail device removals and local device removals. The former allows developers to collect crash information from end users' systems in the field, while the latter helps QA teams and developers investigate issues on test machines. Developers will also be able to include up to 2 MB of custom application data through new D3D12 APIs, providing additional context for troubleshooting. In addition, Microsoft is introducing three dump collection modes ranging from zero-overhead capture, which has no runtime performance impact on supported hardware, to higher-detail modes that collect more vendor-specific debugging data. On compatible Tier 2 hardware, zero-overhead dumps will be enabled by default, meaning developers may begin receiving useful crash diagnostics without making any code changes. The table below explains the three tiers: Tier Description NO_OVERHEAD Enables crash capture with no runtime cost and is suitable for broad deployment MEDIUM_OVERHEAD Provides a balance, capturing additional diagnostic data with moderate impact HIGH_OVERHEAD Collects the most detailed GPU and driver state available, enabling deeper investigation at the cost of higher runtime overhead In terms of availability, the company expects broader release to be around the fall of 2026, which should be right around the time when Windows 11 version 26H2 lands. Right now, DirectX Dump Files are available as a preview and currently, only AMD has the compatible AgilitySDK Developer Preview driver version 26.10.07.02. You can find the official announcement post here on Microsoft's website.
  • Recent Achievements

    • Week One Done
      Eurosoft10 earned a badge
      Week One Done
    • One Month Later
      Eurosoft10 earned a badge
      One Month Later
    • One Year In
      Skeet Campbell earned a badge
      One Year In
    • One Month Later
      Sharbel earned a badge
      One Month Later
    • First Post
      BizSAR earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      599
    2. 2
      +Edouard
      190
    3. 3
      PsYcHoKiLLa
      79
    4. 4
      Michael Scrip
      77
    5. 5
      Steven P.
      70
  • Tell a friend

    Love Neowin? Tell a friend!