Recommended Posts

Hi all,

I am trying to share some files with my sister's computer. I am using Vista whereas she is using Windows XP.

I shared her folder and then i typed this on my vista computer " \\192.168.0.102 " and then it says that it is not accessible. You might nothave permission to use this network resource. Please contact the adminsitrator.

Why is this so ?

Link to comment
https://www.neowin.net/forum/topic/575002-help-with-home-network-please/
Share on other sites

did you configure file sharing on your firewalls? Are you running any firewalls other than XPs or any type of security software that might block file sharing.. virus scanners no do more than just scan files, etc.

Is she on XP home or Pro? What permissions did you setup on the share? on the file folder?

http://support.microsoft.com/kb/304040/

How to configure file sharing in Windows XP

Make sure you have File sharing enabled in Vista, I think it's not on by default...

It can be enabled through the control panel.... can't remember exactly. I once managed to get the file sharing work between XP and Vista, and the problem was just that sharing was not enabled in Vista. :)

Of course, make sure that any firewall isn't blocking connections.

Do you get a response from the other computer when pinging its IP address? (go to command prompt, and type "ping 192.168.0.102")

What kind of connection are you using? just ethernet-cable between the computers, or through a modem/router, etc?

  • 3 weeks later...

Well, I'd explain this.

Go to My Computer -> My shared folder -> Right click and then properties -> Sharing -> Tick all.

Restart.

Then let your sister go to My Network Places -> Entire Network -> 1 of these would have her PC. Make sure she does that too, try it and tell us what you get.

3) And also see KB922120 (this is probably the most important part of it though.
Most important part??? Nonsense -- having machines show up connected on the "Network Map" has absolutely NOTHING to do with accessing a file share - NOTHING!!

Thats like telling people that machines have to be in the same workgroup.. So this is going to be the new vista FUD on file sharing?

^ Sorry...:rolleyes:

But seriously, being able to see a computer helps a great deal.

Well, they have to be don't they?

NO! they freaking don't, a workgroup is nothing more than a place holder to where to put names in "browsing" Browsing has NOTHING to do with accessing a computer or its shares..

An you can see the computer JUST fine.. they just will not be connected on the total network map is all.

You will see them in the different workgroups if browsing, you can access them by name directly -- which is the fastest method

run \\computername

Seeing them with a Line drawn on your network map is nothing but eye candy - an has nothing to do with accessing shares on them.

If the user wants to see them in a pretty little map -- cause he can not figure out that his computers are all connected to his router ;) Then yes he needs to install that patch.. But it has NOTHING do with file sharing.

post-14624-1186575286_thumb.jpg

See all the machines on the network -- I can access shares just fine, I can see them just fine.. There is just not a line drawn on the map -- since they are not running the "Link-Layer Topology Discovery (LLTD) Responder" is all.

If you want, I put every single machine into a different "workgoup" and still be able to see them.. It will just take awhile for the browse list to correct it self.

Here you might learn something

http://www.microsoft.com/downloads/details...;displaylang=en

Computer Browsing for SOHO Networks with Microsoft Windows

Browsing has NOTHING to do with file sharing!

Here, this is what I am talking about.. As you can see now.. all the machines are in "different" workgroups. I can SEE them, I can access them!

An for grins I installed LLTD on one my xp machines.. You can see connected on the network map -- wooh hoow :rolleyes:

It can take a few minutes for the browse list to get into sync. (read the doc I linked too) the XP machines are in a xpgroup.. they will show up in a few minutes.

Even though the kids machine is not listed in the browse list yet.. Guess what I can still access it..

post-14624-1186580420.jpg

See the shared printer.

As I was saying the same workgroup has nothing to do with file sharing, nor does LLTD. So please do not spread FUD about that patch being need to share files between xp and vista.

I sometimes wonder how much use the ability to browse is?
IMHO its pretty much worthless.. Any user looking for a share, would they not know the name of the server the share is on?? ;)

It takes a lot longer to get anywhere.. it causes unnesessary chatter, etc.. etc..

If you use a share quite often, just put a shortcut to \\computername\share or map a drive letter to it, etc.

Only reason I let it even run on my network is to be able to answer questions, an post screen shots ;)

edit: I had to delete the map.. a tiny bit of personal info was on there ;) I can repost.. So we have a 50MB limit on attachments? Man, hmm maybe I should rethink how I put up screen shots if have to delete them in the future.. could make past threads a bit funny looking when found on a search.. Oh wait - no one searches here, so its all good ;)

here is the cleanedup map from the above post

post-14624-1186587788_thumb.jpg

Edited by BudMan

Just to be complete.. I told you the other machines would show up in a bit ;)

post-14624-1186591082.jpg

As you can see - all the machines are in different workgroups.. An they can be seen, an accessed ;)

Now please do not pass on any more FUD about that patch, or having to be in the same workgroup.

Vista an XP can share files just fine - there is no patches that have to be installed, nor anything special about workgroups that have to be configured, etc..

I have been trying to squash the workgroup FUD for years around here.. every time someone asks about file sharing it seems to rear its ugly head again.. We don't won't the same type of thing happening with LLTD. Thanks!

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

    • No registered users viewing this page.
  • Posts

    • Anybody that thinks flying cars were possible are idiots. Everyone would basically need a pilot licence, can you imagine how insane and dangerous that would be, people can barely handle driving on land safely right now.
    • Microsoft Edge 149.0.4022.80 by Razvan Serea Microsoft Edge is a super fast and secure web browser from Microsoft. It works on almost any device, including PCs, iPhones and Androids. It keeps you safe online, protects your privacy, and lets you browse the web quickly. You can even use it on all your devices and keep your browsing history and favorites synced up. Built on the same technology as Chrome, Microsoft Edge has additional built-in features like Startup boost and Sleeping tabs, which boost your browsing experience with world class performance and speed that are optimized to work best with Windows. Microsoft Edge security and privacy features such as Microsoft Defender SmartScreen, Password Monitor, InPrivate search, and Kids Mode help keep you and your loved ones protected and secure online. Microsoft Edge has features to keep both you and your family protected. Enable content filters and access activity reports with your Microsoft Family Safety account and experience a kid-friendly web with Kids Mode. The new Microsoft Edge is now compatible with your favorite extensions, so it’s easy to personalize your browsing experience. Microsoft Edge 149.0.4022.80 changelog: Fixes Fixed an issue that prevented QR code generation from working. Feature updates Intune MAM Protected Downloads. The protected downloads feature for Intune MAM will now save downloaded files to the Documents > Microsoft Edge > Downloads folder in OneDrive. Extensions monitoring in the Edge management service. The Microsoft Edge management service now allows admins to gain visibility into extensions installed across their managed users. From the extensions monitoring page, admins can see which extensions have been installed as well as manage user requests for blocked extensions. For more information, see Microsoft Edge Extensions Monitoring. Validate Edge builds early with enterprise preview. Enterprise preview provides a simpler way for admins to flight pre-release Edge builds to their users. To reduce friction and bolster usage, users will receive pre-release builds directly inside of their Stable Edge application. Admins can allow users to easily opt-out of the preview experience, using built-in rollback to switch between their pre-release and stable channels with ease. Microsoft 365 admin center users can configure the feature, view their flighting population, and receive personalized recommendations all in one place. For more information, see Get started with Enterprise Preview in Microsoft Edge. Download: Microsoft Edge (64-bit) | 193.0 MB (Freeware) Download: Microsoft Edge (32-bit) | 170.0 MB Download: Microsoft Edge (ARM64) | 188.0 MB View: Microsoft Edge Website | Release History Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • 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?
  • 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.
      69
  • Tell a friend

    Love Neowin? Tell a friend!